[Subscription Providers 6/7] Cursor real-client V2/restart and dual-platform qualification

[NOirBRight]

Part of #603.

Acceptance

Qualify production Responses/Chat/Messages and existing client projection. Unpredictable disposable fixtures prove actual current-Codex Code Mode caller execution, official-parent/Cursor-child and reverse V2 spawn/wait/same-child followup, directed task survival and completed-history continuation after actual backend/Gateway restart plus fresh caller, including V2. Ordinary chat or a function named exec is insufficient. Preserve selected identity; no whitelist, output normalization or fallback. Retain malformed-envelope/exact-output failures. Exercise cancellation cleanup, existing auth-failure and authentication-file-change handling, errors and known differences. Existing controlled contract tests cover these safeguards. Real-client acceptance uses the current official CLI account; provisioning multiple real accounts or expired login states and a new account-switch feature are not release requirements. Sanitized evidence binds exact SHA/CLI versions. Strict local suites and Linux/Windows packages from same SHA before shippable claim; release/tag is separate.

Dependencies

#605, #606, #608

Verification

Risk class: strict. Follow docs/agents/verification-policy.md and docs/specs/cli-subscription-providers.md. Historical feasibility does not qualify the production candidate.

[NOirBRight]

Draft implementation/evidence PR: #614. Two authorized bounded probes on exact clean e9449930 passed:

• Responses caller tool (8.40s), actual result (4.48s), actual Gateway restart + fresh caller complete native history (4.35s). Result/restart preserve the same exact 32-byte fixture; no history fields, Item IDs or Call IDs were stripped. Private cleanup checked. Earlier 502 remains historical with unknown cause; it is not relabelled transient or repaired.
• Official-parent → Cursor-child V2 (72.996s): same child followup/wait, two actual Code Mode reads, exact outputs, real Gateway restart and fresh caller. 15 HTTP200, native plaintext metadata, no independent Cursor effort or model fallback. Original reverse-V2 failure retained.

Earlier Cursor Chat/Code Mode/completed-history and Cursor-parent → Official-child passes remain separately bound to their own source snapshots. Reports are in docs/evidence/cli-subscription-production-2026-10-01/ and docs/evidence/subscription-official-cursor-e9449930-2026-10-01/.

This qualification issue remains open: Messages requires a genuine mandatory max_tokens mapping and currently rejects; after-first-text cancellation remains inconclusive; #605 authoritative recovery/old opaque history is partial; same-SHA Linux/Windows qualification is incomplete (yoga SSH unreachable). No same-SHA all-case or shippable claim, no tag/release. Final Linux core is running after a remaining old namespace-declaration test was updated to the reviewed source-prevention contract; Rust 802 tests, Clippy, UI contracts and native physical pointer E2E have passed.

[NOirBRight]

Primary-source output-budget research is checked into PR #614 at docs/research/2026-10-01-cli-subscription-output-budget.md (official docs, exact installed versions/artifact SHA/byte offsets; zero inference, credential reads or implementation changes).

Claude Code 2.1.286 has a genuine CLAUDE_CODE_MAX_OUTPUT_TOKENS → native API max_tokens path, but automatic truncated-output recovery can start another generation. Whole-Gateway-turn budget semantics and the effect of --max-turns 1 are unproven; a simple environment assignment cannot yet qualify Messages.

Cursor 2026.09.28-64d2043's current AgentService/Run descriptors and actual CLI request construction expose no evidenced output-budget field/parameter ID. Generic string parameters do not prove an enforcement contract. desired_max_tokens belongs to a different legacy request type and cannot be transplanted into Run. This is a version-specific bounded finding, not a claim that hidden service support is impossible.

Messages stays explicitly unsupported until a genuine mapping and bounded capture/runtime proof exist. Context limits, monetary/turn limits, prompt instructions and estimated local token cutoffs are not substitutes. This technical gap remains separate from Claude inference permission and Windows qualification; no acceptance issue closes.

[NOirBRight]

Orchestrator platform update: yoga is currently reachable; bounded existing-config SSH readiness passed in 0.301s. Candidate d45988c isolated Windows engineering checks ran, operator checkout was unchanged and owned checkout/processes were cleaned. Thus historical No route to host is not a current platform excuse.

Windows core still failed 12 synthetic backend/transport cases; canonical runtime preparation removed tracked .keep, so clean-candidate provenance remains incomplete. Repairs #640/#641 are delegated, and parent owns a new exact-clean reviewed candidate gate. Synthetic165/Rust822/Clippy/UI188 execution successes do not substitute for these failures or live Provider/dualplatform package qualification. This round performed no vendor inference, entitlement retest, reverse-V2 exact-output or after-first-text cancellation qualification.

[NOirBRight]

编排更新：

• test: capture Official fixture text and message Call boundaries #653 冻结返修 dd88cc927966dc64ac892409cca47ee200e3407a 的独立 Spec delta R3 完成：原 P2A/P2B 均 FIXED，新增 findings 0，父会话验收复核结论。保留原 Standards 0 与父会话 delta Standards 0；275 focused +4 runtime PASS、5 RED→5 GREEN 和交接包/完整源码身份检查已记录。最终 affected core gates 尚在排队；未导入、未 LIVE、未关闭工程票，历史 ba79 原因仍 UNKNOWN。
• test: qualify subscription cancellation after first streamed text #652 已通过独立修复复核的 04f1c78b485ec5463f6bbed04c265597daf945a1，Linux/Windows core gates 继续运行，尚未宣称结果。
• test: observe owned Windows TCP cleanup for streaming cancellation #656 已从队列派出，由 Codex / GPT-6.1 Sol / High 担任唯一源码 writer。明确使用上述 test: qualify subscription cancellation after first streamed text #652 冻结候选作为私有实现基线（复核通过，完整 gates 待返回，并非 campaign admission）；test: capture Official fixture text and message Call boundaries #653 的独立观察改动不属于该实现 seam，未混入基线。实现限定在现有 qualifier 的 Windows owned TCP 观察，保留 deadline/activity/cleanup/FD 原义；一项有限的原生 loopback control 不代表 Windows live cancellation 通过。

当前三个子任务位均已占用：#652 Linux core、#652 Windows core、#656 implementation。#609 仍待实际双平台取消及原 protocol/V2/restart/release 验收；外部 budget/provenance/Claude permission 原前置保持不变。Root 仍为 1137cfeaa61645aefb15cb49ec3a26ffcdad487c，没有发布。