Skip to content

v1.1.0 — The Inspector gets eyes (+ a scripted path for human rejections)

Choose a tag to compare

@StChiotis StChiotis released this 17 Jun 10:09
· 1 commit to main since this release

Closes a reliability gap seen downstream: the Inspector could pass a change on green tests while the rendered UI was wrong, and a human rejection at the final step had no route back into the pipeline — so fixes degraded to unverified in-place patching.

What's new

👁 Visual verification gate (ADR 102) — a new opt-in Inspector sub-skill, lfe-visual-check, renders the changed UI surface (preview/browser MCP, with a manual fallback), reasons over it, and presents it for a human visual sign-off. It is artifact-free — it saves no image files. A new visual-gate enforcement hook makes that sign-off mandatory: it denies the Inspector→Archivist close of a UI-touching slice until the inspection record carries the human's visual_confirmed + visual_signoff. It is the framework's first unconditional-deny floor (it holds even under warn posture), with fail-safe ALLOW on every ambiguous path so it can never deadlock a legitimate close.

🔁 Human-rejection rework loop (ADR 101) — a rejection at the Inspector's finalization gate now re-enters the Builder through a re-entrant rework loop (typed rework_directive sentinel; up to 5 distinct rounds; orthogonal to the mechanical Cycle Guard). The fix always travels back through the Builder and is fully re-verified; patch-in-place at the final step is structurally closed — src/** is writable only under the Builder persona.

Stays out of your way

Both ship inert on a fresh project: the visual sub-skill is off by default and arms only when a change actually touches a UI file class; nothing persists images; the starter stays a clean [BLANK CANVAS] scaffold. Non-visual work gains no new approval burden.

Under the hood

  • The gate has its own injected-I/O test seam; new typed coordination fields are validated; the enforcement chain + gate inventory are reconciled across every documentation representation.
  • Test suite: 1150 passing / 0 failing.
  • Framework decisions recorded as ADR 101 + ADR 102 in .docs/architecture/framework-decisions.md. See USER_MANUAL.md for the visual sign-off ritual.