jschoubben
e1febe8e0f
The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18, 19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only the archaeology of what used to be there. Renumbered contiguously. Renames run in ascending order, so every target number is already free and no two files ever collide. The reference rewrite is one simultaneous pass rather than a sequence of replacements. Numbers moved into slots other numbers were vacating -- the node host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time would have cascaded and silently pointed things at the wrong record. Seven plain-text references survived the merges as prose rather than links, naming records that no longer existed: the enrolment token, the link boundary, what a declaration is, reachability, the repository structure. Each mapped to the consolidated record that now holds it. Verified rather than assumed: every [ADR NNNN](path) link now has matching text and target, checked across the whole repository, and the checker passes. Frontmatter `consolidates:` lists dropped -- they named records that are gone, and each consolidated record already says in prose what it absorbed.
1.9 KiB
status, opened, located-in, fixed-by, amended-design
| status | opened | located-in | fixed-by | amended-design | |
|---|---|---|---|---|---|
| open | 2026-08-22 |
|
005 — The end-to-end pipeline harness has not built since the workspace was removed
Symptom
The repository's end-to-end pipeline test harness depends on a workspace that no longer exists. It has not been buildable since 2026-06-04. Nothing runs it, and nothing reports that nothing runs it.
Why this matters
The delivery pipeline is the mesh's most consequential machinery — every module reaches every node through it — and its only end-to-end coverage has been silently dead for over two and a half months.
That interval is not incidental. Several of the pipeline's most expensive defects landed inside it: packaging that was never actually split from build, migrations and provisioning scripts reading a source layout that no longer ships, selection files never packaged at all. Whether this harness would have caught any of them is unknown — which is itself the point. The coverage was assumed, not checked.
Evidence
- The workspace was removed by pull request #240 on 2026-06-04 (ADR 0004).
- The harness has not built since that date.
- Recorded in the knowledge base as a standing entry, not as a fixed incident.
Relationship to the lab
03-DESIGN/01-to-be/01-end-to-end-testing.md
designs end-to-end testing on a lab mesh, which would replace this harness rather than repair
it. That is a reason to decide its fate deliberately, not a reason to leave it broken and
unmentioned: until the lab exists, this is the coverage the pipeline is presumed to have.
Open questions
- Repair, or retire in favour of the lab? Leaving it in the repository unbuilt is the one option that keeps the false impression of coverage.
- Was anything relying on it, or had it already stopped running before the workspace removal?