session 2026-07-24 night: V-TEXT wave censused (finite 3-class gap-map); root = 0 integration tests → writer switch orphaned cleaner + REVIEWED-54 §5 fallback; unlock named (pre-proc cleaner + tokenizer-as-class FIX); engine track independent of the wave (0 verified → fence is converted+attested)

2026-07-24 19:50:34 +02:00
parent 06203c3833
commit 30f3776095
6 changed files with 91 additions and 4 deletions
@@ -623,3 +623,11 @@ No new skill proposal. Two register notes: **(1)** the S1 proposal **implementat
 | Chamber graduation: **build to the constitution, not to a legacy canonical** | **patch** (chamber `CLAUDE.md` Load-bearing disciplines) | Steward-corrected 2× this session: *"we cannot use the extant canon as precedent."* The extant canon is a pre-constitution/pre-fleet legacy body being *brought* to trust; inferring a requirement's absence from what a legacy peer looks like (no-sidecar from peers; frontmatter mirrored from Bringhurst which predates the schema) reproduces the legacy gap. Build to the spec/`graduation-spec.yaml` schema; where the constitution is silent/unbuilt for a tier, name the gap — never fill it from a peer. The legacy-witness principle (REVIEWED-70) applied to graduation *method*. The chamber `CLAUDE.md` already carries the "legacy body / resolve-source-through-Chamber-Sources" framing (2026-07-24 morning); this generalizes it to the graduation bar. **Discipline change → surface for steward.** | 2026-07-24 (steward-directed) | **PROPOSED** |

 *(Both are propose-only governance-doc patches surfaced for steward authorization; neither auto-applied. They also chime with jurist-package's existing "trace a ruled finding's inference, not its words" — I violated that this session by quoting REVIEWED-64 without applying it to `sections[]`, so the existing discipline held; no patch needed there, only the reminder that it fired.)*
+
+### Harvest 2026-07-24 (night — V-TEXT wave first bite / the integration-test gap)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| chamber-library CLAUDE.md — **integration-test-gap discipline** | patch (repo CLAUDE.md, discipline → steward review) | Add to §Load-bearing disciplines: *"The fleet has UNIT tests (test_tools, per-tool fixtures) but NO integration test — nothing runs a real source end-to-end through the composed pipeline. A producer change (e.g. the REVIEWED-72 pandoc writer switch) passes every unit test and silently breaks the COMPOSITION (orphaned `clean_pandoc_html_residue` + the REVIEWED-54 §5 footnote fallback). The fix is a tier-spanning integration canary with POSITIVE per-stage assertions (plant N markers, assert N-of-N removed — a negative 'output is clean' passes a no-op) + a change-impact clause. See `_curation/v-text-wave-gap-census-2026-07-24.md`."* | `chamber-library/CLAUDE.md` §Load-bearing disciplines | **PROPOSED** (discipline change → steward authorizes; not auto-applied at wrap) |
+
+*(One candidate, load-bearing: this session's whole cascade traced to this gap, and the steward named the mechanism ["prompted to update downstream tools at the same time as the breaking change"]. The census doc holds the full analysis; the CLAUDE.md line is the pointer that stops future-us re-deriving it at the point of work. The GOVERNANCE half — generalize the §Governance reassigned-component check into the change-impact principle, now 3 instances — is loop-work tracked in the census doc, not a skill.)*