Module near_miss 

speccoder.task.near_miss: wrong and permitted variants of a task’s change, to test its acceptance tests.

A judge-side call after a task was verified. It sees the task’s spec and the final contents of the changed source files — never an acceptance test, visible or held-out, so its variants measure the tests independently. It writes near misses (plausible, and wrong about exactly one stated scenario) and, where the spec leaves a choice open, alternatives the spec permits. It has no tools and no say: code applies each variant, runs the tests and counts. The implementer never sees any of it.

Structs

NearMiss

The coded skill.

Constants

CAPABILITY

The capability the skill provides.

MAX_SOURCES

The changed files’ contents the author reads, at most.

Functions

input

The run input: the task’s spec context (the person’s), the changed files’ final contents and the patch (the worktree’s), and how many variants of each kind to write.

policy

What the author is told.

schema

The answer’s schema.

special_case_input

The special-case author’s input: the spec context, the changed files, the change, and the visible reproductions (never a held-out variant).

special_case_policy

What the author is told for a bug task’s special cases: fixes that recognise a reproduction’s literal inputs and keep the old behaviour everywhere else — what a held-out variant with other inputs must catch.