[edgepillar]

The previous current-source corpus selects go-zenon 5a2593. Add an immutable selection for ac16bfd7c083e0b808a17014c38a5a77cc0141f1: 514 upstream files, including the changed database/cache lifecycle, decoder and request-budget paths. Preserve historical corpora and recovery-journal pins. Keep the 556 reference outcomes and add seven runtime profiles selecting 52 upstream test functions. Real node startup is excluded; the selected stop fixtures use stub components and temporary local resources.

All 28 profiles share one 538-file source view, one compiler cache and one cold build, with default vet and -count=1. Replace the existing current-core CI selection while preserving the other jobs. Keep runtime top-level completion separate from the 556 reference outcomes; descendant counts are observed, not independently enumerated expectations.

Validation: all 4,407 local offline tests passed with no skips or resource warnings. A fresh Darwin Go 1.23.12 run completed 32 commands and all 28 profiles, retaining 56 original profile streams. The 67 selected originals passed value/privacy checks, 44 altered-copy refusals, 16 fixed producer-format refusals and 29 synthetic component-metadata refusals. Three inventoried test-only initializers configure structured diagnostics before tests. Go compilation uses GOFLAGS=-trimpath to remove local source paths from expected panic stacks before capture. The content reader permits only the exact upstream Protobuf corruption event when its English diagnostic contains a nonbreaking space; all original bytes and digests stay intact, and private paths, hosts and credentials remain refused. With an explicit Darwin SDK, the profile retains -O2 -g and adds only -Wno-deprecated-declarations; Go assertions and other compiler diagnostics remain captured. Original diagnostics from the refused earlier export remain private and unchanged. The selected SDK contents and transitive compiler provenance remain unauthenticated. Synthetic metadata controls provide no hosted origin. A local result-storage failure was reconciled from the complete zero-exit worker output; the original failure remains unchanged. The reconciliation preserves all original bytes without repeating the completed tests.

Fresh hosted PR checks and original-artifact acceptance are required before integration; push-triggered main CI has its own acceptance gate. Application/core remain NO-GO, recovery action remains NONE and independent protocol assessment remains UNFILLED. Complete account admission, signed-account custody, canonical observation and finality are not established.