docs: tighten deployment runbooks
Some checks failed
CI / fmt, clippy, docs (push) Failing after 5s
CI / test (ubuntu-latest) (push) Failing after 5s
CI / test (macos-latest) (push) Has been cancelled
CI / test (windows-latest) (push) Has been cancelled
CI / iroh integration smoke tests (push) Has been cancelled
Security / RustSec cargo-audit (push) Has been cancelled
CodeQL / Analyze Rust (push) Has been cancelled

This commit is contained in:
Eric Wendland 2026-07-11 11:54:50 +02:00
commit 0595b39532
4 changed files with 128 additions and 13 deletions

View file

@ -41,6 +41,8 @@ behavior.
endpoint ownership live outside the main feature handler module.
- `[x]` Iroh accept-loop and background live-sync task spawning live outside
the main feature handler module.
- `[x]` Graceful shutdown cancels daemon tasks, closes the shared Iroh
endpoint explicitly, and removes the local control socket.
- `[x]` Runtime state is represented by narrow structs with documented
ownership and locking rules.
- `[x]` Existing daemon startup and status tests pass unchanged.
@ -334,6 +336,14 @@ platform/version details, and evidence for this gate. This phase cannot be
marked complete from local unit or integration tests alone; it requires two real
machines and tagged pre-release upgrade evidence.
- `[x]` Prepare the dogfood runbook and evidence format.
Acceptance criteria:
- `[x]` Runbook commands are checked against the current CLI command tree.
- `[x]` Positive paths verify transferred data, not only command exit status.
- `[x]` Streaming checks are bounded or have explicit completion criteria.
- `[x]` Evidence records capture platform, artifact, version, timestamp,
result, and follow-up details without collecting private material.
- `[ ]` Complete two-machine dogfood checklist.
Acceptance criteria:
- `[ ]` Fresh install works on at least two real machines.