chore(memory): G5 fixed, BLK-048, LRN-276, G6-G9 logged

This commit is contained in:
bchanot committed 2026-11-11 13:53:20 +01:00
1 parent aa9da93222
commit c37948c6c1
7 files changed
+150 -1

No files matched your search

+8
View File
@@ -13,3 +13,11 @@
- agents/status-reporter.md:35 + agents/plugin-probe.md:22-23,69 — report installed (cache) or user-scope `claude plugin list` state as "active"; the per-project state is the PROFILE line (`current --plain`). Severity: low. Discovered while: code-clean 2026-11-09. Not fixed.
FIXED 2026-11-10 (/bugfix, bugfix/banner-effective-profile): status-reporter takes `Plugins ON:` from `list_on_plugins` + `pack-*=on` (cache = installed only); plugin-probe comment and plugin-advisor INPUT name PROFILE as the per-project source (PLUGINS = installed).
- agents/handover-doc-writer.md:77-84 — parses registry statuses by hand ("open vs resolved"), the class behind the BLK-032..034 false-open (BDR-129). A fix must read `memory.sh -C <project> index` on v2 registries and keep the `## Index` read on v1 registries never upgraded (`memory.sh index` ignores a v1 Index; memory.sh:21-23). Severity: medium (client deliverable). Discovered while: code-clean 2026-11-09. Not fixed.
FIXED 2026-11-11 (/bugfix, bugfix/handover-memory-status): new `reconcile_blk_classify` (lib/reconcile.sh: strict word on v2, single-word status label on v1 via `_mem_v1_word`, never the `## Index`; closed omitted, prose/mixed/`closed`/`###` entries = unreadable); STEP 9 rooted on the PACKAGE root; SYNTH REPORT fenced with a mandatory `MEMORY:` line, relayed to the user and into the 9.7 report; test lib/tests/handover-memory-contract.test.sh HM1-HM3 runs the shipped STEP 9 block. The request's "keep the v1 Index read" was dropped after challenge round 1 (the Index drifts, BDR-129, LRN-055).
<!-- /bugfix G5 2026-11-11: challenge rounds and gates, plan .claude/tasks/plans/2026-11-10-handover-memory-status-1600.md -->
- agents/handover-doc-writer.md §6.1 — vulgarizes BDRs with no status filter: a superseded or deprecated decision can read as current in the client deliverable. Severity: medium (client deliverable). Discovered while: /bugfix G5 challenge round 1. Not fixed.
- lib/memory.sh `upgrade` (`mem_want`, `_mem_verdict_diff` skips Index-stated IDs) — may take a stale v1 `## Index` cell over a `**Statut** :` body line. UNVERIFIED: check before recommending `upgrade` on v1 repos (faunosteo). Severity: medium if real (wrong status written into the body). Discovered while: /bugfix G5 challenge round 1. Not fixed.
- agents/handover-doc-writer.md STEP 10 and other paths — `git log` and file reads are cwd-relative, not rooted on the PACKAGE root; the PACKAGE `PROJECT:` line is space-separated, so a root containing a space mis-parses (the G5 orchestrator check only catches it when blockers.md exists). Severity: low. Discovered while: /bugfix G5 challenge round 1. Not fixed.
- lib/memory.sh `memory_legacy_status` default range (`## ID` to the next `## BLK-`) — on a v1 registry a `### BLK-` entry after a `## BLK-` entry feeds its status line to the `##` entry: a resolved `###` entry can close the open `##` entry above it, which then leaves the handover §5 (the `###` ID itself is flagged unreadable). Severity: low (rare dialect, flagged indirectly). Discovered while: /bugfix G5 verifier. Not fixed.
- agents/handover-doc-writer.md:83 + agents/client-handover-writer.md:1201-1202 — `ROOT="<PROJECT root from the PACKAGE>"` pastes the root into a double-quoted literal, and the printed remedy `memory.sh -C <root> status …` leaves `<root>` unquoted: a root with `"`, `$(…)`, a backtick or a space breaks the line or splits the path. Value is the operator's own `git rev-parse --show-toplevel`, not registry data. Severity: low. Discovered while: /bugfix G5 security gate. Not fixed.