Skip to content

Verification evidence — 2026-10-14

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

Workspace maintenance (2026-10-14)

Removed 9,694 obsolete generated binary files (8,321,298,592 bytes) from historical publish copies, superseded local release archives and native installer fixture setup directories. The exact removal manifest is local-only at artifacts/cleanup/obsolete-binaries-20261014.json. Logs, acceptance reports, checksums, the current release, compiler tools and source-tree publish outputs were retained. Binary paths in earlier verification entries describe the original checks; obsolete payloads at those paths are no longer retained.

The scoped source changes accumulate grep statistics per batch and extract CLI input/run-state helpers. They do not change permissions, contracts or chat behavior. No runtime speed benchmark, full release build or native UI acceptance was performed for this maintenance change.

Scoped verification passed:

  • scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter Broker -NoRestore: 933 passed, including two additional multi-batch statistics/order cases. The initial run before those cases were added also passed all 931 tests.
  • scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter RuAgent.Cli.Tests -NoRestore: 1,427 passed; the changed CLI and its dependencies built successfully.
  • pytest tests/test_current_documentation.py tests/test_guidance_route_counts.py -q: 15 passed.
  • git diff --check: passed.

CLI model usage refactor (2026-10-14)

Extracted header metadata lookup from the chat orchestration into ChatModelUsage, with explicit model-selection inputs and an injectable catalog reader. Retained-run context windows, unknown selection handling, rate reset, catalog failure handling and cancellation keep their previous behavior.

scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter RuAgent.Cli.Tests -NoRestore built the affected CLI and passed all 1,436 tests, including nine resolver cases. The first build failed because the forwarding function retained an unnecessary async; after that correction, three new test cases failed because InlineData provided int values for a long? parameter. Correcting those values to long produced the final passing run; assertions were retained.

Current-documentation and route-count guards passed all 15 tests, and git diff --check passed. No full matrix, release publish, native UI acceptance or performance benchmark was run for this internal refactor.

GUI title-bar Update shortcut (2026-10-14)

The compact title-bar Update button sits beside the side-panel toggle, before the system caption buttons. It opens General's Updates card, resets its scroll position and checks the selected channel when no check/download is in progress. Source builds show their existing installation guidance. The shortcut never starts installation; the existing explicit install/restart flow remains in use. The action group's DPI-aware non-client passthrough region follows layout.

dotnet build gui-winui3/RuApp.csproj -c Debug --no-restore passed with zero warnings/errors. scripts/test_dotnet.ps1 -Configuration Debug -ProjectFilter gui-winui3 -NoRestore passed all 1,423 tests. The initial test run found an off-scale literal corner radius (1 failed, 1,422 passed); using AppMicroPillCornerRadius corrected it without changing assertions. Documentation/route guards passed all 15 tests, and git diff --check passed. The subsequent build.bat Release build completed all 11 stages and regenerated the self-contained flat publish directory at gui-winui3/bin/Release/net10.0-windows10.0.26100.0/win-x64/publish. Log: artifacts/gui-titlebar-update-build.log. Native visual/click/DPI acceptance and release installer packaging were not run for this shortcut.

CLI uninstall and download feedback (2026-10-14)

Added the registered CLI uninstall shortcut, a one-command bootstrap example, and interactive download progress for bootstrap/update. Registry/path validation binds removal to the calling CLI installation. The embedded worker waits for the exact parent process, honours request revocation and rechecks registration before opening the native confirmation wizard. No process is terminated by the helper and no profile deletion or direct PATH editing was added.

The CLI Debug suite passed all 1,444 tests (eight uninstall/progress cases). After extending bounded error reporting, those eight cases passed again under the shared matrix lock. Registration tests use private fixture paths; the worker cancellation test never launches an uninstaller or reads live registration. Documentation/route/distribution guards passed 18 tests. PowerShell parser checks passed for bootstrap, worker and the one-line example. git diff --check passed.

Self-contained win-x64 CLI publish passed; log: artifacts/cli-maintenance-publish.log. The published executable's uninstall --help returned 0. No live installation was removed, no native successful uninstall or terminal visual acceptance was performed, and no new public release was published. Public 0.1.0-preview.1 predates this CLI command.

About and conditional GUI update action (2026-10-14)

Settings now has General, Models & Providers and About tabs. About owns the version, source/installed build label, Windows architecture, repository link and update controls. The title-bar shortcut starts collapsed and is shown only after the selected channel yields a newer compatible release. Channel changes and failed/empty checks clear availability. Installed Desktop checks at startup and every 30 minutes, with a 30-second check deadline and no automatic installation; source builds do not poll. Disposal stops the timer and cancels pending checks.

