docs: record completed hardening work
This commit is contained in:
parent
b6f74e6e83
commit
f1e3addc16
|
|
@ -45,8 +45,8 @@ work belongs here before implementation.
|
|||
- [ ] Test malformed/corrupt configuration and snapshot files without panics.
|
||||
- [ ] Test interrupted/failed writes where feasible and implement atomic file
|
||||
replacement for repository metadata and epoch snapshots.
|
||||
- [ ] Remove unused dependencies and dead/demo command paths.
|
||||
- [ ] Make format, tests, strict Clippy, and release build pass.
|
||||
- [x] Remove currently reported unused dependencies and the demo `show` path.
|
||||
- [x] Make format, tests, strict Clippy, and release build pass.
|
||||
|
||||
## Phase 3 — finish the intended current CLI
|
||||
|
||||
|
|
@ -109,17 +109,16 @@ These require user approval and are not part of the current implementation:
|
|||
|
||||
## Audit notes
|
||||
|
||||
- The README currently describes organisation/link/event interfaces that are
|
||||
absent from the top-level parser.
|
||||
- `show` currently prints a randomly generated entity repeatedly and does not
|
||||
inspect repository data.
|
||||
- `init` exposes `--force`, but the handler does not use it.
|
||||
- `epoch diff` and `epoch fsck` panic through `unimplemented!()`.
|
||||
- The old README described organisation/link/event interfaces absent from the
|
||||
parser; the rewritten docs now distinguish current and planned behavior.
|
||||
- The old demo `show` output, ignored `init --force`, and panicking `epoch diff`
|
||||
/ `epoch fsck` paths were replaced and covered by CLI tests.
|
||||
- `epoch switch --force` is parsed but ignored.
|
||||
- Entity rendering emits ANSI escapes when stdout is redirected and relies on
|
||||
several optional Nerd Font glyphs for labels.
|
||||
- Name generation used to create `naming.json` in the working directory; this
|
||||
was removed in favor of read-only embedded defaults.
|
||||
- The binary crate currently has no tests; most coverage is parsing/model-level.
|
||||
- Existing library tests passed on 2026-09-20. Tarpaulin was intentionally not
|
||||
- The binary now has four integration tests; broad lifecycle and failure-path
|
||||
coverage remains on the backlog.
|
||||
- All 62 tests and the release build passed on 2026-09-20. Tarpaulin was intentionally not
|
||||
run because badges are release-only by project policy.
|
||||
|
|
|
|||
Loading…
Reference in New Issue