Declared-block schema compatibility policy (plugin version vs consumer CLAUDE.md declarations) #52
Labels
No labels
component:adapters
component:lifecycle
component:qa
component:setup
component:shared
component:worktrees
phase/accepted
phase/backlog
phase/deployed
phase/developing
phase/integrating
phase/planning
phase/qa
phase/requirements
phase/uat
priority:critical
priority:critical
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:bug
type:chore
type:docs
type:feature
type:infra
type:tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jbr870/devwork-skills#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spawned from finding
F-PO-50-2-8(in-scope-deferrable) on issue #50 during decision D-PO-50-2-13.Original scope note: Raised by the SREQ expert panel (Solution Architect): once the suite ships as a versioned plugin, a vN+1 skill can read a consumer project's CLAUDE.md declaration written against vN. Nothing today states who bends — no versioning or tolerance rule exists for the declared-block schemas (
forge:,observability:,uat:,parallel_dev:).Disposition rationale: New normative capability, not a migration touch — needs its own design pass (compatibility direction, tolerance rules, maybe a schema-version marker in the blocks). Not needed for 0.1.0: the #50 cutover rewrites consumer declarations in the same window as the install, so plugin and declarations start in lockstep; drift becomes possible from the second release on.
This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run
/requirements --issue={new-number}to flesh it out before planning.