chore(desktop): decide fate of speculative maka.usage and cursor-subscription IPC surface

[Astro-Han]

Summary

Two IPC surfaces have zero renderer/overlay/e2e consumers but are deliberately-built (not accidental) — they need an explicit product decision rather than a silent delete.

1. maka.usage bridge namespace (speculative authority surface)

• preload/preload.ts:935-953 exposes usage.summary/buckets/logs/listPricing/putPricing/resetPricing → main/usage-ipc-main.ts:86-166 handlers + usage:pricing:changed push.
• Zero consumers on main and across all local/remote branches (verified by repo-wide grep). The usage settings page (renderer/settings/usage-settings-page.tsx) uses settings:usageStats (usage-ipc-main.ts:83) via onReload/onUpdate props — not this namespace. usage:pricing:put is the only writer of pricing overrides, so that feature is currently unreachable.
• However, this is the v0 Host surface deliberately exposed by feat(runtime-host): extract Usage/Pricing authority #1596 "Usage/Pricing authority" (tracked under [Tracking] Runtime Host M3 domain ownership migration #1167 M3), with full main-side tests (main/__tests__/usage-ipc-main.test.ts incl. CAS/notification contract). The fix/usage-stats-restyle branch restyles only the renderer page and does not wire maka.usage (its merge-base predates feat(runtime-host): extract Usage/Pricing authority #1596).

Options: (a) remove the maka.usage preload namespace now, keep main-side authority handlers for the planned consumer; or (b) explicitly defer with an owner and delivery plan. Do not silently delete the main-side authority.

2. maka.cursorSubscription OAuth service + 8 channels (experimental, previously shipped UI)

• preload/preload.ts:749; service constructed every boot (main/boot.ts:380); channels in main/subscription-ipc-main.ts:361-411 gated by MAKA_CURSOR_SUBSCRIPTION_EXPERIMENTAL !== '0' (default on, opt-out — oauth/cursor-subscription-helpers.ts:79-80).
• No renderer consumer; OAuthCardId (renderer/settings/provider-oauth-section.tsx:20) has no cursor. A cursor card existed until refactor(desktop): simplify model connection settings #1033 removed it (2026-07-15). main/app-lifecycle.ts:275-282 still migrates the legacy .cursor_subscription_token file, suggesting historical user credentials exist.
• Incidental: cursor-subscription:logout is not gated by the flag (subscription-ipc-main.ts:408-411).

Options: (a) product retired the Cursor subscription — remove service/handlers/preload namespace, with an explicit plan for any migrated credentials; (b) a card is planned — add cursor to OAuthCardId + provider-oauth-section.tsx. Do not delete without the credential-migration decision.

Owner

Product owner (desktop subscriptions) + main process (usage/pricing authority).

Acceptance

• An explicit decision is recorded on this issue; the chosen option lands in a follow-up PR.

[me2seeks]

English

I went through #1596, the current Desktop wiring, and how comparable agents handle Cursor and pricing overrides. My preference would be:

• Retire the current cursor-subscription implementation and do not restore its OAuth card. It is built around an external/private auth pattern and still has no model/runtime consumer, so restoring the card would expose a login that cannot power a usable provider. If Maka later supports the official Cursor Agent CLI or SDK, I think that should be a separate external-agent backend decision rather than a continuation of this OAuth surface.
• Keep pricing overrides as a product capability and track an editable Pricing Settings page. feat(runtime-host): extract Usage/Pricing authority #1596 already makes Runtime Host the eventual Usage/Pricing owner. Since the current window.maka.usage namespace has no renderer consumer, I would remove that speculative bridge now instead of treating its shape as the future M4 contract. The Desktop adapter can expose a narrow renderer interface backed by pricing.query / pricing.mutate once there is a real consumer; the exact preload shape should be coordinated with [Tracking] Runtime Host M4 Desktop-first client adapters #2010.
• Make credential retirement explicit. The cleanup should idempotently remove both the legacy Cursor token file and the shared cursor-subscription credential entries, without importing, refreshing, or otherwise continuing to use them. It should also prove that unrelated credentials are untouched and that rerunning cleanup is safe.

If this direction is accepted, I would split the follow-up work into independently reviewable pieces:

1. remove the Cursor service, handlers, preload surface, boot construction, migration path, and retired credentials;
2. specify the Pricing Settings behavior (four rates, built-in vs override provenance, reset/delete, validation, and revision-conflict reload), with Host adapter wiring coordinated with [Tracking] Runtime Host M4 Desktop-first client adapters #2010;
3. leave any official Cursor Agent CLI/SDK integration to a separate future issue/RFC.

I have not started implementation yet; I wanted to record the product and migration decision before freezing another client interface.

简体中文

我重新对照了 #1596、当前 Desktop 接线，以及类似 Agent 对 Cursor 和价格覆盖的处理方式。我的倾向是：

