Stage the GitHub Issues tracker handoff - #76
Merged
Conversation
Prepare the isolated instruction/writer proposal for the reviewed GitHub Issues + selected-Project tracker handoff (canonical packet publication/pantheon/approved-packet.json, SHA-256 64e87550...c74d11, independently re-reviewed and passed against the 23-issue packet, plus a later 38th source-coverage record folded into the existing issue 52 rather than a new issue). - AGENTS.md: replace the Tasks section's .tasks/-only instructions with a pointer at docs/github-issues.md and its activation checkpoint, minimal replacement rather than a second competing authority. - CONTRIBUTING.md: point the work-item form's closing paragraph at the staged handoff instead of restating .tasks/ as permanently authoritative; the pre-existing Lexicon links in this section are untouched. - README.md: add a short entry point to the staged handoff and migration map. - docs/github-issues.md (new): the staged issue workflow, its authority-after-activation rules, and the activation checkpoint: pause/drain, human merge, final source compare, staged read-only discovery probe, record activation (claims still paused), a bounded post-activation GitHub-only pickup recheck, then resume claims. The selected GitHub Project is referenced generically throughout (owner/number supplied through authorized operational context), never named or hard-coded. - docs/github-tracking-migration.md (new): the full 23-issue owning-map and 38-record source disposition table, plus an in-repository byte ledger. Three cross-repository shared-idea records, and the later blind-review-packet supplement (folded into existing issue 52, its own supplemental issue closed not planned as a duplicate), are recorded as duplicate/existing-parent, not declined, with no link where the owning record is private. No .tasks/ bytes changed, no runtime or MCP code touched, no GitHub write performed. This commit is local only; push and PR creation wait for root's review of this exact diff. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GWABA4PMD96miVKtSfYJQr
Three narrow corrections to docs/github-issues.md, applied atop 3426c62 after independent review passed the prior four-finding rework (migration-independent-review.md, manifest SHA-256 54ea23b4136ea311c4a76c3e4b9bfabad83e9535f5c247ae0a0549ece3c6dfcd): - Drop the "that is what completing the cutover means" claim from the Authority section: step 5 establishes GitHub authority: it does not itself complete the cutover, which remains step 7. - Restrict the step 6 activation-checkpoint pickup recheck, and the "Pick up and hand off work" intro that describes it, to steps 1 through 4 of that procedure, read-only, against the one unstaged candidate. The prior wording ran the full six-step procedure, which would have claimed the candidate and moved it to Doing while general claims are still supposed to stay paused between steps 5 and 7. No other file changed. Still exactly five files differ from base 5cd3588, still 38 source keys, 23 issues and 19 unmodified legacy task files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GWABA4PMD96miVKtSfYJQr
![daedalus-orion[bot]](https://avatars.githubusercontent.com/u/101428489?s=60&v=4){kind=small}
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
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
Stages the handoff from
.tasks/JSON tracking to GitHub Issues, without activating it yet.AGENTS.md: replaces the.tasks/-only "Tasks" section with a pointer at the stagedactivation checkpoint in
docs/github-issues.md.CONTRIBUTING.md: updates the "Filing a work item" closing paragraph to match, dropping thenow-inaccurate "an explicit cutover is decided" phrasing in favor of the staged checkpoint.
README.md: adds a short entry point linking the staged handoff and the migration map.docs/github-issues.md(new): the staged issue workflow, authority before and afteractivation, how to pick up and hand off work against the repository's selected GitHub Project,
how to close against evidence, and the activation checkpoint itself.
docs/github-tracking-migration.md(new): the full owning-issue table for the publishedissues and the full source-disposition map from the prior
.tasks/records and planningdocuments.
Why
.tasks/JSON records already disagreed with reality (several readreviewafter their pullrequests merged), and this repository's GitHub Issues are now populated with a reviewed,
one-to-one mapping from every prior source record to an owning issue or an explicit disposition.
This proposal is the instruction and source-map half of that handoff: it tells a contributor
where authority currently sits and what changes once activation is verified.
What this does not do
.tasks/*.jsonbyte is touched. All existing task files stay present and unmodified as ahistorical ledger.
remaining steps in
docs/github-issues.md's own checkpoint (draining acknowledged legacywriters, a final source comparison from the merged revision, and a read-only discovery probe)
are verified,
.tasks/stays authoritative exactly as it is today.Review only
This is a review-only proposal per the repository's own contribution guidance: it needs a human
merge before anything in it takes effect, and merging alone does not itself complete activation.
🤖 Generated with Claude Code
https://claude.ai/code/session_01R42VsFhDeagCR5JqirAUVG