remote-state-machine-guardrail

To audit remote state-machine documentation before a commit, run a pre-commit guardrail that synchronizes canonical state machine docs with code changes, validates transitions, and records unresolved product tradeoffs under 待讨论取舍.

A remote surface state-machine guardrail is used to align canonical documentation with implementation changes affecting attach/detach/use/follow state predicates, routing decisions, queue gating, and headless lifecycle progression before changes are committed.

To detect dead or half-dead user states in a state machine, apply an audit guardrail that validates transitions against current behavior, identifies unreachable states, and fixes bug-grade issues found during the documentation synchronization process.

You should run a state-machine documentation audit after your implementation stabilizes and before committing changes to remote-surface state-machine logic carriers, ensuring documentation reflects current behavior and unresolved tradeoffs are recorded.

You document unresolved product tradeoffs for state transitions under the 待讨论取舍 section in the canonical remote-surface state machine documentation file, preparing them for review before the final commit.

Yes, you can use this guardrail for headless lifecycle progression changes, as it explicitly audits and aligns documentation for routing decisions, queue/dispatch gating, and prompt/modal state transitions across code and docs.