enhance(cli): walk a repository to a result in four commands

[luuuc]

The bench instrument now walks a repository from a github handle to a measured result in four commands, with nothing typed that it already knows and no arithmetic left to the person running it. Every stop says what happened, what comes next, why, and the one command that moves it.

Problem

Driving one repository through one cycle took six commands, one of which did not exist. sense-lab report, sense-lab harvest and sense-lab board were printed as instructions and answered unknown command. Twelve paths were typed by hand across probe and two score calls, nine of them values the crank was holding at the moment it printed the instruction, and the command it printed named a scenario file that cannot exist because the run tree is not committed. Two files had to be hand written, cells.json and the bench that declares what a repository is measured on. The delta, which is the number the whole instrument exists to produce, was left as a subtraction in the operator's head. Four stops printed no next step at all, and the position page ran to 30KB, reprinted after every phase.

Underneath that was one inversion. The instrument did the hard, irreversible things unassisted and correctly, then handed over the clerical work.

Worse, a check could not refuse. The preflight phase had a single verdict, so when it found no bench file for a repository it wrote sixty lines explaining why that was fatal, emitted the only verdict it had, and the loop advanced into the phase that spends money against a matrix no file declared.

Summary

One verb walks the flow and one verb spends, with the paths, the arms and the arithmetic derived rather than typed. A phase that finds something wrong can now say so and stop the loop.

Changes

The flow

• sense-lab next <repo> admits an unknown repository or advances a known one, printing five plain stages, a line as each stage starts with its clock and its wall, and a four part stop
• sense-lab pay <repo> runs the paid cells the bench declares, checks each pair is a measurement, scores both arms and states the gap in words. Six refusals happen before anything spawns
• sense-lab why <repo> is the whole record, and sense-lab help concepts defines the vocabulary the pages deliberately avoid
• repo and run are deleted. run spawned a single unisolated session and took no subject, so a tree built with it carried arm names and no arms

Safety

• Preflight gains a refusing verdict with its own standing and exit code, so an undeclared matrix stops the loop before the money instead of after it
• cells.json is written after every cell, and a second paid run into a directory that already holds one is refused by name, because an interrupted matrix that left nothing naming the burned arm is how a later pass pairs it
• Spending narrows to the paid cell alone. Judging a result spends a model call on an artifact already on disk, so those phases are driven rather than held back
• The checkout is held at its pin on every invocation rather than only the first, so a phase cannot run against a tree that drifted

Output

• Numbers are stated with the bar and the direction, never as a bare recall or a delta
• No phase name and no verdict token reaches the four commands a person walks the flow with, and a test enforces it
• Admission writes a starter bench file, checked against the resolver, so what a repository is measured on is decided by editing rather than authoring

Architecture Highlights

• Three new pure packages: stage maps the eleven phases onto five named stages, say turns a scored pair into a sentence, ask is the only place the binary waits for a person
• The confirmation lives at the command boundary and never between two phases. Every command takes -yes, and a caller with no terminal and no flag is refused rather than assumed either way
• Tests walk the phase graph rather than restating it, so a phase or a verdict added without words fails instead of printing a blank line
• position reports what kind of act moves a repository; the verbs live in one function in the command layer, so a pure package cannot go stale when a command is renamed

Breaking Changes

⚠️ sense-lab repo and sense-lab run are removed. repo is replaced by sense-lab next <repo>, which admits and advances. run has no replacement by design: a paired cell is produced by sense-lab pay, and a single unisolated session is not a measurement.

Test Plan

• sense-lab next <handle> clones, indexes and stops with a bench file to review
• sense-lab next <repo> walks the stages and stops at the money with the command that spends
• Declining the confirmation leaves no clone, no record and no phase run
• A repository with no bench file cannot run a phase, and the refusal names the file to write
• A second sense-lab pay into a directory holding a record is refused and the record is unchanged
• An interrupted paid cell records what it burned, and the agent's process tree dies with the binary
• A drifted lab clone is put back at its pin before anything is dispatched
• No page prints a command this binary does not have
• make ci passes: coverage gate, lint, complexity ledger
• make smoke passes

[codecov]

Codecov Report

❌ Patch coverage is 94.97863% with 47 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
lab/internal/cli/paycmd.go	91.55%	14 Missing and 11 partials ⚠️
lab/internal/cli/nextcmd.go	94.79%	10 Missing and 4 partials ⚠️
lab/internal/cli/job.go	86.20%	2 Missing and 2 partials ⚠️
lab/internal/cli/starter.go	97.89%	1 Missing and 1 partial ⚠️
lab/internal/status/render.go	71.42%	1 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!