Adopt canonical planning-convention repo (consumer #1)#238
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (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
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.
Replaces copy-paste sharing of the planning convention with a canonical source repo + an agent-applied instruction doc, and wires
modern-dias its first consumer.The mechanism
The convention (the
index.pyvalidator/index,_templates/, the Quick-path + Conventions prose) now lives in a personal, public canonical repolesnik512/planning-convention(live, tag1.0.0). Each consuming repo records the version it last applied inplanning/.convention-version. To adopt or update, an agent reads the canonical repo'sAPPLY.mdand applies the delta — verbatim copy for the clean files (index.py,_templates/), judgment-merge for the files that mix convention with repo-specific content (justfile,CLAUDE.md, the README portable block) — then verifies withjust check-planningand opens a PR.Chosen over Copier / a published package / pre-commit because the convention spans mixed files Copier can't merge, and an agent handles those intelligently with no new tooling or dependency. Personal (not org) repo so it can be consumed across several orgs.
This PR (modern-di side only)
planning/.convention-version=1.0.0.planning/README.md: the## Conventionsblockquote repointed from "copy this section" to the canonical source +APPLY.mdupdate flow.planning/deferred.md: the sibling-rollout item now describes runningAPPLY.mdagainst each sibling.design.md+plan.md) underplanning/changes/2026-06-25.03-canonical-convention-repo/.modern-di'sindex.py/_templates//prose already equal the canonical1.0.0(the canonical repo was seeded from them), so there's no file churn beyond the marker + pointer.Verification
just check-planning→planning: OKjust test-ci→ 232 passed, 100% coveragejust lint-ci→ cleanjust docs-build→ OKSibling-repo rollout is tracked in
planning/deferred.md.🤖 Generated with Claude Code