Propose CH-015: capture build/distribution/guide/downloader idea as a plan - #22
Merged
Merged
Conversation
… plan Adds G-003 (proposed goal: legacy robots easy to obtain, wrap, and run) and P-002 (draft plan serving it, four milestones: Gradle version-catalog cleanup, artifact distribution, a usage guide pointing to rumble.robowiki.net, and bot-acquisition tooling with feasibility left open). Regenerates the goals and plans README indexes. Flags an M-prefix identity-ledger gap in open-questions.md: P-001's existing milestone IDs were never registered with clue id, so `next M` offers colliding numbers; this plan's milestones continue P-001's sequence directly instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6pPpd8gWaqE3w1PWYr4qn
flemming-n-larsen
marked this pull request as ready for review
September 9, 2026 18:56
…chema clue validate on 0.24.1 requires full core frontmatter (id, type, status, links, title) on every file under changes/CH-xxx/, not just proposal.md. proposal.md gets type: change, status: open (not "proposed" — that status is no longer valid for type change in this release). tasks.md and open-questions.md get their own ledger-tracked identities under the existing TASKS/OQ prefixes (TASKS-008, OQ-006), matching what a prior change already used for the same files. clue validate passes locally (68 artifacts, no issues). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6pPpd8gWaqE3w1PWYr4qn
Closes the open milestone-ID question: P-002's M-144-M-147 stay as manual continuation of P-001's sequence (human decision — no ledger backfill in this change). All tasks are done; deleting changes/CH-015-build-distribution-guide-plan/ per the digest step. clue validate --forbid-changes passes clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6pPpd8gWaqE3w1PWYr4qn
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
G-003(proposedgoal): legacy robots should be easy to obtain, wrap, and run on Tank Royale.P-002(draftplan) servingG-003, with four milestones: Gradle version-catalog cleanup (M-144), artifact build & distribution (M-145), a usage guide pointing to https://rumble.robowiki.net/ (M-146), and bot-acquisition tooling with mechanism left open pending feasibility (M-147).docs/goals/README.mdanddocs/plans/README.mdindexes viaclue scaffold.This is a plan-capture change only — no implementation against
P-002's milestones is in scope here; the plan is deliberatelydraft/todothroughout.Open question
changes/CH-015-build-distribution-guide-plan/open-questions.mdflags a.clue/id-ledger.yamlgap: theMprefix has no prior entries even thoughP-001already declaresM-001–M-143in its milestone tables, soclue id next Mcurrently offers colliding IDs.P-002's milestones (M-144–M-147) were numbered by continuingP-001's sequence directly instead. Needs a human call on whether to backfill the ledger or keep numbering milestones this way.Test plan
clue validatepasses clean (65 artifacts, no new issues)clue scaffoldregenerated both README indexes with no manual edits neededG-003/P-002wording and the milestone-ID open question🤖 Generated with Claude Code
https://claude.ai/code/session_01A6pPpd8gWaqE3w1PWYr4qn