Repository navigation
fix(runtime): adopt Core 0.19.10 native ownership - #183
Conversation
Bumps the gomod group with 1 update: [github.com/codefly-dev/core](https://github.com/codefly-dev/core). Updates `github.com/codefly-dev/core` from 0.19.4 to 0.19.5 - [Release notes](https://github.com/codefly-dev/core/releases) - [Changelog](https://github.com/codefly-dev/core/blob/main/docs/releaseupdate.md) - [Commits](codefly-dev/core@v0.19.4...v0.19.5) --- updated-dependencies: - dependency-name: github.com/codefly-dev/core dependency-version: 0.19.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: gomod ... Signed-off-by: dependabot[bot] <support@github.com>
|
A lazybox agent is working on this. • Build preparation is complete. Core10883 has been asked for the immutable source and focused-test receipt; the authorized native-only build can proceed when they arrive. The handoff will include the actual private home, installed binary and SBOM paths, hashes, and Core provenance. Old artifacts remain preserved; no Docker or runtime actions. Worked for 2m 21s • 1:16 PM › Ask Codex to do anything GPT-6-Astra · high) started at 2026-10-28 05:17 UTC, last renewed the claim at 2026-10-30 17:24 UTC, and the claim lapses at 2026-10-30 18:24 UTC unless it is renewed again. A claim is an assertion with an expiry, not proof that a process is alive. claim detail |
Adopt published Core v0.19.10 so newly built Next.js agents use Core’s authenticated-v2 native ownership and corrected process inspection. Preserve dependency carrier d3dcf8e and merge current main 4d0f9f6, retaining the linked-package fixes and release documentation. The agent version remains 0.0.169; these local bytes are not a published Next.js release.
Classification: fix at the dependency adoption boundary. Core owns the writer, birth checks, process groups and stop/recovery behavior; CLI owns preview/expect recovery. This PR reuses the existing native runner, authenticated manager, network mapping APIs, agent deps/build packaging, and receipt parser. It adds no runtime, registry, recovery framework, process matcher, or production runtime edit. The maintained real-agent test and
.claude/skills/verify-changes/SKILL.mddocument and exercise adoption.Validation on clean 8c9a44f, darwin/arm64, GOWORK=off (parent results explicitly attributed below):
agent deps --pin v0.19.10, standalone build verification,go build ./...,go vet ./..., andgo mod tidy -diff: pass.go test -json -skip 'TestNextjsLifecycle_Matrix/(docker|nix)' ./...: pass, 177 passing test events. Default opt-ins skip; separate runs below close the native and manifest cases.CODEFLY_TEST_RUNNER=1 TestCreateToRun: pass; production and factory sources are unchanged by the test/docs-only correction.Local-run limits: no local Docker slot was used. The later hosted CI below supplies native/Docker lifecycle matrix, effective-input and proto-companion evidence; native-cross packaging remains unverified. Nix was explicitly excluded under the isolated-cache constraint, although its executable exists. No Linux runtime, sandbox/principal admission, full CLI composition, or released Next.js artifact is qualified. The selected reviewed CLI uses its recorded local Core source, not a published-pin CLI. The existing declared Go 0.0.56 source packager was reused for final GOWORK=off packaging; its own writer is not claimed upgraded.
The native proof is bounded to the tracked npm group. Next.js 16.4.1 may briefly spawn a detached telemetry flush helper despite telemetry being disabled. Test teardown retries deletion of its own fixture home; it does not claim or signal detached/foreign processes. Audit reports existing upstream GO-2026-4883 and GO-2026-4887; passing audit is not zero vulnerabilities.
Independent source/artifact review closed the original-owner-before-signal finding at exact 8c9a44f. Original manager registration is retained before workload RPCs, stale selection refuses through the same guard used by the positive test, and the recovery receipt is bound to the original birth. Historical pre-correction passes remain weaker execution evidence. Frozen local manifest: nextjs183-r2-manifest.json; full review: codex-native-next-fastapi-owner-correction-review.md.
Linux CI at 8c9a44f passed build, manifest guard, effective-input and proto companion checks, but the standalone stale-birth test observed the authenticated launch shell before it executed sleep. Descendant 6a02740 fixes only that test readiness and its procedure: wait for the retained original identity, fail changed/absent/unauthenticated birth or cancellation, and preserve the signal guard. The focused stale/readiness/cancellation test passed locally; a fresh independent review accepted the correction for new Linux CI. The actual-agent fixture and production sources are unchanged, and earlier native artifact evidence retains its original revision attribution.
Hosted qualification on exact final head 6a02740: run 40643518440 passed all five jobs: build/vet/tidy, test, sync-conformance, effective-inputs-conformance and manifest guard. Logs identify merge checkout 71327e6 into main 4d0f9f6. The corrected standalone stale-birth test passed in both Linux test and manifest jobs (4.13s each); native/Docker lifecycle matrix and explicit double-render/inventory/ownership checks passed. Seven frozen evidence hashes were reverified by root.
Nix, installed-agent ownership and CreateToRun opt-ins remain skipped in this hosted run. The actual installed-agent native binary and positive owner-death evidence remain attributed to 8c9a44f on Darwin/arm64; the final correction only changes standalone readiness testing and its documentation. Linux installed-agent owner-death, full composition, release publication and consumer adoption remain unqualified. The earlier failed 8c9 CI and all historical artifacts remain preserved.