WIP: Provision recipient readiness storage #294

Draft
erikinkinen wants to merge 5 commits from feature/recipient-readiness-capacity into feature/pty-readiness-capacity
Owner

Give original recipient waiters an independent deployment count through runtime configuration, shell forwarding, image production and reports. The producer requires the pristine version-ten 33-word compiler layout, retires version nine, includes final typed alignment at zero capacity and preserves the existing terminal stack.

Existing program-budget and filesystem-packaging consumers retain explicit zero-waiter policy and their original storage boundaries. Matching provider: Launchd #69.

  • Preserve explicit zero and positive counts across runtime, shell and image boundaries.
  • Keep waiter storage independent of job, stream, realm and program arenas.
  • Reject retired, truncated, nonpristine and invalid target geometry.
  • Preserve terminal-stack placement and filesystem-only packaging.
  • Execute matching-provider native recipient readiness and retirement controls.

Hosted image checks do not establish native readiness or either required guest rebuild.

Depends on #292 and #293, included by a normal merge.

Give original recipient waiters an independent deployment count through runtime configuration, shell forwarding, image production and reports. The producer requires the pristine version-ten 33-word compiler layout, retires version nine, includes final typed alignment at zero capacity and preserves the existing terminal stack. Existing program-budget and filesystem-packaging consumers retain explicit zero-waiter policy and their original storage boundaries. Matching provider: [Launchd #69](https://git.erikinkinen.fi/erix/launchd/pulls/69). - [x] Preserve explicit zero and positive counts across runtime, shell and image boundaries. - [x] Keep waiter storage independent of job, stream, realm and program arenas. - [x] Reject retired, truncated, nonpristine and invalid target geometry. - [x] Preserve terminal-stack placement and filesystem-only packaging. - [ ] Execute matching-provider native recipient readiness and retirement controls. Hosted image checks do not establish native readiness or either required guest rebuild. Depends on [#292](https://git.erikinkinen.fi/erix/integration/pulls/292) and [#293](https://git.erikinkinen.fi/erix/integration/pulls/293), included by a normal merge.
erikinkinen added this to the Alpha 1 milestone 2026-11-05 14:50:42 +01:00
fix: Check component clones within each CI job
Some checks failed
CI / markdown (push) Successful in 23s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / rust (push) Failing after 2m42s
CI / host_one (push) Has been skipped
CI / host_zero (push) Has been skipped
CI / integration (push) Has been skipped
ac86691ae5
Each isolated host shard and integration job needs its own configured component checkout before consumption. Replace the obsolete workflow-wide clone count while preserving catalog, path and runtime source identity checks.
Carry an independent Launchd waiter count through runtime configuration, shell forwarding, image selection and capacity reporting. Require the pristine version-ten compiler layout and include the final typed waiter slice without borrowing existing job, stream or realm storage.

Preserve zero-count alignment and terminal-stack placement, reject retired or previously patched descriptors, and select the matching Launchd provider. Update existing program-budget and filesystem-packaging consumers to declare their original zero-waiter policy explicitly.
ci: Compose component source layout controls
Some checks failed
CI / markdown (push) Successful in 19s
CI / rust (push) Failing after 1m6s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
a9ff59c71e
Retain the independent job-scoped clone regression controls alongside recipient storage provisioning so validation observes each actual checkout boundary.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
2f520dcc9d
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (push) Successful in 10s
CI / rust (push) Failing after 57s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
b8e5372bfc
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / markdown (push) Successful in 10s
CI / rust (push) Failing after 57s
CI / host_zero (push) Has been skipped
CI / host_one (push) Has been skipped
CI / integration (push) Has been skipped
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/recipient-readiness-capacity:feature/recipient-readiness-capacity'
git switch 'feature/recipient-readiness-capacity'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/pty-readiness-capacity'
git merge --no-ff 'feature/recipient-readiness-capacity'
git switch 'feature/recipient-readiness-capacity'
git rebase 'feature/pty-readiness-capacity'
git switch 'feature/pty-readiness-capacity'
git merge --ff-only 'feature/recipient-readiness-capacity'
git switch 'feature/recipient-readiness-capacity'
git rebase 'feature/pty-readiness-capacity'
git switch 'feature/pty-readiness-capacity'
git merge --no-ff 'feature/recipient-readiness-capacity'
git switch 'feature/pty-readiness-capacity'
git merge --squash 'feature/recipient-readiness-capacity'
git switch 'feature/pty-readiness-capacity'
git merge --ff-only 'feature/recipient-readiness-capacity'
git switch 'feature/pty-readiness-capacity'
git merge 'feature/recipient-readiness-capacity'
git push origin 'feature/pty-readiness-capacity'
Sign in to join this conversation.
No description provided.