Module controls 

A person’s controls over single tasks: accept, skip, nudge — and cost, what the work used.

What a person decides is recorded where speccoder’s other durable facts are: an acceptance is a commit on speccoder/<feature> (Verdict: attested — a person’s word, never shown as evidence); a skip is a ref under refs/speccoder/skipped/; a nudge is a task note in the state directory that rides in the attempt’s journaled input.

Re-exports

pub use crate::attest::notes::SKIPPED;

Constants

SET_ASIDE

The outcome a run’s set-aside changes are saved with.

Functions

accept_in

accept_with, in the person’s checkout when in_place (accept --in-place): committed with the in-place trailers, then ticked.

accept_with

speccoder task accept T --reason R: a person attests the task is done. speccoder ticks it and commits Verdict: attested.

changed_files

The files commit changes against its parent, repository-relative.

cost

speccoder report --cost: tokens per task — every attempt recorded in git, the passing one and the saved ones — plus convergence, priced when [model] states prices.

drop_set_aside

speccoder task drop TASK: every change set aside before the task’s runs, discarded.

is_set_aside

Whether a saved attempt holds changes a run set aside (0.1.0 saved them as interrupted, with this reason).

nudge_with

speccoder task nudge T "note" (or --clear): a person’s note for the task’s next attempts, journaled with them.

restore

speccoder task restore TASK: the changes set aside before the task’s run, committed onto speccoder/<feature> as the person’s own — merged three ways when the branch moved since, refused when they conflict.

rule

speccoder task rule <task> --tests-right --reason …: a person rules that the tests of a held attempt are right — the flagged alternative is not what the spec allows. The ruling is bound to the alternative’s digest; the next run of the task judges the held attempt again from the journal and ticks it with the ruling recorded.

skip

speccoder task skip T --reason R (or --undo): the task is neither done nor attempted; the feature loop passes it by, and what depends on it stays blocked.

skipped

Skipped tasks of feature with their reasons.