feat(desktop): summarize session requests and copy safe diagnostics #2107

Goal

Show bounded outcomes and latency from this Desktop session and let users preview and explicitly copy a safe diagnostic summary.

Parent: #2100. First-wave delivery: #2099. Work item: F1-05.

PR breakdown

• PR 05-A — Native request observations and safe projection. Define request versus user-operation measurements, bounded retention/reset behavior, latency units, and failure/cancellation/unknown-write semantics. Collect at the native boundary and project an allowlisted summary before exposing data to the renderer.

• PR 05-B — Session page and diagnostic preview/copy. Implement the This session view, clearly labelled outcomes/latency, visible coverage, safe-summary preview, and explicit copy with success/failure feedback.

Dependencies and coordination

• PR 05-A/05-B may project allowlisted Installer/Ops status from feat(ops): expose structured personal Server lifecycle operations #2116/feat(desktop): guide local Server setup and lifecycle management #2117 into a distinct diagnostic section. Reuse the owning operation/status contract; do not create another journal or count download/install/service operations as Server HTTP latency.

• Use feat(desktop): establish the shared application layout and navigation #2102's Observation container. Agree with feat(desktop): integrate Server discovery and operation compatibility #2101 on operation names, context transitions, and identity-check request treatment.

• Coordinate outcome semantics with feat(desktop): complete Memory save, search, and exact-read journeys #2104 and include new native operations from feat(desktop): visualize health and processing observations #2105/feat(desktop): visualize current-Scope inventory and usage #2106 without requiring those pages to finish before collection work starts.

• Follow the repository observability field/privacy contract and coordinate with feat: establish operational visibility and end-to-end diagnostics #1980 without requiring global Server tracing.

• Required installed clipboard/platform behavior is verified by build(desktop): deliver signed Windows preview packages #2108 and build(desktop): qualify signed and notarized macOS packages #2109; build(desktop): package and qualify the optional Ubuntu Desktop preview #2111 provides optional Linux coverage.

Acceptance criteria

• Local setup failures can be explained with safe phase/result and a supported opaque operation reference. Summaries never copy raw installer stdout, paths, endpoint secrets, config, or journal contents; preview/copy stays explicit.

• Every measurement clearly represents either an HTTP request or a user action; identity checks do not silently double-count user actions or mislabel request latency as end-to-end latency.

• Collection is bounded with documented limits and session/reset behavior. Context changes do not leak private data; observation failure cannot change results or suppress cancellation.

• Success, definite failure, cancellation, and uncertain write outcomes remain distinguishable; session observations are not authoritative proof of persistence.

• The native summary excludes memory content, queries, prompts/responses, credentials, raw endpoints, identity/Scope IDs, private paths, and raw exceptions. No whole-state serialization followed by renderer-only redaction.

• Users can inspect the exact safe text before explicitly copying it; copy behavior is exercised in the installed application.

• The page states that it covers this Desktop session, not global Server/Agent tracing. Empty/loading/failure states, English/Chinese, keyboard/focus, small windows, and scaling are usable.

• Regression evidence covers bounded retention, measurement/outcome semantics, sensitive-data exclusion, and collector failure isolation.

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

No global telemetry backend, durable business audit trail, automatic diagnostic upload, or persistent content-bearing request history.

References and delivery rules

• Product scope and PR breakdown; static UI prototype. The prototype uses sample data, not production state logic.
• RFC docs(rfc): propose Tauri desktop control center #1455 and the Desktop delivery plan.
• Keep focused PRs independently reviewable and intermediate merges usable. An internal adapter may land before its page; do not expose incomplete features as operational. Close this issue only after its complete outcome is verified.
• Preserve the reviewed native transport, credential, public API, and context boundaries. Record actual backend/platform execution separately from mocks and CI-only fixtures.