Record the decision-overview rollout and pin its image in admission inputs

Operator rolled out sha256:971e88e3 after a pre-rollout inspect (7 confirmed,
no unresolved submissions) and an in-volume backup. README backup path now
matches the deployment, which mounts no /backup volume.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 359683@bnt-lap001
Assistant-Session: eebdc939-7a9b-4e50-9d39-c8437e8a14ec
This commit is contained in:
tegwick 2026-09-21 22:32:19 +02:00
parent ac0a4e2fb0
commit 77792fa4f5
4 changed files with 26 additions and 6 deletions

View file

@ -164,11 +164,12 @@ The installed `informed-decision-admin` supports local custody operations only:
```sh
informed-decision-admin inspect --db /data/private/review.sqlite
informed-decision-admin backup --db /data/private/review.sqlite --output /backup/private/review.sqlite
informed-decision-admin backup --db /data/private/review.sqlite --output /data/private/review-YYYYMMDD.sqlite
```
The backup parent must already be owned/private 0700; the destination must not
exist. Backup uses SQLite's consistent backup API while the service may be live.
exist. The deployment mounts no `/backup` volume; `/data/private` qualifies but
shares the PVC, so copy the file off-cluster (`kubectl cp`) for an independent copy. Backup uses SQLite's consistent backup API while the service may be live.
Do not copy a running SQLite file while ignoring WAL. Inspection prints counts
and schema version, not memo content or credentials. These are privileged
operator custody commands, not browser endpoints. An independent backup copy,