Repository navigation
feat: release OS 0.3 with owned units and retirement - #17
Merged
Merged
Conversation
This was referenced Nov 5, 2026
Sunrisepeak
changed the title
Sunrisepeak
marked this pull request as ready for review
November 6, 2026 03:48
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.
Release OS 0.3.0 with generic owned process units, an observation reference retaining native identity, and retirement that closes admission before proving completion. The composition supports bounded concurrent work and recovery after process loss without platform PID logic in consumers. If all native holders are lost and completion cannot be proved, observation remains unknown and recovery refuses to guess.
The dependency group selects public OpenKal 0.24, Linux 0.25, macOS 0.22 and Windows 0.20. Image and hosted CI select public platform 0.24 with public mcpp 2026.11.5.1. Native lifecycle controls use the immutable published specification/backend merge commits.
The new minor isolates explicit compatible requirements such as
^0.2.3; a bare0.2.3remains an exact pin. Source-only resolver controls confirm that OS 0.3 and platform 0.24 configure together, while old/new mismatched groups are refused. Ordinary public OS installation and range controls follow source publication and catalog admission.Final exact-head native, image, hosted and lifecycle CI plus independent ecosystem review remain required before merge. This does not claim automatic recovery when native completion is unknown.