R-263 writer invariant pinned by an AST test; R-368 IsDefault comment exact (no binary change; burn-down)
gates / gates (push) Successful in 32s
gates / gates (push) Successful in 32s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -1,3 +1,15 @@
|
||||
## unreleased — a comment pinned by a test, a comment made exact; no binary change (burn-down 2026-10-05: R-263, R-368)
|
||||
|
||||
The next release carries these two lines into its own entry.
|
||||
|
||||
- **R-263:** `SetBackupTarget` is „the only writer that GRANTS" `StoragePath.BackupTarget` (ClearBackupTarget also writes
|
||||
it, only `false`), now pinned by `internal/settings/r263_backup_target_writers_test.go`: an AST scan of every non-test
|
||||
file under `internal/` and `cmd/` for an assignment or a composite-literal key, refusing anything but `false` outside
|
||||
`SetBackupTarget`. Red-proofs (`ClearBackupTarget` writing `true`; a `BackupTarget: true` literal in `internal/web`)
|
||||
both convict — `felhom.eu/documentation/audits/burndown-2026-10-05/r263-red-proof.txt`.
|
||||
- **R-368:** `StoragePath.IsDefault`'s comment says who applies it — the deploy FORM pre-selects it; the deploy API
|
||||
applies no default. Behaviour unchanged on purpose (it is right on the path households use).
|
||||
|
||||
## v0.296.0 — a backup cut off by a power cut or a restart is said on the page; the whole-system backup text states today's measurement (R-519, R-518) (2026-10-05)
|
||||
|
||||
**MinAgent: 0.131.0** (unchanged). New household string: `backups.interrupted_run` (Hungarian and English); the
|
||||
|
||||
Reference in New Issue
Block a user