• 正式退役当前 cursor-subscription 实现，不恢复它的 OAuth 卡片。它基于外部/非公开认证模式，而且仍然没有 model/runtime consumer；恢复卡片只会暴露一个无法驱动可用 provider 的登录入口。如果 Maka 以后支持官方 Cursor Agent CLI 或 SDK，我认为应当把它作为独立的 external-agent backend 决策，而不是延续这套 OAuth surface。
• 保留 pricing override 这一产品能力，并追踪可编辑的 Pricing Settings 页面。feat(runtime-host): extract Usage/Pricing authority #1596 已经确定 Runtime Host 是最终的 Usage/Pricing owner。当前 window.maka.usage 没有 renderer consumer，因此我倾向于现在删除这套 speculative bridge，不把它的形状提前冻结成未来的 M4 contract。等有真实消费者后，Desktop adapter 再提供由 pricing.query / pricing.mutate 支撑的窄 renderer interface；具体 preload 形状应与 [Tracking] Runtime Host M4 Desktop-first client adapters #2010 协调。
• 明确处理历史凭据。清理应以幂等方式同时删除旧 Cursor token 文件和共享 CredentialStore 中的 cursor-subscription 凭据，不再导入、刷新或继续使用它们；测试还应证明不会影响其他 provider 的凭据，并且重复执行清理是安全的。

如果维护者认可这个方向，我建议把后续工作拆成可以独立审查的部分：

1. 删除 Cursor service、handlers、preload surface、boot construction、migration path，并清理已退役凭据；
2. 明确 Pricing Settings 行为（四类费率、内置值与 override 来源、reset/delete、校验，以及 revision conflict 后重新加载），其中 Host adapter 接线与 [Tracking] Runtime Host M4 Desktop-first client adapters #2010 协调；
3. 官方 Cursor Agent CLI/SDK 集成留给未来独立的 Issue/RFC。

我还没有开始实现；我希望先记录清楚产品与迁移决定，再冻结新的 Client interface。

[Astro-Han]

@me2seeks thanks for the thorough read-through — this matches what I was seeing too. Two current-code facts that support the direction:

• feat(inspector): surface the session trace as a workbar tab #2018 (Session Inspector) deliberately reads the AgentRun stream, not the Usage read model, for cost rendering — the renderer's cost surface is converging on the stream, which strengthens the case against freezing maka.usage's shape now.
• fix(ui): clarify the Usage page hierarchy #2024 (Usage page hierarchy) still runs on settings:usageStats, so the maka.usage namespace remains zero-consumer.

Decisions I'd record here:

1. Cursor subscription: retire. Remove the service, handlers, preload namespace, boot construction, and legacy migration path; do not restore the OAuth card. Credential cleanup must be idempotent — remove the legacy .cursor_subscription_token file and the shared cursor-subscription credential entries without importing or refreshing them, with tests proving unrelated credentials are untouched and reruns are safe. Official Cursor Agent CLI/SDK support, if any, is a separate external-agent backend decision; I'd track it as its own issue rather than a continuation of this surface.
2. maka.usage bridge: remove the preload namespace now, keep the main-side authority handlers — they're the desktop wiring of the feat(runtime-host): extract Usage/Pricing authority #1596 Host authority and stay until the M4 client adapter (tracked in [Tracking] Runtime Host M4 Desktop-first client adapters #2010) exposes a narrow renderer interface backed by pricing.query / pricing.mutate.
3. Pricing override stays a product capability — track an editable Pricing Settings page per your follow-up (2) sketch.

I'm good with your three-way split (cursor retirement / Pricing Settings spec / Cursor CLI-SDK deferred to a separate issue) as independently reviewable follow-ups. Owner: desktop subscriptions for (1), main-process usage/pricing for (2)+(3).

简体中文对照

同意这个方向，两点补充事实：#2018 的成本展示走 AgentRun stream 而非 usage read model；#2024 用量页仍走 settings:usageStats——maka.usage 确实零消费者。

决定：

1. Cursor 订阅整套退役（含幂等清理历史凭据），OAuth 卡片不恢复；官方 Cursor CLI/SDK 支持另立 issue。
2. 删除 maka.usage preload namespace，保留 main 侧 authority（feat(runtime-host): extract Usage/Pricing authority #1596 Host 接线的桌面部分），等 [Tracking] Runtime Host M4 Desktop-first client adapters #2010 M4 adapter 用 pricing.query/pricing.mutate 暴露窄接口。
3. Pricing override 保留为产品能力，跟踪可编辑的 Pricing Settings 页。

认可三个独立 follow-up 的拆分。Owner：desktop subscriptions 负责 (1)，main-process usage/pricing 负责 (2)(3)。

[me2seeks]

The decisions tracked here have now landed: Cursor subscription retirement in #2037, removal of the consumer-less Usage bridge in #2065, and the remaining Pricing work is tracked in #2015. I think this issue has served its purpose and can be closed. Thanks!

[Astro-Han]

Closing as completed. #2037 retired the cursor subscription, #2065 removed the consumer-less Usage bridge, and the remaining Pricing delivery is tracked in #2015.