Repository navigation
fix(runtime): retain native launch identity through Nix - #123
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Redis v0.0.100 used Core v0.19.4's clock-derived Darwin boot evidence, and scoped cleanup could lose a native server outside its workspace when Nix materialization or Redis process-title rewriting removed observable launch metadata. This consumes Core bc4e15ca through
codefly agent deps --pin: stable birth checks, incompatible-evidence retention, and durable workspace attribution in the versioned owner record.Classification: fix through the shared owner capability. Redis continues to use the existing Nix runner; it adds no identity encoder, process registry or workspace matcher.
templates/agent/README.md.tmpldocuments persistent attribution, mixed-reader upgrade requirements and the prohibition on rewriting retained evidence. CLI owns scoped selection and must adopt Core List/Lookup/InspectOwnership rather than copy a v2 parser.Validation: supported pin resolved
v0.19.8-0.20261027211051-bc4e15cab5b0and passed standalone build. The native lifecycle/claim/concurrency subset passed7.320s. Earlier required-infrastructure full suite passed204.152s at b14; it is not final-head evidence. Fresh required-infrastructure suite, final published Core pin, independent consumer follow-up, and root-owned real controller-dead Redis/sibling scoped-stop qualification remain required before release. No existing live legacy identity was rewritten and no cloud deployment was performed.