ze-verify

Automating repository verification runs lint, unit, and functional tests while reporting outcomes transparently. It triggers the fastest verification path by default and falls back to staged lint and test runs upon timeout.

When repository verification encounters active repo locks, the workflow waits and reads logs to avoid overlapping runs. It does not proceed until the lock is resolved, ensuring a repeatable process that produces a clear result log.

The Ze verification workflow never auto-fixes failures. It always reports every failure with type, test, and error details, prioritizing the main repo log over memory to ensure transparent validation of repository changes.

Handling timeouts during staged verification triggers a fallback to lint and test stages. The workflow initially attempts the fastest verification path, automatically transitioning to comprehensive testing if the initial fast path times out.

Validating staged changes without overlapping concurrent CI runs is supported by handling active repo locks. The workflow waits for locks to clear and reads logs, ensuring changes are validated with a repeatable, transparent process.

Verification prioritizes the main repo log over memory for failure summaries to ensure accurate reporting of every failure type, test, and error. This prevents auto-fixing and maintains a transparent result log for repository changes.