chore(audits): D4 dialect and drift-check items closed with justification (BDR-125 close-out)
This commit is contained in:
1 parent
173e1f97bf
commit
2bef08a6f8
1 file changed
+2
@@ -45,7 +45,9 @@
|
||||
|
||||
<!-- /feat D4 2026-11-12 (feature/prune-memory-status-reader): follow-ups from challenge rounds and gates, plan .claude/tasks/plans/2026-11-11-prune-memory-status-reader-1400.md r3 -->
|
||||
- Registry dialects the classifier cannot read: game is `format: 2` but written in the `date: … · status:` dialect (decision statuses unreadable), faunosteo uses `closed` / `active` words, v1 date dialects give no 90-day `proposed` candidate. /prune-memory shows them on the info-only `[Status unreadable]` line; a dialect migration (memory.sh upgrade or a one-shot rewrite per project) is not designed. Severity: medium (prune finds no candidate on those projects). Discovered while: /feat D4 challenge round 1. Not fixed.
|
||||
RESOLVED 2026-11-14 (BDR-125 close-out J), no code change: the migration path exists. v1 files: `memory.sh upgrade` (faunosteo done on chore/memory-v2 530af1b, its `closed`/`active` words upgraded, user merges). v2-headed files in the v1 `date: … · status:` dialect (game: 80+ BDRs, many mixed/prose lines): /prune-memory STEP 2 `[Status unreadable]` lists the IDs and the user gives each word (`memory.sh status <ID> "<word>"`); a judgment per entry, never an automatic rewrite. game run left to the user (another session has uncommitted work open there, a parallel rewrite of decisions.md would collide). 90-day `proposed` candidates on v1 date dialects: accepted limit (no date = no candidate, STEP 1.A says so).
|
||||
- skills/prune-memory STEP 4 — status drift check (Index vs body, title word vs status word) dropped from D4 as an ungated new gate. Severity: low. Discovered while: /feat D4 challenge round 2. Not fixed.
|
||||
WONTFIX 2026-11-14 (BDR-125 close-out J): BDR-129 makes the Index never a status source and the title never a status, so an Index/body or title/status drift changes no decision of any reader; `memory.sh check` already guards the structure. A new gate without a consumer is not added.
|
||||
- lib/memory.sh:657 `memory_legacy_status` reads `MEM_LEGACY_RE` from the environment: an ambient `export MEM_LEGACY_RE` also widens `memory.sh upgrade`'s `<end>` readers (`_mem_legacy_open`, `_mem_explicit_status`, `_mem_repair_one`, the last one decides a v1 closure write). Fails closed on a bad regex. Fix: explicit 4th positional argument, drop the env read. Severity: low. Discovered while: /feat D4 security gate. Not fixed.
|
||||
FIXED 2026-11-13 (d8e62c1): selector = 3rd positional, env read gone, `_MEM_LEGACY_BDR_RE` in memory.sh; T15-env-selector-ignored.
|
||||
- lib/memory.sh `memory_legacy_status` `<end>` range on v1 decisions: the last BDR entry runs to EOF, so a `## Index` or other `##` section after it would be read by the widened selector (none on disk today). Severity: low. Discovered while: /feat D4 verifier. Not fixed.
|
||||
|
||||
Reference in new issue
Block a user