feat(principles): propose always-on signals after deep debugging digs
Merged
FU
9d ago+17+17+01234567890123456789-4-4-0123456789
Why
pstack 0.15.23 (cursor/plugins#604) ends deep debugging by proposing a cheap, always-on signal that would have shown the decisive fact at first look. This is the bottom layer of the pstack 0.15.23 stack.
What changed
principle-fix-root-causesgains that rule. A proposal does not authorize adding the signal outside task scope.- The principles reference example and a new provenance section cover it. Manifests move to
0.6.3.
Scope
- The provenance section introduces the full 0.15.23 review. Later layers add their own paragraphs.
Verification
- In a clean worktree of this commit:
validate.pyreported 52 skills and 0 problems, all 15 Node tests passed, and all 120 Python tests passed. - Static only: no live debugging session exercised the rule.