phrazzld/ci

/ci

Confidence in correctness without turning local work into a Docker tax.

Harness Kit's canonical gate is:

cargo run --locked -p harness-kit-checks -- check --repo .

The gate is implemented in Rust at crates/harness-kit-checks/src/ci_check.rs. Dagger may exist as a legacy or experimental runner, but it is not the default local gate, not required for pre-push, and not the source of truth for shipping this repo.

Modes

• Default: audit the gate surface, fix mechanical gaps, then run the Rust gate.
• --audit-only: produce audit report and gap proposals; do not run gates.
• --run-only: skip audit, just drive the Rust gate green.

Stance

1. Rust owns the gate. Add or remove default gates in crates/harness-kit-checks/src/ci_check.rs. Do not add default CI behavior through Dagger, shell glue, or provider YAML.
2. Fast enough to use. A default local gate that routinely takes many minutes for harness/docs changes is a design failure. Keep expensive, networked, mutation, browser, provider, and experimental checks opt-in or path-scoped.
3. No quality lowering. Removing Dagger is not permission to remove the invariant. Preserve meaningful checks by moving them into direct Rust functions or narrowly scoped commands.
4. Act, do not propose. Mechanical strengthenings are applied directly. Escalate only when the choice is product scope, not CI plumbing.
5. Fix-until-green on self-healable failures. Formatting drift, stale generated docs/index, and trivial lints get fixed. Logic failures get a precise diagnosis.

Delegation Judgment

For substantive gate-policy changes, delegate on judgment per the shared Roster contract: native subagents by default; when the decision is architectural or risky, add a cross-model critic or scoped roster lanes with lane handoff prompts. See harnesses/shared/AGENTS.md (Roster).

Local lane guidance: Each lane states responsibilities, context boundary, output evidence, and lead verification. Direct work is limited to mechanical repair and emergency preservation. The lead owns synthesis.

Audit

Check the live gate surface:

• Root contract names cargo run --locked -p harness-kit-checks -- check --repo ..
• .githooks/pre-push routes through harness-kit-checks git-hook pre-push.
• git_hooks.rs uses changed-path classification and calls the Rust gate for source/harness changes.
• ci_check.rs contains the default lane list.
• Generated docs/index are current after skill/docs/backlog changes.
• Dagger references are legacy/optional only, never mandatory local closeout.

Run

Run:

cargo run --locked -p harness-kit-checks -- check --repo .

If red:

• Fix deterministic generated drift.
• Run focused tests for the failing Rust module.
• Re-run the aggregate gate.
• Stop after three self-heal attempts per gate and report the exact failing command, file/path, and likely cause.

Output

Report:

• Audit: gaps found, severity, what was strengthened, what was deferred.
• Run: gate command, pass/fail, self-heals, escalations.
• Final: green/red, residual risk, and any deferred heavyweight checks.

Never claim green from Dagger alone in this repo.