Commit 6824a42
fix(cli): make
Closes #54.
`verisimiser start` previously parsed the manifest, printed three
status lines, then returned `Ok(())` because the interception daemon
(V-L1-C1, #46) hasn't been built. That looks like a successful start,
which is worse than not having the subcommand at all — anyone running
`verisimiser start` would assume their database is being augmented
when nothing is happening.
Replace the print-and-exit with `anyhow::bail!` that:
- still loads the manifest (so config errors surface)
- names the tracking issue (#46 / V-L1-C1) in the error message
- exits non-zero, so shell scripts and CI gates notice
This is option (a) from the issue: refuse with a typed error. Once the
interception daemon lands in V-L1-C1, the bail can be replaced with
the actual daemon loop.
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>start refuse explicitly instead of silent-exiting (#71)1 parent 4315990 commit 6824a42
1 file changed
Lines changed: 11 additions & 14 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
133 | 133 | | |
134 | 134 | | |
135 | 135 | | |
136 | | - | |
137 | | - | |
138 | | - | |
139 | | - | |
140 | | - | |
141 | | - | |
142 | | - | |
143 | | - | |
144 | | - | |
145 | | - | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
146 | 147 | | |
147 | | - | |
148 | | - | |
149 | | - | |
150 | | - | |
151 | 148 | | |
152 | 149 | | |
153 | 150 | | |
| |||
0 commit comments