Module review 

speccoder review: the person’s review of the spec, one requirement at a time. A decision — approved, or changes requested with a comment — is bound to the exact line it was made on, and names who made it; when the line changes, the decision lapses. It is recorded in review.json beside the spec, to commit and share like the spec itself. The model never writes it (crate::tools::paths::REVIEW_FILE).

Structs

Snapshot

The review records under root’s units, as they are before a hosted skill runs: it must not change them, nor leave one in a unit it creates.

Functions

answer

speccoder review answer Q1 "…": writes the person’s answer where the question was — the marker replaced by the answer, nothing else touched.

decide

speccoder review approve|request|clear [ID…]: records the person’s decision on the requirements named (none: every one not approved on its current wording) and writes review.json. request needs a comment.

edit

speccoder review edit FR-003 "…" [--approve]: the person rewords a requirement — its line keeps its identifier, its decision lapses (or is approved on the new words with approve).

report

speccoder review: every requirement and its review.

restore

Puts back every record that changed since before, and removes one in a unit that appeared since; the paths restored.

snapshot

The records as they are now.

summary

The review without its git reads (changes, history): what the inbox needs, per feature, on every refresh.

totals_of

The review state of the feature in dir (project-relative) under root; None when the format has no requirement identifiers or the spec names none.