golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

test(#1139): add phase 6 capstone conformance gate (#1158)

Browse Source
This commit is contained in:
Tom Boucher
2026-06-13 02:12:16 -04:00
committed by GitHub
parent aec3374bc2
commit f116b76128
5 changed files with 125 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/how-to/develop-a-capability.md
View File

@@ -225,9 +225,12 @@ Run the smallest affected tests first, then the full suite before opening a read
```bash
node --test tests/capability-registry.test.cjs
node --test tests/phase6-planning-capabilities.test.cjs
node --test tests/phase6-capstone-conformance.test.cjs
npm test
```
Run the Phase 6 capstone test whenever a Capability adds a `when` key or moves activation logic in a host workflow. It checks that migrated activation keys are resolved through Capability hooks or state, and that Capability-owned config keys stay out of the central schema. If a host workflow must keep core behaviour behind a `workflow.*` key, document why it is core rather than Capability-owned before adding it.
## Keep the docs with the slice
Every Phase 6 slice that changes capability behaviour must update the relevant docs in the same PR. Use this manual for developer-facing Capability authoring facts, use how-to guides for task flows, and use ADRs only for decisions and trade-offs.