docs: triage the capture archive, file its live findings #234

Merged

john merged 1 commit from chore/triage-capture-archive into main 2026-08-22 19:37:31 +00:00

Conversation 0 Commits 1 Files changed 1 +18 -5

john commented 2026-08-22 19:28:28 +00:00

Owner

Copy link

The 185-item block archived on 2026-08-08 had never been read since. Its 30 severity-marked items were verified against the current tree: 19 already fixed, 10 still live, 1 moot.

The fixes had shipped across later cycles with nothing closing the capture, which is what an untriaged queue looks like from the inside.

The 10 live findings are filed as #231, #232 and #233. The remaining 155 unmarked items are unverified.

Two things argue for the tracker over the file:

• #231 duplicates a defect class v3.5.8 phase 2 filed independently against the same seam two weeks later, neither aware of the other.
• .planning/CAPTURE.md is gitignored, so it is the one planning document with no history behind it.

issue-check.mjs already surfaces referenced issues at every /cad-land, which is the come-back-on-its-own property CAPTURE.md stopped providing the moment anything went below ## Archive.

Doc-only change: PROJECT.md's close record. CAPTURE.md is gitignored and carries none of this.

The 185-item block archived on 2026-08-08 had never been read since. Its 30 severity-marked items were verified against the current tree: **19 already fixed, 10 still live, 1 moot.** The fixes had shipped across later cycles with nothing closing the capture, which is what an untriaged queue looks like from the inside. The 10 live findings are filed as #231, #232 and #233. The remaining 155 unmarked items are unverified. Two things argue for the tracker over the file: - #231 duplicates a defect class `v3.5.8` phase 2 filed independently against the same seam two weeks later, neither aware of the other. - `.planning/CAPTURE.md` is gitignored, so it is the one planning document with no history behind it. `issue-check.mjs` already surfaces referenced issues at every `/cad-land`, which is the come-back-on-its-own property `CAPTURE.md` stopped providing the moment anything went below `## Archive`. Doc-only change: `PROJECT.md`'s close record. `CAPTURE.md` is gitignored and carries none of this.

john added 1 commit 2026-08-22 19:28:29 +00:00

docs: triage the capture archive, file its live findings ... d46e536763

The 185-item block archived on 2026-08-08 had never been read since. Its 30
severity-marked items were verified against the tree: 19 already fixed, 10 still
live, 1 moot. The fixes had shipped across later cycles with nothing closing the
capture, which is what an untriaged queue looks like from the inside.

The 10 live are filed as #231 (six defects in the release/changelog seam, all
reproduced by execution), #232 (plan frontmatter lets plan-overlap clear two
plans that collide) and #233 (two stale self-description claims). The remaining
155 unmarked items are unverified.

#231 duplicates a defect class v3.5.8 phase 2 filed independently against the
same seam two weeks later, neither aware of the other. That, plus CAPTURE.md
being gitignored and so the one planning document with no history behind it, is
the case for the tracker rather than the file.

john merged commit a2bfa2c2f9 into main 2026-08-22 19:37:31 +00:00

john referenced this pull request from a commit 2026-08-22 19:37:33 +00:00

Merge pull request 'docs: triage the capture archive, file its live findings' (#234) from chore/triage-capture-archive into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

already-shipped

Capability was already present in the shipped code when triaged; no work needed

  

bug

Something isn't working

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

external-review

Raised by an outside code review; body carries the adjudication

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

in progress

  

invalid

This doesn't seem right

  

needs-decision

Deliberate keep/cut call before any code

  

proposal

Make the case for a change before writing the code

  

question

Further information is requested

  

security

Hardening: a control that fails silently or an exposure surface

  

wontfix

This will not be worked on

No labels

already-shipped

bug

documentation

duplicate

enhancement

external-review

good first issue

help wanted

in progress

invalid

needs-decision

proposal

question

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: crenshawdev/cadence-archived#234

No description provided.