Summary

Change risk level

• P0 — Low risk: copy, style tweaks, defaults, local display conditions, test assertions. No Runtime/API/persistence contract changes.
• P1 — Medium risk: shared state, business logic, persistence, cross-component interaction, Runtime request parameters, shared components.
• P2 — High risk: Daemon/Runtime, protocol, database migration, process management, service configuration, build/packaging, release pipeline, or Web/Desktop parity changes.

Verification

• Targeted checks for the changed files / closest tests
• pnpm typecheck for affected packages (TypeScript changes)
• Module tests for affected areas (P1+)
• Production build (only when touching compile boundaries, lazy loading, assets, or build config)
• Service restart + health check (P2 daemon/runtime changes)
• Web/Desktop parity checks (shared UI, Bridge, or packaging changes)

Actually ran:

Intentionally skipped, and why:

Web / Desktop parity

• This change does not affect Web/Desktop parity
• General capability implemented once in shared Web/Daemon code (no per-bridge forks)
• Platform-specific entries are hidden when the capability is unavailable (no silent no-op buttons)
• The same flow was checked on the other platform, not only the one where the issue was reported

Checklist

• Focused change — no unrelated refactors or fixes mixed in
• Docs updated in the same PR if user-visible behavior changed
• No .runtime/, credentials, Codex sessions, build caches, or user data committed