Checkpoint 016 · first human findings

Local vision restored

The split works.
The seams are visible.

The first real Game Bar session proved GTC routing, persisted context, replay, and local vision. It also exposed four concrete usability defects and one desktop visibility-policy mismatch.

PASS

Local vision

Game Assist now routes auxiliary vision to local Ollama qwen3-vl:4b. A post-restart Hermes call identified the game and visible quest correctly.

Observed latency: about 78 seconds during this validation run. Warm-path and cancellation behavior still need testing.

PASS

GTC request

An explicit request to use GTC produced visible gtc_search and gtc_scrape steps and a sourced correction. Research intent is routed; ordinary prompts are not forced through GTC.

What the screenshots established

Remembered context affected an answerThe research surface used Recall-derived tracker and campaign context. The run receipt remains trace evidence rather than a first-class chat badge.
Inactive game restored as activeThe widget restores the saved game before live detection and keeps it when detection reports no game. There is no startup policy toggle. Default should be an empty state.
Conversation tail is not anchoredReplay starts at the beginning, and growing/new messages do not reliably keep a user who was already at the tail at the tail.
Sources view resource lookup crashesA dynamic research-plan element looks for NagatoAccent in application resources even though the brush is page-scoped.
Artifact acceptance remains incompleteThe failed screenshot run produced no artifact. A successful GTC run should be used to verify that an artifact opens from its successful tool result and remains scoped to that run.

Isolation finding

Storage
Game Assist sessions live under the isolated game-assist profile.
Runtime
Only the Game Assist gateway was restarted; personal Hermes was untouched.
Desktop visibility
Hermes Desktop intentionally aggregates all profiles, so the Game Bar session appears in its API group.

The recommended desktop policy is current profile only by default, with an explicit All profiles / developer view. This preserves development access without making profile separation look broken.

Recommended issue order

Sources crashSmall, deterministic widget bug with direct test coverage.
Conversation tail anchoringDeferred initial scroll plus tail-preserving streaming updates without yanking a user who scrolled upward.
Inactive-game startup policyAdd Keep last game when inactive, default off, and implement a proper empty state.
Desktop profile visibilityDefault to the active personal profile; expose cross-profile sessions only through an explicit developer control.
Receipt and artifact discoverabilityMake memory use and run-scoped artifacts obvious without requiring trace archaeology.
Local vision hardeningMeasure warm latency, timeout/cancellation, GPU contention, and model fallback. Keep native main-model vision first when supported.

Separate warning

Mnemosyne loads far enough for the vision request, but startup logs report that the plugin has no register() function. Track this separately; it did not block the call.

Next human checks

Retry the same screenshot prompt, test a second warm request, open a GTC artifact from its trace, and confirm a recalled fact's memory.context.injected receipt.

Generated 25 July 2026, Pacific/Auckland. Sanitized, unlisted, noindex, and unauthenticated. No credentials, raw prompts, trace payloads, or local filesystem details are included.