type: reference title: "Terminal control-plane diagnostic evidence" description: "Retained failed candidate receipts and subsequent source validation for the 2026.1 command journey."

Terminal control-plane diagnostics, 2026-10-11

These are retained execution results for SDK issue #1424's bounded 2026.1 command journey. The overall qualification failed. They prove successful and denied individual stages and preserve the server defects that block a complete release claim.

The CLI ran its real executable with a private HONUA_BEARER_TOKEN. MCP used a real MCP client/tool roundtrip against createServer with the control-plane runtime explicitly composed. Studio used its command adapter; JavaScript used the shared SDK runtime. The local SDK and MCP build came from 70566967348b3a78f6abc107c205538cad67e3b3; its package metadata still said 0.1.14. These are source-build results, not evidence about published 0.1.14 registry bytes.

The server was the immutable nightly-93cad86 image, digest sha256:785de2ae7f72e6277ce62aa1ece4f08ee0425970b71c47f9f4843c0baae2c8db, in an isolated Production stack with PostGIS, Redis persistence, an encrypted keyring, and a configured audit-chain key. Real OIDC sign-in issued the authenticated tenant principals; no fabricated tenant header supplied their identity. runtime-proof.json, principal-proof.json, scope-principal-config.json, and audit-integrity-proof.json identify that setup. The audit-integrity check covers its stated 82 rows and was captured before the subsequent command calls; the stage-specific audit exports retain those later calls separately.

The package fixture was an independently owned inline one-point package, not a package assembled from the imported table. This run therefore does not prove the complete connection→import→published-map journey, approval completion, full terminal/Studio equivalence, or release certification.

Server issue #5872 tracks durable URL-import idempotency. Server issue #5877 tracks the scoped Studio refusal response. The read-scope URL-import guard already landed in server PR #5823, but it is absent from the selected 93cad86 image. A later supported combined build and, separately, the selected immutable release candidate must be exercised before issue #1424 can close.

The temporary fixture object was deleted after all eight background jobs finished; owned-import-cleanup.json records HTTP 204 followed by HEAD 404. The retained object identity and content hash identify the input without retaining its signed URL. The original private diagnostics remain untouched. artifact-index.json records each copied file's original and retained hashes and the exact JSON paths where a signed URL or truncated signed-URL summary was removed. Tokens, passwords, certificates, cookies, environment files, and signed URLs are excluded.

Engineering follow-up outcomes

engineering/ retains the subsequent local diagnostics without replacing the failed candidate receipts above. The actual .NET 10 source-generated import DTO parsed an omitted targetSrid as zero, while explicit 4326, 3857 and zero remained distinct. default-probe.jsonl records those four outputs. Server commit ff44ded979 corrects that initializer behavior and adds direct-context and retry-conflict regressions.

The local integration source was commit 072ed2781f33135670f073802135bdd95c3510af, combining the reviewed import and Studio repairs. Its initial production Server target completed; the pending local test invocation was cancelled at that boundary. The retained receipt records its actual Server DLL hash. After applying the reviewed default repair, a second normal production rebuild used separate compiler processes and a 900-second bound. It exited 124 before producing a completed corrected runtime. No local tests, corrected-runtime behavior, or candidate certification are claimed for that attempt. The base64-encoded reviewed-source.patch.base64 and its decoded SHA-256 bind the attempted source precisely.

Hosted checks for ff44ded979 passed all 5,716 FastServer tests. The architecture gate then correctly found that the newly added real import integration test was missing from the shard roster. The roster follow-up registers it in the existing Cloud and Streaming Import shard; its checks and the supported immutable-candidate replay remain separate requirements. Studio repair PR 5880 has merged, but a real signed Production refusal and no-actuation receipt remains necessary for server issue 5877.

The hosted follow-up at 38590f602b passed all 63 Cloud and Streaming Import cases. Its TRX contains both real SameKeyAcrossRoutes_DownloadsAndPersistsOnlyOnce route orders: one download and persisted row, matching operation and response, and a changed-payload conflict. engineering/hosted-synchronous-import.json records the exact test outcomes and original artifact hashes. These synchronous Test-environment results do not certify Production background jobs or the later review fixes.

At final reviewed server source 80e51d29ff3c765e874cbd4facba4581f93e924b, the focused Core workflow passed 53 tests in each of two iterations, including all 13 bound-idempotency cases covering cancellation, retry audit failure, uncertain creation and concurrent ownership. The final Cloud and Streaming Import shard passed 63 tests, including both real HTTP endpoint aliases. engineering/hosted-final-import.json records the original artifact and TRX hashes and exact targeted outcomes. The complete normal PR gate subsequently passed: 5,732 FastServer tests, 363 architecture tests, 69 AI tests, all six affected integration shards, and the required HTTP/GDAL/PDAL/boot proofs. The review gate passed after all four findings were repaired and their tests executed. Server PR 5879 merged normally at a916167ee777e8ec0f732fc64ea8f8cfb772807d on 2026-10-11 at 22:17:23 UTC. The signed Production candidate replay remains a separate requirement.