The Debug GUI build passed with zero warnings/errors; the GUI project matrix passed all 1,426 tests, including three About/availability/lifetime contracts. The first matrix had 1 failure / 1,425 passes because a provider-navigation contract read only SettingsView.xaml.cs after navigation moved to a partial. Using GuiSource.ViewText("SettingsView") restored complete class coverage and kept the provider-entry assertions unchanged. After binding checks directly to the displayed channel, the final GUI matrix also passed all 1,426 tests. Documentation/route/distribution guards passed 18 tests; git diff --check passed. Native About/indicator visual acceptance and live background release checks were not exercised in this scoped verification.

The subsequent combined build.bat Release build completed all 11 stages and regenerated the flat GUI/CLI/Host publish tree with the pending maintenance features. Log: artifacts/about-cli-maintenance-release-build.log. This is a local self-contained build; no new public installer release was published.

Product packages and explicit updates (2026-10-14)

Workspace-only native installer checks passed for both products: install, locked-file refusal, helper handoff, upgrade with owned-file cleanup, unowned-file preservation and uninstall. Fixtures include spaces and a trailing separator in the install directory. The test build has a separate AppId and no uninstall registration, shortcuts, user PATH changes or GUI launch. Evidence: artifacts/release-verification/native-local-final.log and its private acceptance.json. Synthetic old markers test installer mechanics; they are not old-release binary compatibility evidence.

The packaged CLI checked the real GitHub release API and defaulted to Stable; no newer compatible release was available. Live asset replacement awaits a published successor. Production install/update/uninstall, registry/PATH behavior and profile preservation passed on the disposable Windows runner in release workflow 38553202482. Both packaged Hosts passed version/protocol and idle-shutdown smokes. CLI upgrade acceptance uses a synthetic older marker with the candidate's binaries, so it does not prove compatibility with an older published release. Native GUI click/restart and Authenticode/SmartScreen acceptance remain unverified.

The public prerelease v0.1.0-preview.1 targets commit 4d197228 and contains five assets: Desktop/CLI Setup executables, Desktop/CLI ZIPs and SHA256SUMS.txt. The unauthenticated GitHub API exposes its CLI installer, digest and canonical download URL. No Stable release is published yet. Initial hosted failures exposed a missing ripgrep prerequisite, stripped PowerShell module paths, a delayed glob deadline timer, missing runtime packs before a fresh GUI clean, and PATH separator loss. Those issues were fixed before the final green pipeline; resize and ConPTY cleanup fixtures were also made independent of transient layout/file locks.

Initial failures were retained: a TUI resize timing check passed alone and in the rerun; maintenance fixtures initially raced their synthetic approval rows with recovery, replaced an unsupported Host lifetime, or accessed an already disposed provider. Fixtures now isolate pending state and capture the tracker before shutdown. The handoff fixture now awaits its owned child before cleanup. A local-only Inno preprocessor flag initially used the wrong unary operator; conditional compilation was corrected before native acceptance. The first packaged-host probe used process_id; it now checks the actual descriptor pid. No product policy assertions were weakened.

See distribution and updates for package ownership, channels, recovery and commands.

Combined GUI fixes before integration (2026-10-14)

The streaming/retry, session replay ownership and inline activity context changes below were checked together before commit/push:

  • Entire GUI Debug suite: 1,423 passed / 0 failed / 0 skipped (artifacts/gui-fixes-final.log).
  • The canonical Release package was already built from this GUI implementation by the 11/11 inline-activity build recorded below. This integration check did not repeat the 12-project matrix or native/provider acceptance.

Inline activity context (2026-10-14)

Tool context such as search queries and website names now shares the activity header row. The header stretches to the transcript width; context takes the remaining column and uses one-line ellipsis. Header labels and metadata are also one-line and bounded; tooltips expose their full text. Thinking, edit and terminal detail blocks retain their existing explicit expansion behavior.

  • Debug GUI build and 36 focused checks passed / 0 failed (artifacts/gui-inline-activity-green.log), covering activity bindings, same-row context, single-line overflow/tooltips and transcript typography.
  • build.bat: 11/11 stages passed, canonical publish updated (artifacts/gui-inline-activity-build.log). Documentation guards: 15 passed; git diff --check passed.
  • The first check attempt built the GUI but failed compiling the new test with CS1503: the XML helper accepts XDocument, not XElement. Corrected the test to pass its owning document before the successful run (artifacts/gui-inline-activity-tests.log).
  • The full GUI suite was not repeated for this bounded XAML change. Existing full-suite figures below remain their recorded snapshots. Native resize and streaming appearance still require operator acceptance.

