Tracking: deliver lightweight observation views in Desktop #2100

Goal

Deliver three complete lightweight observation views in Desktop: Runtime state, current-Scope Inventory & usage, and This session. Use existing public Server contracts and constrained native operations, and keep the core Memory journey independently usable.

Parent and first-wave delivery: #2099. Product decisions: #1899. Backend observability coordination: #1980.

Sub-issues and PR ownership

• feat(desktop): visualize health and processing observations #2105 — Runtime state. PR 03-A renders existing health/capabilities/processing facts; PR 03-B adds explicit readiness and constrained local diagnostics.
• feat(desktop): visualize current-Scope inventory and usage #2106 — Current-Scope Inventory & usage. PR 04-A provides get_stats schema/native/IPC integration; PR 04-B delivers charts, equivalent tables, and coverage/estimate explanations.
• feat(desktop): summarize session requests and copy safe diagnostics #2107 — This session. PR 05-A implements bounded native request observation and safe projection; PR 05-B delivers the page and safe-summary preview/copy.

Each child owns its complete data integration, UI, states, and focused evidence. This tracker coordinates semantics and integration rather than creating a separate unassigned frontend workstream.

Dependencies and parallel work

• feat(ops): expose structured personal Server lifecycle operations #2116 supplies read-only local installation/service facts, including when HTTP is unavailable; lifecycle actions belong to feat(desktop): guide local Server setup and lifecycle management #2117. Observation pages must not become a second installer or service controller.

• feat(desktop): establish the shared application layout and navigation #2102 owns the Observation container, tabs, reusable presentation, and navigation conventions. Child adapters and isolated components can start before all layout details finish.

• feat(desktop): integrate Server discovery and operation compatibility #2101 owns operation compatibility, deployment/Principal isolation, and readiness behavior behind the UI. Coordinate its interfaces before exposing actions.

• feat(desktop): complete the connection-to-Scope journey #2103 supplies the exact active Scope; statistics must not silently broaden the selection.

• refactor(desktop): replace the custom OpenAPI-to-Rust schema mapping #1896 owns generation behavior. feat(desktop): visualize current-Scope inventory and usage #2106 owns its reviewed operation addition and consumption; agree on generated outputs rather than waiting for the whole generator issue.

• Reuse existing public capabilities/statistics contracts. feat: establish operational visibility and end-to-end diagnostics #1980 owns backend observability improvements; unsupported later capabilities are not first-wave promises.

• Required platform diagnostics and installed acceptance belong to build(desktop): deliver signed Windows preview packages #2108 and build(desktop): qualify signed and notarized macOS packages #2109; feat(desktop): implement optional Linux native integration #2110/build(desktop): package and qualify the optional Ubuntu Desktop preview #2111 provide optional Linux coverage. The final release path is build(desktop): publish Desktop and local runtime installation artifacts #2112.

Shared acceptance criteria

• A newly provisioned personal Server works with an empty SQLite inventory and no model setup. Missing/stopped/broken local services have accurate states and navigation to feat(desktop): guide local Server setup and lifecycle management #2117; independently authorized remote operations remain usable.

• All three pages work from the shared container and expose meaningful unconfigured, unauthorized, empty, loading, unavailable, partial-failure, and recovery states.

• Every view identifies its data source, scope/coverage, observation time, refresh behavior, and units. Connected Server observations and local-machine diagnostics remain distinct.

• Observation access is handled independently: denied observation permission does not disable separately authorized Memory/statistics operations when their compatibility is established.

• Readiness is explicitly triggered with a clear explanation of model/dependency probes. Ordinary view opening/refresh or Memory use does not silently invoke readiness through a hidden native path.

• Processing observations are not Scope completion, backlog, or ETA. Historical failure and later success are not misrepresented as proof of incident recovery.

• Inventory is a current snapshot; missing usage remains unknown. UTC periods are correct, and recall-token estimates are not billing savings or quality scores.

• Session measurements state whether they represent HTTP requests or user operations. Bounded collection preserves cancellation and business results and distinguishes unknown writes from definite failures.

• Diagnostic summaries are allowlisted at the native boundary and exclude content, queries, credentials, raw endpoints, identity/Scope IDs, private paths, and raw exceptions. Preview and copying are explicit.

• Switching connection/Scope cannot display old private observations. Public process-level and current-Scope data are labelled according to their real coverage.

• English/Chinese, keyboard/focus, accessible labels, equivalent chart tables, small-window behavior, and scaling are covered in child PRs.

• Integrated behavior is exercised with actual Server/native outputs and final installed packages on the declared platforms. Static sample data or mock success does not close this tracker.

Delivery priority

Windows 11 x64 and macOS Apple Silicon/Intel are required for #2099. Linux #2110 and #2111 are optional, owner-driven work under #1428; missing Linux implementation, packaging, or qualification does not block this issue's first-wave acceptance or the Windows/macOS release. Any advertised Linux support requires its own actual qualification.

Non-goals

Global Server/Agent tracing, a required external monitoring stack, persistent business audit history, per-Scope progress invented from process facts, automatic diagnostic upload, and full Dashboard layout/feature parity.

References

• Product scope and focused PR plan
• Static UI prototype
• RFC docs(rfc): propose Tauri desktop control center #1455 and the repository observability contract