auto-verify

Routing an alias invocation to a canonical workflow router requires a thin shim that forwards verify requests while preserving user flags and context. This prevents logic duplication by delegating directly to the full auto workflow.

Preserving command flags when forwarding verify requests is handled by the alias shim, which captures parameters like --auto, --loop, and --model before delegating to the canonical auto workflow for execution.

An alias shim in workflow routing acts as a lightweight intermediary that intercepts specific command invocations, resolves context, and immediately loads a detailed workflow without duplicating operational logic across environments.

Yes, using a verify routing shim requires the existence of detailed auto workflow sources. The shim resolves context and SPEC paths but relies on the canonical router to provide the actual execution logic.

The best way to handle plugin-local routing for verify commands is implementing a thin alias shim that seamlessly forwards parameters to the canonical auto router, enabling execution across environments without redundant logic.

A workflow alias fails to pass context to the main router if it lacks proper context restoration and SPEC path resolution before loading the full verify workflow. The shim must explicitly preserve flags before delegating.