0.10.2 candidate: endpoint-scoped catalog, tiered pricing and release verification

[Hmbown]

This 0.10.2 candidate makes model admission, catalog facts and exact tiered pricing specific to the selected endpoint. It repairs Windows command approval/input/recovery, Claude login state, temporary quota-worded rate limits and oversized-session diagnostics, and integrates Runtime worker ownership and late completion receipts. 0.10.2 has not shipped.

Current candidate and intake

Candidate head: 9985a6f0fa, tree 4a27e34712f12d5ac44a2d2c3f4802307a4f1747. This ancestry refresh merges the reviewed stacked contributor head deb491c4 into a42813ff. The five shared documentation/credit conflicts retain the exact candidate blobs; the entire candidate source tree is byte-for-byte unchanged. Both original contributor histories and credits are preserved.

The original contributor PRs must still land as themselves before this candidate's conditional squash. The candidate now contains their current source heads as ancestors. #6989 carries #6985’s source for parallel qualification of their combined tree; merge order remains #6985, then #6989, then this candidate. Neither original PR is claimed merged by this update.

Contributor PR	Current PR head	Included contribution and limits
#6985, @henrikdukefoss	9f5ed8ebb674d12afb7276ce0bbf4519444c7c1d	Standard Compute descriptor, authenticated-discovery implementation and Unknown billing; original source ancestor 93132146 retained. Fresh checks pending. No live provider or commercial qualification.
#6989, @shenjackyuanjie	deb491c44bb4bcf9b4dbfb0b9c5b3cde601a17ef	OHOS Ninja selection and ungated CLI SHA-256 helper; original source ancestor c59004af retained. Windows clipboard gate failed before native tests; exact startup cause is unknown and a bounded same-head retry is held until the workflow finishes. This is an intake dependency failure, not a result of this candidate’s separate native job. Linux-SDK checking is not Windows-host SDK or OHOS-device acceptance.

#6393 remains excluded. Its contributor returned it to draft for unpublished navigation/measurement work; scope clarification is pending. Existing historical Aditya credit remains intact; no new #6393 feature or release claim was imported.

Current qualification

The 51c00f23 repair addresses the inherited Windows metric-fixture failure observed on #6989's prior head and the mobile smoke pipeline failure on candidate 282e1948. The metric fixture uses the existing test-only host-capability pin across platforms; the smoke assertions avoid an upstream broken pipe under pipefail. Production host discovery, catalog budgets, equality assertions and test deadlines remain unchanged. Original failure logs remain attached to their exact heads.

The three-file repair was validated locally on macOS before committing 51c00f23: 2 existing focused Rust tests passed, the complete extracted tool catalog equals the existing budget with no identity/cap changes, the production CLI binary built, 9 mobile HTTP smoke assertions passed, and npm test && npm run check:web passed 1,312 tests with 0 failures and 7 skipped (540 Node + 772 Vitest). The first isolated smoke launch exceeded macOS's socket-path limit before HTTP assertions; correcting only the artifact launcher then passed all 9 assertions with the same compiled binary. Both attempts are retained. These are focused local results on the main repair, not full native qualification of this combined candidate head.

Fresh candidate checks are pending on 9985a6f0fa. All three native suites and required gates must complete for the refreshed head before merge admission. The immediately preceding a42813ff run, on the identical source tree, completed all 9 mobile HTTP smoke assertions and 772 Web Frontend tests successfully. Those receipts retain their actual old-head identity; the ancestry update does not convert them into fresh-head status checks. No overall candidate PASS is claimed, and local macOS checks do not replace hosted Windows or packaged acceptance.

Prior source-specific evidence remains available: candidate 282e1948 passed local npm/check:web (1,312 passed, 7 skipped), all 55 Runtime metrics exactly at budget and the production CLI compile check. Its hosted Lint also passed the actual Runtime/persistence gates. Those results retain their original source identity; the full 55-metric measurement was not repeated as part of 51c00f23's focused repair. Earlier fe7e1fc7 full native and clipboard receipts likewise qualify that earlier head only.

The retained source review found no Rust merge conflicts; candidate implementation, contributor changes, Engine execution-ID/input documentation and all 72 generated feature rows are preserved. macOS LLVM setup and candidate debug-profile settings remain. Windows startup diagnostics do not establish a startup cause or fix. Actual Windows 10 1607 startup/Native-host acceptance remains unverified; the release wording is limited to dynamic API lookup and the unsupported LPAC result.

CodeQL alerts #562–565 remain open and undismissed. The four reported function bodies were rechecked against the current candidate source tree and are byte-identical to the earlier bounded static triage. That counterevidence did not justify a source repair; it is not exhaustive security acceptance or a fresh hosted CodeQL analysis.

Carried changes and contributor credit