Session replay ownership correction (2026-10-14)

GUI session reads now retain the existing source_run_id wire field. Both open and turn reload use SessionTranscriptBuilder to attach replay by identity and insert an unanswered run's feed after its user message. Partial/activity-only replay preserves the persisted final answer. Legacy histories without identities use ordinal matching only with balanced counts; ambiguous histories keep saved prose rather than borrowing a different turn's feed. No schema or public route changed, and no stored user history is rewritten.

  • Before correction: the greeting + unanswered gold-question reproduction failed because the second run was placed on the first assistant bubble (artifacts/gui-session-replay-red.log).
  • Focused replay checks: 23 passed / 0 failed (artifacts/gui-session-replay-green.log). Includes failed middle/last turns, permuted run order, incomplete replay, missing run data, final-answer deduplication and the actual API parser preserving source ids.
  • Full GUI Debug suite after tightening the legacy matching policy: 1,422 passed / 0 failed / 0 skipped (artifacts/gui-session-replay-full.log).
  • build.bat: 11/11 stages passed, canonical publish updated (artifacts/gui-session-replay-build.log). Documentation guards: 15 passed; git diff --check passed.
  • Evidence is deterministic synthetic history/replay and source wiring checks. Reopening the user's actual session remains native acceptance. A transient failed-attempt answer that was never committed is not durable history and is not reconstructed or invented by this change.

Agent Feed streaming and retry correction (2026-10-14)

Scoped GUI correction after the streaming-motion pass. Activity boundaries and turn completion now drain the deferred 100 ms render as well as queued deltas. Retry snapshots retain earlier model steps and explicitly invalidate failed attempt text in frozen slices and activity split offsets. Grouping publishes final visibility, folded durations and repeated-detail flags without resetting live bindings first.

  • Before correction: 4 failed / 18 passed in the focused reproductions, including lost earlier-step prose, unchanged-feed binding churn and the missing deferred-render drain at the view boundary (artifacts/gui-feed-red.log).
  • After correction: 43 passed / 0 failed focused checks, including a retry after an activity froze the failed answer, reset/replacement coalescing, shorter and longer replacements, and replayed-reset deduplication (artifacts/gui-feed-green.log).
  • Entire GUI Debug suite: 1,414 passed / 0 failed / 0 skipped (artifacts/gui-feed-full.log). This is scoped evidence; the full 12-project matrix above remains the earlier snapshot.
  • build.bat: 11/11 stages passed, replacing the canonical self-contained GUI/backend/CLI publish directory (artifacts/gui-feed-build.log).
  • Documentation guards: 15 passed; git diff --check passed.
  • Tests replay synthetic events through production accumulator, scheduler, segment and grouping helpers, plus source contracts for WinUI timer wiring. Native GUI appearance and real-provider retry behavior remain manual acceptance; the test process does not interact with the user's app.

Hover and state brush fades (2026-10-14)

GUI motion slice 5, the follow-up to the shell pass: the swaps that were still instant now cross-fade. The nav, settings and theme-toggle hovers, the active-nav selection, the composer's attach-image and context-meter hovers, the session rows' action buttons and the title-bar toggle all route through UiMotion.FadeBrush / UiMotion.FadeOpacity. FadeBrush animates a private solid-colour brush per fade, because the theme brushes are shared instances and animating one would repaint every element painted with it; it reads the live colour before replacing the brush, so a fade interrupted by its reverse continues from where it is. Non-solid targets and animations-off readers keep the instant swap.

  • GUI suite: 1,408 passed / 0 failed, with two new contracts (the nav and hover brush fades with no direct assignment left, and the composer/row state fades) plus the module's private-brush rule (artifacts/tui-audit/hover-motion-gui.log).
  • build.bat 11/11 (artifacts/tui-audit/hover-motion-build.log).
  • Hover feel is visual behaviour and needs the operator's eye on the running app.

Theme fade-through and send-button morph (2026-10-14)

GUI motion slice 4, closing the pass. A theme switch now fades the shell out, flips the palette and the title-bar colours at the trough and fades back in: ApplyTheme hands the flip to ApplyThemeCore through UiMotion.SwapContent, and the startup theme still lands instantly (_hasAppliedTheme, before the window is up). The composer's send button cross-fades between the send and stop faces instead of swapping the glyph in place, and only a real face change animates — repeat refreshes re-apply instantly so a refresh storm cannot strobe the button. Both paths fall back to the instant state change with animations off.

  • GUI suite: 1,406 passed / 0 failed, with two new contracts (the fade-through split with its startup guard, and the guarded send-face cross-fade) (artifacts/tui-audit/window-motion-gui.log).
  • build.bat 11/11 (artifacts/tui-audit/window-motion-build.log).
  • The fade and the morph are visual behaviour and need the operator's eye on the running app. Interactive acceptance of all four motion slices (streaming, shell, theme, icon) remains the operator's pass.

