Skip to main content

Module regression

Module regression 

Source
Expand description

Why a tick is regression-only: one reason from a closed set, decided by code from the run’s facts, worded once, and carried in the commit’s Regression-Only: trailer and its signed statement.

The reason sits beside crate::verify::Verdict, not inside it, so the verdict’s statements and schemas are independent of it; a tick without a recorded reason reads RegressionReason::Unrecorded.

Structs§

Regression
A regression-only tick’s reason with its one-line wording.
RegressionFacts
The facts a reason is decided from.

Enums§

RegressionReason
Why a tick is regression-only.
SkipCause
Why the acceptance author’s answer was not used: typed, so the reason is decided by code, never by reading a message.

Constants§

TRAILER
The trailer’s name.

Functions§

code_path
A path an author chose, as speccoder shows it: one line, no backticks, at most 120 characters, inside a code span.
decide
The reason, by precedence (highest first): acceptance_off, no_story, no_scenarios, author_failed, author_wrote_none, tests_not_collected, not_red, already_passing — for a task judged by its own acceptance tests (a convergence gap, a quick change); a story task’s reason comes from its progress on the story’s oracle.
detail
speccoder’s words for a skip cause.
parse_trailer
Reads a trailer value back; None when it is not one speccoder writes.
trailer
The trailer’s value: <reason>[ <key>=<value>]… (contracts/cli-json.md).
wording
The one sentence per reason, the same in every interface: the only place a reason is worded.