• @SparkofSpike's #6929 merged as its own PR at 5ebb2c14f8: PowerShell call operators, quoted ampersands and combined redirection retain destructive-command detection. Thanks also to @jayanthvee for the detailed #6963 diagnosis.
• @SparkofSpike's #6949 carries Windows junction handling. Missing-target first use and final packaged acceptance remain separate limits.
• @Lstarsky0's #6967, #6966, #6971, #6975, #6977, #6956, #6958 and #6943 improve steering receipts, watchdog readiness, loopback fixtures, host recovery, cleanup and clipboard handling.
• @Lstarsky0’s #6979, #6982 and #6984 now also carry terminal-fixture isolation, relay-watchdog scheduling tolerance and provider-status alignment. @printf033’s #6983 carries the Linux/Android confined-directory anchor repair; actual compiled Android-binary acceptance remains pending.
• @gaord's #6974, #6959 and #6924 contribute provider marker persistence, skill trust and workspace lease lifetime fixes.
• @aboimpinto's #6973 carries command-shape adoption for the main config surface.
• Candidate fixes also address @Statter's temporary quota response report (Bug or feature: in case of Gemini 429 error, wait and auto-retry last task #6923), @7jrxt42BxFZo4iAnN4CX's oversized-session diagnostics (A saved session document larger than 8 MiB can no longer be resumed or forked, and the refusal names no remedy — the journal is what pushes it over #6955), @cmdcorp6534's modal input report (未适配中文输入法 #2323), and @LmeSzinc's Windows import/startup report (Windows 10 1607: v0.10.1 fails to start — unresolved load-time import DeriveCapabilitySidsFromName (0xC0000139) #6953). Known OS/input/provider and final-artifact limits remain below.

Eight original PRs merged during this takeover: #6979, #6982, #6984, #6983, #6873, #6917, #6965 and #6807. The latter four retain ancestry for already-carried or explicitly superseded source. Pet reconciliation #6807 leaves main's source tree unchanged, preserves shared Stage/mode controls and supersedes the old unconditional override; skipped native jobs provide no new native/default-parity proof. All source branches are retained.

Remaining release gates

1. Complete the remaining approved intake on each contributor's own PR, reconcile any subsequent accepted intake, and freeze the resulting source. Complete exact-head CI and fresh merge/dependent-PR checks before the conditional squash. Preserve all source branches and return the canonical checkout to main.
2. Qualify the final main SHA with full manual CI and a nonpublishing RC: seven targets, 34 baseline assets, the RC's own parity results, digests/checksums and Windows import sidecars. No final-source RC is established.
3. Run the strict clean-source 29-crate no-upload preflight and archive/VCS audit at that final SHA. Historical package receipts cover earlier sources only. codewhale-ratatui 0.1.2 is already published; do not republish it.
4. Complete actual final Windows native/archive/npm/NSIS installation, embedded-plugin and generated-uninstaller checks, VC dependency closure and packaged/native-app owner recovery. Actual x64 Windows 10 1607 acceptance or an explicit founder decision remains required.
5. Resolve final-source security coverage and alert disposition. Claude's independent-state/input repair has synthetic malformed-input proof, not a successful issuer grant; registration/client identity and release visibility remain founder/external decisions. 0.10.2: repair ChatGPT sign-in rejected by unsupported originator parameter #6925 login and 0.10.2: every Bash/shell operation Codewhale starts or tracks is inspectable and stoppable #6931 terminal journeys remain separate acceptance work.
6. Retain the remaining real-session resume/fork, native recovery, IME/preedit and long-running scroll limits (codewhale resume refuses any session whose saved history still holds a raw sub-agent handoff — the canonical acknowledgement compares the Engine-restored messages with the saved document #6954, 未适配中文输入法 #2323, After running for a long time, TUI scrolling becomes laggy, like jelly. #6652). Issues close on release or explicit direction. Runtime API terminal contract: input attribution, restart-safe identity, Windows ConPTY #6160 ConPTY and unrelated research are not release promises.

The founder's conditional squash approval does not authorize tagging, package/release publication or deployment. Latest public release remains v0.10.1. Ownership and evidence are on CW-6439.

Windows reports #6986 (paste), #6987 (shell binding) and #6981 (compaction/busy state) remain open. The first two have relevant source fixes already in v0.10.1; reporter-equivalent and packaged acceptance remain distinct. No issue-specific reproduction or fix for #6981 is established. The current clipboard fixture does not cover raw-key fallback, trailing blank lines, Windows 10 1607, ARM64 or installers. Real-session resume/fork, IME/preedit, long-running scroll and login journeys remain acceptance work.

Refs #6396

— Written by GPT-6 (AI agent) on behalf of the maintainers.

[claude]

⚠️ Code review skipped — your organization has no extra usage available to pay for this review.

If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.

Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.