chore: remove plan/ directory, migrate doctrine to remote-first - #395
Merged
Merged
Conversation
Every plan/*.md body was migrated to its corresponding GitHub issue body (in an ## AI Agent Notes section wrapped with amos tooling markers) via amos sync-edges + a one-shot body-migration script; every frontmatter edge was migrated to native GitHub relationships. With both sides remote, the local plan files are redundant. - Delete all 80 plan/*.md files. The plan/ directory is now empty (kept by .gitkeep for backward-compat with tooling that expected it; will drop in a follow-up). - Update broken `plan/N-slug.md` links in docs to point at the GitHub issues directly: `docs/design/gpu-capability-sandbox.md`, `docs/research/blit-copy-classification.md`, `docs/retests/294-post-vulkan-cleanup-retest.md`. - Rewrite `docs/issue-template.md` rules 1–2: "GitHub is the source of truth" + "every issue includes an AI Agent Notes section". Add the AI Agent Notes section (with amos markers) to the template itself. Note that `Blocked by` / `Blocks` / `Parent` are native GitHub relationships, not text in the Related section. - Update CLAUDE.md's issue-writing paragraph to match and point at the new `/amos-file` skill. Verified before landing: moved plan/*.md to a /tmp backup, ran amos milestones / next / blocked / graph against the emptied directory, confirmed identical output to the pre-move state (9 milestones, 6 ready in Polyglot SDK Realignment, etc.). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
With every plan-file body migrated to its GitHub issue (in an
## AI Agent Notessection) and every frontmatter edge migrated to native GitHub relationships viaamos sync-edges, the localplan/*.mdfiles are redundant. This PR removes them and updates the doctrine docs to match.Changes
plan/*.mdfiles.plan/...doc links in:docs/design/gpu-capability-sandbox.md→ link to issue GPU capability-based access (sandbox + escalate) #319 directlydocs/research/blit-copy-classification.md→ link to issues GPU capability-based access (sandbox + escalate) #319 / Restrict GpuContextSandbox API surface to safe ops #324 directly, drop the "Plan file" referencedocs/retests/294-post-vulkan-cleanup-retest.md→ link to test: retest camera + encoder + display roundtrip after Vulkan cleanup #294 directlydocs/issue-template.mdrules 1–2 for remote-first:<!-- amos:ai-notes-begin -->/<!-- amos:ai-notes-end -->markers so tooling can find and update safelyBlocked by/Blocks/Parentare native GitHub relationships, not text in theRelatedsectionCLAUDE.mdissue-writing paragraph to match + point at the new/amos-fileskill (part of tatolab/amos#43).Verification before land
plan/*.mdto a/tmpbackup.amos milestones— identical counts to the pre-move state (9 milestones, Polyglot SDK Realignment 6 open / 6 ready / 3 done, etc.).amos next --dir ...— correctly enumerates the 6 open issues in the focused milestone.amos blocked --dir ...— "no matching nodes in focused milestone" (expected, all 6 are ready).amos graph --dir ...— tree renders from native edges alone.Related
amos issue-createsubcommand +amos-fileskill that this doctrine refers to.🤖 Generated with Claude Code