Clarify repair and steering addon usage

[Copilot]

Daily Rig evaluation exposed recurring misuse of repair, steering, and unused defineTool parameters. Existing guidance also reversed the middleware order required for steering to observe repair prompts.

• Addon guidance

  • Document repair as a bare addon with maxTurns configured on the agent.
  • Correct ordering to [steering(), repair].
  • Document custom warnings via steering({ message }).
  • Add API JSDoc for IDE discoverability.

• Strict TypeScript handlers

  • Recommend destructuring only used tool arguments or aliasing unavoidable bindings with an underscore.

const check = agent({
  maxTurns: 3,
  addons: [
    steering({ message: "Return valid JSON now." }),
    repair,
  ],
});

• Fixes [rig-tasks] Daily rig evaluation — 2026-07-24 — 5/5 passed #89

[pelikhan]

@copilot make repair a function as well (that takes { maxTurns:... }) as options so that it matches steering and is less confusing.

[Copilot]

@copilot make repair a function as well (that takes { maxTurns:... }) as options so that it matches steering and is less confusing.

Implemented in 0d63766. repair is now an options-based factory (repair({ maxTurns })), with callers, tests, samples, and guidance updated.

[pelikhan]

@copilot keep maxTurns as an agent level option, remove option maxTurns from "repair" options.

[Copilot]

@copilot keep maxTurns as an agent level option, remove option maxTurns from "repair" options.

Implemented in ed0541c. repair() is now zero-argument, and maxTurns remains on the agent spec (with the existing call-time override). The addon-level option and budget metadata were removed, and callers/docs were updated.