Skip to content

Gate v1.15 on one installed end-to-end operator-desk proof #114

Description

@clintecker

Problem

Unit, headless UI, and wheel tests can each pass while the assembled operator workflow is broken. v1.15 needs one repeatable active-signal proof that crosses installation, book discovery, dashboard evidence, command selection, child execution, and refreshed evidence.

Direction

Create a release-gating scenario from a clean installed wheel plus [tui]: scaffold a neutral book, launch the real desk headlessly, assert initial honest states, select a safe real command through the generated picker, observe structured and raw child output, assert the exact verdict, and refresh the DESK model from resulting digest/receipt evidence.

Dependencies

Invariants

  • The scenario uses an installed wheel, a neutral scaffold, and the real CLI child boundary.
  • Assertions observe return codes, typed states, events, files, digests, and receipts; no sleeps or screenshot-only claims.
  • The scenario is bounded, replayable, and produces evidence on failure.
  • No book-specific identity or private fixture enters the package.
  • The v1.15 release cannot proceed without this proof in its trust receipt chain.

Acceptance

  • The scenario fails under seeded sabotage: missing extra, wrong book root, malformed event, child nonzero, changed artifact bytes, stale/wrong receipt, and concurrent launch attempt.
  • The clean path passes on the supported release environment.
  • Failure artifacts include normalized UI state, raw child streams, structured events, and evidence diagnostics.
  • The release workflow consumes the proof as a named accumulated-trust receipt.
  • The milestone cannot close until this issue and all P1 dependencies are complete.

Links

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:ci-cdGitHub Actions, releases, and toolchain imagesarea:tuiTerminal UI, operator desk, and interactive run controlarea:uxUser-facing command behavior and diagnosticsarea:verificationExecutable contracts and artifact verificationenhancementNew feature or requestpriority:P0Critical: public output, data safety, or release integrity is brokentest-layer:L7External repository and release boundaries

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions