concept-guardrails

# Concept Guardrails Focus: do existing specifications state module contracts clearly and correspond to facts and derived maps? Run only on explicit `$concept-guardrails` invocation. The workflow adapts [wyx v0.26.0](https://github.com/jlifyio/wyx) under MIT (`LICENSE.upstream`); specifications use this repository's Jackson dialect while runtime scripts retain upstream behavior. ## Authority Model - `CONCEPT.md` defines purpose, state, actions, and operational principle; optional notes hold application context. - `SYNCS.md` records app/include/sync coordination for application purposes and scenarios; when/where/then define rules and `// flow:` groups them. - `PIPELINE.md` records sources, stages, outputs, invariants, triggers, and data boundaries without replacing synchronizations. - `ARCHITECTURE.md` is a derived navigation map. Product dependencies come from the overall PRD, not synchronization edges. - Backfill reconstructs evidenced contracts from implementation; drift compares implementation with contract. Neither proves fitness for purpose. **Synchronization may restrict behavior, never extend the contract**: flag violating coordination during backfill rather than legitimizing it. Coverage does not prove design correctness; accurate maps do not prove code conformance. Label inferred purposes; an ideal OP cannot justify a defect. ## Modes Use `$concept-guardrails <mode> [path-or-description]`. A path means backfill, a description means create, and no argu...