Assignment ADR-0053/delivery/010, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Root authorized read-only production metadata/file inspection and local diagnosis/correction. Delivery performed no production POST, signature/window, credential activation, deployment, promotion, env or DB mutation, Phase C or business/recipient call. Diagnostic13z is retained. Original009 claim/result and revoked role remain intact; root remains sole canonical publisher/indexer.
Concrete packaging defect
The009 request logged only fixed sdk_integrity, outcome denied. In the exact uploaded source5f9 artifact, native SDK version3.8.1 and all five pinned executable hashes are correct. Fresh deployment file API inspection verifies the private function config uploaded UID and all58 SDK package files against reviewed bytes. Its343-entry filePathMap and entire uploaded file tree contain zero jose, @vercel/cli-config or @vercel/cli-exec files, despite these being declared SDK runtime dependencies.
assertSdk verifies the version and five hashes, then performs native require('@vercel/oidc'). That entry eagerly requires verify-vercel-oidc-token.js, which requires native jose, and token-util.js, which requires the CLI packages. Webpack's bundled application JOSE does not supply a native node_modules package to this require chain. In a fresh isolated Linux function directory, the exact SDK passes version/hash checks and then fails MODULE_NOT_FOUND jose. The actual packaged launcher separately reproduces404/no-store with sdk_integrity: denied, zero audit queries, zero SDK/JWKS calls and zero unexpected network calls. This is a concrete defect in the deployed upload and reproduces its observed denial; the production log itself does not expose an exception code or stack.
The original008 native harness ran beneath the repository and allowed Node to search ancestor node_modules. Those dependencies masked the incomplete function package. Original008 evidence is retained, but its successful result does not establish isolated dependency completeness. The010 harness materializes actual function files/file mappings under an isolated /tmp directory and rejects every resolved executable outside that runtime root. No SDK stub supplies the missing package.
Small correction and exact candidate
Application source is ab43bc8da9d88babda2f0619e97b6361b246dc10. next.config.mjs includes the installed native SDK runtime dependency closure for this private route, including nested versions, through lib/native-package-trace.mjs. The build gate requires successful native SDK loading with every resolved file present in the NFT trace. Trace input uses stdin, avoiding Linux process-size limits. The first local build's oversized environment-input failure is excluded from accepted artifact evidence. No SDK, version/hash check, approval/runtime binding, audit cap, TLS, cancellation or financial logic changed.
Source diff against57cb0c is docs/adr0053-workload-proof/review/sdk010-source.patch, SHA256 cf7e92a73146f2048e4d9deb28f4a665dfd974cccc1c7256039a3800d493705b. Distinct .tmp/linux/diagnostic-sdk-closure/ Build Output was built from exact clean source with unavailable local database inputs, actual five cron definitions in source/build override/output and all external actions off. It has1799 entries (1680 regular,119 contained links), six Node24/ARM64 functions, private proof maxDuration30, zero native addons, unchanged public-example allowance and SDK pins. Its1451-entry private function map includes the full native dependency closure.
| Evidence | SHA256 |
|---|---|
| Corrected artifact manifest | 0ddba783b9958dda16ed091a9edba93d1b2c768638753ee58799342cfca69f7b |
| Corrected artifact verification | 73a797bcc57160499f66abf9099d7ec60a590afd561f29e9565ead23ec8b590c |
| Full26-pin review packet | 5c7acb3d6ec97553f11569402c9ceca0771e9f92b753ed6dfacf1aa3e5e520bb |
Packet is docs/adr0053-workload-proof/review/sdk010-review-packet.json. It additionally proves exact Git source blob hashes match candidate source file bytes. Original009 artifact572/119 and cleanup508/118 entries were completely rescanned with their original manifests and remain unchanged.
Positive, negative and native validation
Four fresh isolated SDK-load cases pass: corrected native load succeeds; removing the resolved entry for each of jose, @vercel/cli-config and @vercel/cli-exec fails while SDK version/five hashes remain correct. The corrected actual native launcher returns200/no-store/passedtrue and produces approved/reserved/completed rows. Eleven HTTP denials cover bad signature,121-second span, source/runtime drift, default-off silence, replay and each of the five SDK executable tamper cases. Tamper/admission denials precede audit queries; replay performs only its denied reservation query. There is one SDK exchange double, one JWKS double and zero unexpected network calls. The SDK itself and all native dependency resolution are real and contained.
Real PostgreSQL17.9 fixture is fresh loopback127.0.0.1:55484, databaseproof010, restricted roleproof_runtime010 and ownerlocal010_owner, with data retained at .tmp/local010/pgcluster. Native reservation/privilege/owner/clock SQL runs against this real fixture through an explicit test-only PG transport bridge. It verifies the diagnostic CA and rejectUnauthorized options before bridging to local SQL; RSA/JWKS and token-fetch responses are fixture doubles. This is not deployed TLS, Vercel workload/epoch/resource or production restricted-role attestation. Only this new cluster was stopped after evidence; older fixtures/listeners are untouched.
Delivery npm test passes996 with15 skipped, plus8 audit unit tests. Typecheck, runtime smoke, native trace-closure test, build/native-load gate and complete artifact scans pass. Corrected candidate has not been deployed.009 stays UNKNOWN, and all production financial/activation gates remain open. Any future production acquisition needs a separately reviewed fresh executable/profile/claim bound to this new source/artifact, not reuse of completed009 custody.