refit

Refit

Refit surveys the environment the agent worked in — not the code it produced (review and verify own that) and not one launch run's lessons (the sediment pass owns that). Every kind of work leaves friction behind: a ralph loop that kept tripping on the same check, an autopilot run that stalled waiting for a signal, a debugging session where the decisive output was never captured anywhere. OMC instruments all of it. Refit reads the instruments and converts recorded friction into environment changes, so the next run starts in a better yard.

Evidence first

The survey starts from OMC's instruments, not from a checklist. Read before asking the user anything:

• trace_timeline / trace_summary — where turns stalled, repeated, or fanned out wastefully
• omc session friction report — friction the session recorded about itself
• .omc/logs/ and session state — errors, retries, swallowed failures
• plan notepads .omc/notepads/*/issues.md and problems.md — problems that accumulated across a plan
• the repo's own check surface (package.json scripts, CI workflows) — read before proposing any new check, because a check that exists but sits unwired or silently broken is the finding, not a reinvention

Findings emerge from what the data shows. An empty survey is a valid result and is stated plainly; an invented finding is the same violation as skipping the survey. A repo with no wired automated checks is itself a finding, not a neutral default.

Four fix-owner surfaces

Every finding names the surface that owns its fix. A finding that fits no surface is declined, explicitly and with the reason.

1. Deterministic check — the failure was mechanical: a fixed syntactic pattern, a banned API, an import shape, a file-location rule. The fix is a lint rule, hook, or CI job — whichever the repo's existing guardrails make cheapest. Default to building the check over writing the rule.
2. Steering surface — the failure was a judgement call no guardrail substitutes for: cross-file consistency, matches-surrounding-style. The fix lands in the matching docs/standards/ volume, or in CLAUDE.md/AGENTS.md within the thin-entry budget the launch sediment pass defines. Navigation pointers over prose.
3. Tool surface — the drag was tooling itself: expensive or token-inefficient MCP calls, missing automation, checks too slow to be run when they matter. The fix lands in .mcp.json, scripts/, hooks, or OMC config.
4. Information surface — the agent needed a signal it could not reach: dev-server logs, service state, third-party readonly access. The fix tees the log, exposes the state, or documents the access path.