boundary-check

To enforce write boundaries for an active development phase, verify the active phase's allowed_write_paths to ensure all target changes stay within the defined scope. If any target file falls outside, it prevents arbitrary edits and prompts a replan or scope update.

When a file change falls outside the allowed write scope, the workflow halts the part and prevents arbitrary modifications. It then triggers a replan or requests an approved scope update instead of proceeding with the unauthorized edit.

To revalidate the write scope when a workflow phase closes, run the command `python3 scripts/workflow.py run <task-id> --complete --changed-path ...` to ensure all modifications align with the defined boundaries before finalizing.

You should use a boundary check because modifying files directly risks scope creep. The boundary check validates the file list against allowed_write_paths, preventing unauthorized edits and ensuring changes only occur within the approved phase boundaries.

Yes, if target files require boundary changes, you can update the allowed write paths. The boundary check detects files outside the current scope and prompts you to modify the phase or request a scope update rather than blocking the workflow entirely.