Shell motion (2026-10-14)

GUI motion slice 3, built on a new shared module UiMotion (fade-and-lift entrance, fade-and-drop exit whose completion is deferred past the animation, dip-faded content swap, show-once panel entrance; every path returns to the plain state change when UiTiming.AnimationsEnabled is false).

  • The side surface fades out before it collapses. The reserved column space follows the last painted mode (AgentSidePanelControl.CurrentMode) while the fade is in flight, so the chat cannot jump under a panel that is still visible; the collapse and the reserve release happen in the completion, which re-checks the policy so a re-show during the fade wins. The re-show slides the surface back in explicitly, because a hide leaves the mode untouched and the mode-change entrance compares equal.
  • The settings and session-usage overlays fade out with the collapse and the focus hand-back deferred to the completion; a reopen during the fade wins.
  • Screen switches dip-fade through UiMotion.SwapContent with a generation guard, so the newest click owns the content frame (OnNavClick, OnToolsMenuItemClick, NavigateToDiagnostics).
  • The composer's small panels (task list, queued turns, inline status) enter once through UiMotion.SetVisible and collapse immediately, because the content around them reflows anyway and a delayed collapse would race the next show.
  • GUI suite: 1,404 passed / 0 failed, with four new source contracts (artifacts/tui-audit/shell-motion-gui.log).
  • The slice-2 arrival animation is corrected here: a composition Visual has no Translation property (that name is XAML-only), so animating it threw, the guard restored full opacity and the reply arrived without its lift. The entrance now animates Offset — the composition property behind a translation — in both UiMotion and MarkdownBlock.PlayArrival.
  • The slide, the fade and the swap are visual behaviour: they need the operator's eye on the running app, since no headless check renders WinUI.

Streaming chat motion (2026-10-14)

GUI motion slice 2. The streaming reply now parses as Markdown from the first token: ChatView hands the growing text to the block on a 100 ms cadence (UiTiming.StreamTextRefresh), the deferred render is scheduled through a one-shot timer that re-checks message identity and liveness, and the plain-text streaming mode is gone (MarkdownBlock.PlainTextMode and its two bindings no longer exist) — so the end-of-turn settle no longer reshapes the whole reply in one jump. A reply's first text fades and lifts into place (140 ms, MarkdownBlock.IsStreaming, skipped when animations are off or a transcript is reopened from history). Three pulsing dots wait in the bubble for the first token, driven by the previously unused ShowTypingDots and holding a static opacity with animations off (TypingDotsControl, Composition keyframes, no timer). The follow scroll glides with the growing reply unless the reader has animations off; session opens and the new-messages pill stay instant.

  • GUI suite: 1,400 passed / 0 failed, including four new source contracts — the streaming cadence and the deferred render's identity/liveness guards, the short gated arrival, the gated pulsing dots driven by ShowTypingDots, and the follow-scroll gate with the deliberate jump left instant (artifacts/tui-audit/streaming-motion-gui.log).
  • build.bat 11/11 (artifacts/tui-audit/streaming-motion-build.log).
  • The pulse, the arrival fade and the scroll glide are visual behaviour: they need the operator's eye on the running app, because no headless check renders WinUI. Reduced-motion behaviour is contract-checked (every animation consults UiTiming.AnimationsEnabled) but its look stays operator-verified too.

App icon from the wordmark (2026-10-14)

