Skip to content

Verification evidence — 2026-10-16

Historical snapshot only. Counts, commands and limitations describe that snapshot and do not establish current acceptance. Use current verification.

Core TUI simplification and Release rebuild (2026-10-16)

Scoped Debug verification with scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter RuAgent.Cli.Tests rebuilt the affected CLI and passed all 1,465 tests without failures or skips. This includes header context-meter cells, chat/session/attachment/approval/recovery coverage, removal from help/completion and compact plan progress without a streamed-word break. A subsequent focused run rebuilt the final prompt-recall/autocomplete test edits and passed both tests. The current-documentation and guidance-route guards passed all 15 checks. Logs: artifacts/tui-core-tests.log, artifacts/tui-core-final-targeted.log and artifacts/tui-core-docs.log.

The TUI now omits dedicated activity/todo/change inspectors, file browsing, session tree/rewind/export and token/prompt-history reports. Context metering, Up/Down recall, inline tool/diff details and headless CLI/RPC remain. The release and ConPTY results below predate this simplification; they preserve historical evidence, including inspector commands that are now removed. This scoped check was followed by a Release rebuild and packaged runtime checks, recorded here.

Final verification was scoped to the changed CLI: the runner with -Configuration Release -ProjectFilter RuAgent.Cli.Tests rebuilt and passed all 1,465 tests without failures or skips. build.bat then completed all 11 stages. The flat published Host passed authenticated status/maintenance and acknowledged idle shutdown. The published CLI entered a real ConPTY alternate screen, opened core help/status/session views, refused the removed /stats command and exited with code 0. Its flat assembly SHA-256 matches the standalone CLI publish, and bin/ru.cmd --version reports 0.1.1. Owned probe processes were closed. Logs: artifacts/tui-core-release-qa/cli-release-tests.log, build-release.log, published-host-smoke.log, packaged-tui-smoke.log and ru-version.log under that same directory. No installer, tag, GitHub release or provider generation was created. The full-matrix figures above remain the earlier baseline; the current change used scoped CLI and documentation checks.

TUI Release verification (2026-10-16)

The full documented Debug matrix passed all 6,370 tests across 13 projects, without failures or skips. Full Python verification passed 215 tests with the POSIX process-group test skipped on Windows. build.bat completed all 11 Release stages, producing self-contained win-x64 GUI, Host and CLI outputs. The source launcher now uses the rebuilt flat CLI; its assembly SHA-256 matches the standalone CLI publish output, and bin/ru.cmd --version reports 0.1.1.

scripts/publish_smoke.ps1 -PublishedDirectory verified the flat Host's startup, authenticated status and acknowledged idle shutdown. A ConPTY check of the published CLI opened /activity, /todos and /changes and exited with code 0. The probe needed inheritable console handles for the child executable; earlier probe-only quoting/handle and exit-code-query failures are retained alongside the final passing captures in artifacts/tui-release-qa/. Owned smoke processes were closed. No provider generation, installer packaging or remote release was invoked for these build checks.

An initial full-matrix invocation with -Configuration Release stopped in Broker: 942 passed and Stale_approval_cannot_add_a_session_grant failed. Its fixture sends expected_intent_hash, a test override compiled only under #if DEBUG; Release intentionally ignores that caller-supplied field. No permission rule or assertion was weakened. The documented Debug matrix was then run in full and passed, while the Release artifacts were validated through the build and runtime smokes above.

TUI feed and inspection repair (2026-10-16, scoped)

scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter RuAgent.Cli.Tests -NoRestore built the affected CLI and passed all 1,462 tests. Documentation and route-count guards passed all 15 tests; git diff --check passed. Focused red/green logs and the final CLI log are retained under artifacts/tui-repair-qa/.

Regression checks reproduce sentence splitting on silent metadata, a worker-thread retry leaving its superseded answer visible, and document paging scrolling the conversation behind the panel. Additional checks cover durable-text repair without dropping tool rows or earlier turns, late tool outcomes updating in place, session inspection reset, plan replacement and bounded long-message replay. The outcome fixtures distinguish a run status from the tool's typed completion state; durable tool ordering remains proposal order.

Native checks used a real Windows ConPTY, isolated temporary profile and QA workspace, and the user-authorized saved provider. Three completed provider turns used a two-item todo/read task and a short Markdown table/code reply. The first exposed a missing streamed head; subsequent checks verified full-text recovery. Activity and Todo panels opened during streaming, the plan reached 2/2, and 120×36 → 90×28 → 120×36 resizing preserved the session. Raw terminal captures and emulator reconstructions are local-only under artifacts/tui-repair-qa/; they are separate evidence from the Terminal.Gui driver-buffer tests, not native screenshots. An intermediate recovery capture exposed visible ANSI escapes, corrected by the same stripping used for normal transcript rows. The initial console probe inherited the tooling shell's NO_COLOR/dumb-terminal settings and exercised sequential output; interactive acceptance used valid console handles and explicit terminal settings.

These checks do not establish full GUI feature parity: the new inspection panels cover received activity in the current connection, without historical activity replay or background-process control. These scoped checks initially preceded the follow-up Release build recorded above, which updates the source launcher's binary. No installer or remote release was published. Owned QA consoles and hosts were closed.