chore(profile): point capabilities.spec.file at the real SPEC.md#6
Merged
Merged
Conversation
kit.yaml referenced spec_v3.md, which never existed in this repo (a source-project leftover the brownfield persona test flagged). The kit now has a canonical spec (SPEC.md, merged in #5) — cite that. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LxEwyqF1KjEPpQKqM5tSrv
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.
Summary
One-line follow-through on the v2 spec (#5):
kit.yamlpointedcapabilities.spec.fileatspec_v3.md, which never existed in this repo — a source-project leftover the brownfield persona test flagged. The kit now has a canonical spec (SPEC.md), so the profile cites it, which turns the spec-drift / §-citation checks from a dangling reference into a working gate for the kit's own PRs.Spec citation
SPEC.md §12.2— the kit's own repo treats its spec as live ("the kit now has a spec — this file").What was tested
kit.yamlparses;capabilities.spec.fileresolves to a file that exists at repo root.Risk and rollback
Risk: low — configuration pointer only.
Rollback: revert the PR.
Docs
Follow-ups
🤖 Generated with Claude Code
https://claude.ai/code/session_01LxEwyqF1KjEPpQKqM5tSrv
Generated by Claude Code