feat: gate template source formats before component rollout - #63
Merged
Conversation
dapi
marked this pull request as ready for review
September 6, 2026 23:53
This was referenced Sep 7, 2026
* docs: define component runtime execution plan * refactor: avoid repeating source JSON validation * docs: define durable component recovery execution * feat: add component contract validation primitives * fix: enforce frozen validation and projection boundaries * fix: distinguish historical replay from transition authorization * feat: compose component installations and explicit document transactions * feat: complete component migration and explicit adoption runtime * fix: reject unsupported URI schemes before relocation * ci: fetch legacy ancestry for component migration fixtures * fix: clarify template ownership with compatible renderer v3 * fix: preserve draft links and recognize source projections * refactor: remove duplicate evidence sorting
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.
A CLI predating component support could install an unfamiliar template as a legacy payload. Add a source-format gate shared by init, pull, resolution plans and doctor repair, plus a machine-readable capabilities handshake. The bridge accepts the pinned legacy template f1f04de and declared legacy/v1 sources; unknown manifestless and component sources fail before downstream mutation.
The canonical-source canary also exposed an existing ownership bookkeeping bug: locally adapted files must persist their ownership even when no payload bytes change. Git object reads now ignore local replacement refs, and the canary selects the canonical template independently of the CLI build revision.
Validation at 3b434fd:
This is W1 of #62 and supports dapi/memory-bank#141. It closes neither issue. Release the bridge before the component-aware CLI and template. Custom manifestless sources outside the explicit allowlist must retain their previous CLI or add the declaration and deliberately repin. Release publication, merge and live downstream migration remain outside this PR.