The operator asked for the wordmark's block r as the app logo in the bare style: the mark alone, no tile. scripts/make_app_icon.ps1 regenerates gui-winui3/Assets/AppIcon.ico (16/24/32/48/64/128 as 32bpp BMP frames plus a 256 PNG frame) and the packaged-app PNG set from the same half-cell grid as docs/assets/wordmark.svg; an even cell per size keeps every half-cell a whole pixel, so the small frames stay crisp without anti-aliasing.

  • The .ico was parsed frame by frame with an independent reader: seven frames, contiguous data, exact sizes and doubled BMP heights (structure ok: True). Windows' own System.Drawing.Icon decoded every BMP frame for 1:1 and 4x sheets on dark and light strips, and the 256 PNG frame was extracted and rendered on its own (System.Drawing cannot decode PNG frames, which is why only 256 ships as PNG, as convention expects).
  • build.bat 11/11 (artifacts/tui-audit/app-icon-build.log) and the published RuApp.exe carries the new mark: the associated icon extracted from the exe is the source 32x32 frame pixel for pixel (artifacts/tui-audit/app-icon-exe-check.log, app-icon-from-exe.png).
  • GUI suite: 1,396 passed / 0 failed; Python 212 passed / 1 skipped (artifacts/tui-audit/app-icon-frames.png, app-icon-assets.png for the rendered sheets; they are reconstructed images, not native Explorer captures).
  • The unpackaged app reads AppIcon.ico through the existing <ApplicationIcon> and AppWindow.SetIcon wiring; the store PNG set is only read by a packaged MSIX build.

Faster multi-hue busy wave and green preset (2026-10-14)

The operator asked for the wave to move faster and carry more colours, and for the composer's Standard label to go green. One cycle is now 0.8 s (was 1.4 s) on a 60 ms phase bucket (~17 repaints a second on the 18 ms ticker), and the ramp gained two palette anchors — mint (Ok) and amber (Warn) beside aurora, brand and brand2 — so five hues sweep the row and the wrap segment passes through amber back to green. The preset label takes the green accent (Ok, the tone the user block's prompt chevron already carries) instead of brand blue. Glyph, cell count, spacing and the classic TuiSpinner.WaveText parity reference are unchanged.

  • Full CLI Debug suite: 1,422 passed / 0 failed / 0 skipped (artifacts/tui-audit/wave-fast-cli.log). New guards: one cycle must reach green-, blue- and red-dominant samples (the old three-stop ramp never reached red, so the wider palette is pinned) and the preset cell's foreground must be the green accent.
  • Python suite: 212 passed / 1 skipped (artifacts/tui-audit/wave-fast-python.log).
  • Release build: build.bat 11/11 (artifacts/tui-audit/wave-fast-build.log); launcher smoke passes with the distributable CLI hash matching the publish and the parser failing bounded with exit 1 (artifacts/tui-audit/wave-fast-launcher-smoke.log).
  • The full 12-project matrix was not rerun for this CLI-only tweak; the last full matrix is the composer-wave run above. A rendered filmstrip of the new cycle and the green meta row lives in artifacts/tui-audit/wave-preview.png (reconstructed cells, not a native terminal capture).

Filled composer and balanced busy wave (2026-10-14)

Operator request: bring the prompt back to the opencode-style filled block without the accent rail it once had, and rebalance the busy wave, which read as too heavy after the thicker pass. The reference is the pre-batch composer at d09a4c66: one panel-toned surface (SurfaceRgb) with no frame outline, no rail and no interior prompt glyph, while keeping the multiline editor and the growing height, and moving the preset/model/provider row back inside the block (MetadataRow = 3 at one input row; the meta row follows the draft). The wave glyph changed from ▄ to ▬ (five cells) in the Terminal.Gui footer and in the classic TuiSpinner.WaveText reference, so copy parity holds.

  • Full 12-project Debug matrix: 6,213 / 0 / 0 (artifacts/tui-audit/composer-wave-matrix.log)
  • Python suite: 212 passed / 1 skipped (artifacts/tui-audit/composer-wave-python.log)
  • Release build: build.bat 11/11, 0 warnings (artifacts/tui-audit/composer-wave-build.log)
  • Publish smoke: PASS (artifacts/tui-audit/composer-wave-publish-smoke.log)
  • Launcher smoke: bin\ru.cmd --nonsense fails at the parser with exit 1 and the distributable CLI assembly hash matches the Release publish (artifacts/tui-audit/composer-wave-launcher-smoke.log)
  • The first matrix run failed on RuAgent.Broker.Tests.HelpDocsTests: the user-facing README rewrite had dropped the # Ru Agent heading, so BundledHelpDocsCatalog refused the embedded overview (missing_h1) and every help-docs test failed. The heading is restored under the hero banner (Broker reruns 930 / 0); this regression predates the composer change.
  • Rendered checks were updated with the shape rather than weakened: composer cells assert the panel tone across the whole block while empty and while editing, frame and rail glyphs are asserted absent, the meta row is read through TgComposerView.MetadataRow, and the 20×12 command-overlay test records that the palette strip owns the frame there while the slash dropdown leaves the new fill visible.
  • Documentation follows the change: the CLI README describes the filled prompt surface and the medium block wave, and docs/architecture.md no longer says the metadata sits on a square frame.