fix(serve): stop renewing settled Hosted Shell grants - #13199

What this PR does

Stops renewing a Hosted Shell publication once the original execution has authoritatively settled, while retaining its binding until receipt acceptance so failure cleanup still works. Each renewal pass attempts all live bindings before reporting failures with their publication IDs. A renewal already in flight when settlement is observed can finish without producing a misleading warning; genuine renewal failures still block dispatch.

Why it's needed

A slow Session receipt leaves the settled execution in the batch's bookkeeping. The publication service correctly rejects renewal of settled executions, but the client previously kept renewing them and logged a misleading warning. The first rejection also prevented queued publications later in the same pass from being renewed.

Reviewer Test Plan

How to verify

1. Hold the first Shell execution open in a two-call batch and advance the renewal timer. Both its running publication and the queued second publication should renew.
2. Settle the first execution, hold its receipt commit across two timer ticks, and check that only the queued publication renews. Release the receipt: both calls should complete, ownership should release normally, and no publication-renewal warning should appear. Repeat for original-finished-publication recovery and a proven not-started execution.
3. Let an already-running renewal reject after settlement is observed. It should not warn or prevent renewal of the queued publication.
4. Reject an unsettled timer renewal with HTTP 503. The same tick should still renew the queued publication and log exactly one warning naming the failed publication. The next successful tick should retry both live publications. HTTP 400 or 503 during pre-dispatch renewal must still block dispatch after attempting all bindings.
5. Return cancelled-before-dispatch with no capture, then reject the finished-publication lookup. Recovery must cancel the original execution and send close_not_started with the original publication ID and token, without releasing uncertain ownership.

Evidence (Before & After)

N/A for visual evidence: internal Hosted lifecycle behavior, no TUI layout change. With the final regression tests on unchanged base 8eaaa13, seven cases fail and the cleanup-preservation case passes. Settled publications are renewed, delayed receipts produce spurious warnings and skip queued grants, and genuine per-binding errors stop the renewal pass. The exact same eight cases all pass with the fix. After the fix, all 581 Hosted CLI tests (15 files) and 1,927 managed-runtime core tests (34 files) pass, 2,508 in total. Full build, full typecheck (4 GiB Node heap), bundle, repository-wide lint:ci, changed-file Prettier, diff whitespace checks, and the serve-fast-path bundle closure check also pass.

Tested on

Environment (optional)

Debian 13, Node.js 24.19.0, repository-pinned pnpm 11.24.0. Usage statistics and OTel are disabled with QWEN_USAGE_STATISTICS_ENABLED=false and QWEN_TELEMETRY_ENABLED=false. The component tests exercise the actual Hosted turn coordinator and local Session/harness persistence with controlled Broker and publication-service fixtures. Only interval timers are advanced. The global qwen CLI is unavailable in this environment.

Risk & Scope

• Main risk or tradeoff: renewal eligibility must not erase the original binding needed by failure cleanup; the regression suite pins both paths. Review remains important for this Hosted lifecycle code.
• Not validated / out of scope: full npm run preflight did not complete. Its default 2 GiB integration-typecheck heap exhausted memory; a separate full typecheck passes with NODE_OPTIONS=--max-old-space-size=4096. The repository-wide unit-test run then encounters EPERM when browser-use tests bind Unix-domain sockets in this environment. The scoped Hosted suites reported above pass; no full-suite pass or real Java Broker, Session Store, database/OSS E2E is claimed. Tenant-wide reservation-expiry races remain outside this change.
• Breaking changes / migration notes: none; no protocol, server, ownership, or public-interface changes.
• AI assistance: implementation and tests were produced with OpenAI Codex. Submitted as a draft; human review is pending.

Linked Issues

Fixes #12957. Follow-up to merged #12894.