You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: sync .metaspec/README.md for documentation consistency (v0.6.8)
CRITICAL BUG FIX: Documentation inconsistency after metaspec sync
Problem:
- metaspec sync only updated .metaspec/commands/
- Did NOT sync .metaspec/README.md
- After sync: commands use new naming (metaspec.evolution.*.md)
- But README referenced old naming (/metaspec.proposal, etc.)
- Result: Documentation contradicted actual files
Impact:
- Severity: CRITICAL - Misleading documentation
- Affected: All speckits using metaspec sync from v0.6.2+
- User confusion: Follow README but commands don't exist
Fix:
- Added Step 7.6 to sync.py: Update .metaspec/README.md
- Extract speckit name from pyproject.toml
- Render template with current version
- Updated README.md.j2 template: All Evolution references use new naming
Before (v0.6.7):
- metaspec sync → Updates commands but not README
- README shows: /metaspec.proposal
- User runs /metaspec.proposal → File not found!
After (v0.6.8):
- metaspec sync → Updates both commands AND README
- README shows: /metaspec.evolution.proposal
- Documentation and files consistent!
All 156 tests passing.
Credit: Bug discovered by user reviewing documentation consistency.
0 commit comments