maestro-guard

To set directory-level write boundaries, you configure allowed and denied paths within a workflow guard, which normalizes directory handling and enforces permission-controlled editing across your project.

Project path guard protects directories by applying non-destructive state changes to configuration files, validating hook presence, and warning when protection is configured but not actively enforced.

By managing allowed and denied paths in the guard configuration, you can scope AI assistant edits to specific folders while applying path normalization to ensure consistent directory handling.

The guard supports enabling or disabling path protection while preserving configuration state, so you can toggle enforcement without clearing your established allowed and denied path boundaries.

This warning occurs during enforcement readiness validation when the workflow-guard hook is inactive, indicating that write boundaries are configured but lack active hook presence to enforce them.

The guard requires config-only mutation and non-destructive state changes when managing denied paths, ensuring path normalization and boundary updates occur without modifying existing project files.