jschoubben
c0b35652d0
papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.
48 lines
1.9 KiB
Markdown
48 lines
1.9 KiB
Markdown
---
|
|
status: open
|
|
opened: 2026-08-22
|
|
located-in: [hal]
|
|
fixed-by:
|
|
amended-design:
|
|
---
|
|
|
|
# 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 0007](../../02-DECISIONS/0007-no-npm-workspace.md)).
|
|
- 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`](../../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?
|