workflow-guard

PreToolUse hooks enforce mandatory edit workflows by intercepting Edit, Write, MultiEdit, and NotebookEdit operations. They check for a `.workflow-active` marker file, applying hard gates to ensure governed file modifications.

A PreToolUse hook gates file edits before execution by validating workflow activation states and marker files. It transforms standard operating procedures into strict requirements, blocking unauthorized Edit, Write, MultiEdit, and NotebookEdit operations.

Run the workflow-activate.py script with your current directory as the project root to activate the workflow guard. This generates the `.workflow-active` marker file, establishing session state and enabling automated hook enforcement.

Yes, workflow automation supports auto-activation by default for repositories using PROJECT.md markers. It includes TTL handling to manage stale sessions, ensuring continuous edit governance across active editing workflows.

Yes, bootstrap exemptions are built in for internal guard scripts to ensure safe deployment. This prevents PreToolUse hooks from blocking the initialization scripts required to establish the `.workflow-active` session state.

Stale sessions are managed via TTL handling. When a session exceeds its time-to-live, the workflow guard invalidates the `.workflow-active` marker, requiring re-activation through workflow-activate.py before further file edits are permitted.