OverClick 0.3.19

OCL-202: the board records the harness that ran; it no longer decides one.

Removed

• The harness policy: harness_list, harness_recommend and harness_set are no longer published, the Harness policy tab leaves Settings, and no policy is seeded on a new workspace. Which CLI, model and effort run a piece of work is decided where it is launched (in Overclock, its per-task Harness table).
• Cards no longer carry a planned harness: task_create stops filling one, a reopened card is no longer escalated along a policy chain, and task_claim no longer answers harness_divergence or writes an executor-swap entry.
• The plugin's opt-in pre-create guard (enforce_harness), which called harness_recommend. Reinstall the plugin to drop it.

Recorded

• task_claim records what actually runs the card (cli, exact model, effort) and every card read returns it as executor. The effort was already stored; it now shows on the card and the briefing asks for it when a claim leaves it out.
• task_deliver keeps recording the measured usage per model.

Transition (this release only)

• task_create, task_update and subtasks[].harness still accept harness: it is ignored and the answer carries a warnings entry instead of an error. task_list and task_search accept include: ["harness"] the same way.

Data

• The planned harness stored on existing cards and the policy rows stay in the database untouched and unread. No migration in this release.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com