docs(harness): land the DevTools RFC run's closing artifacts - #1522
Open
rickylabs wants to merge 1 commit into
Open
docs(harness): land the DevTools RFC run's closing artifacts#1522rickylabs wants to merge 1 commit into
rickylabs wants to merge 1 commit into
Conversation
The RFC and its 159-file planning corpus merged with #1450, but the three artifacts written after that merge -- the filing record, the session record, and the final context-pack state -- existed only on the plan branch. That matters for one concrete reason: the filing ledger posted on #1450 links FILING-LOG.md at a plan-branch blob URL, and plan branches get deleted. The record of which draft ID became which live issue, which preconditions held, and which two deviations from the manifest were taken would have gone with it. Landing them next to the corpus they close makes the ledger's link durable. No RFC or corpus content changes; this only adds what the merge predates. Refs #1450 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DChBXWYP9LStvjQztUJV5b
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
Three artifacts written after PR #1450 merged, landing next to the corpus they close.
filing/FILING-LOG.md.llm/2026-08-11-devtools-contribution-rfc-seed.mdrun-loop.md§9.5context-pack.md(modified)leak-report.mdagentic:leak-checkoutput —survivors: []Why it is worth a PR rather than leaving on the plan branch
The filing ledger posted on #1450 links
FILING-LOG.mdat a plan-branch blob URL, and plan branches get deleted. That file is the only record of which draft became which issue, which preconditions held at filing time, and which two deviations from the ratified manifest were taken (DT-8 filed as six-state because the manifest predates the amendment that added the sixth quarantine state; bodies citingrfcs/0005-…rather thanrfcs/0000-…). Losing it would leave the ledger pointing at nothing.The RFC and its 159-file corpus already merged with #1450 — this only adds what that merge predates. No RFC or corpus content changes.
Not included, deliberately
An
arch-debt.mdentry for #1481 (/designships ungated) is warranted — it is a live doctrine violation sitting inBacklog / Triage, i.e. without the time-bounded plan10-codebase-verdict-and-handoff.md:184-195requires..llm/harness/debt/arch-debt.mdwas outside the run's mutation boundary, so the obligation is recorded in the session record rather than taken quietly or dropped. It needs its own PR and a decision on the time bound.Refs #1450