argot-refresh

Argot refresh

Treat a refresh like dependency maintenance, not a blind rebuild. The repository may have changed enough that its corpus scope, paths, and suppressions need review before the next fit freezes them into the shared snapshot.

Keep three concerns separate:

• [exclude] and [detect] shape what the fit learns. Changing them requires a new fit.
• [rules], [[migration]], and mutes shape check policy. They do not train the model, but stale policy can hide useful findings and belongs in the same maintenance review.
• .argot/ is the generated, committed fit snapshot. CI only reads the base branch copy; it never fits or certifies a snapshot supplied by a PR.

Non-negotiable contract

• Work on the accepted/default branch with a clean source tree. If either is false, show the evidence and stop before fitting.
• If the repository has never been fitted, stop and hand off to argot-setup. Refresh maintains a reviewed baseline; it does not replace first-time corpus selection and setup verification.
• Never fit in CI, in the background, or merely because a commit count or age is high.
• Run every audit below read-only first. Do not edit argot.toml, prune a mute, fit, stage, or commit while still assembling the proposal.
• Ask for one explicit confirmation covering the proposed scope and mute changes. A user may accept some rows and reject others.
• Never remove an exclusion or standing mute just because it currently matches nothing; it may be a deliberate future guardrail. State the uncertainty.
• Never claim a hash mute on a still-present file is stale. Argot cannot recover its original hunk from the hash.

0 · Preflight

Run:

argot --version
git status --short
git branch --show-current
argot status --format json

If Argot is missing, stop and point to https://argot.tmonier.com/docs/getting-started/. Read these status fields:

• snapshot.complete and snapshot.committed
• refresh.compatibility
• refresh.recommendation, score, and reasons
• refresh.next_action
• refresh.fit_sha and accepted_sha