WIP: Prepare restricted realm terminal control sources #93

Draft
erikinkinen wants to merge 10 commits from feature/realm-terminal-control-preparation into feature/original-stream-receiver-adoption
Owner

Prepare terminal control from the original realm stream owner with exactly the requested rights. Retain stream-source custody through native preparation, configuration and cleanup. Failed preflight remains cleanup-only; a malformed sender reply after completed creation retires the exact realm before releasing its sources.

Depends on #92, LibIPC #184 and LibStdio #16.

  • Carry terminal sources through original-owner preparation and retirement.
  • Preserve first failures and prevent replay after cleanup or completed creation.
  • Compile and exercise the matched original-owner provider graph.
  • Run the guest realm lifecycle with original stream-owner terminal preparation: after completed creation, a malformed sender reply must retire that exact realm before releasing retained sources, without replay or additional authority.

This branch also includes the completed downstream features from #94, #95, #96.

Prepare terminal control from the original realm stream owner with exactly the requested rights. Retain stream-source custody through native preparation, configuration and cleanup. Failed preflight remains cleanup-only; a malformed sender reply after completed creation retires the exact realm before releasing its sources. Depends on [#92](https://git.erikinkinen.fi/erix/launchd/pulls/92), [LibIPC #184](https://git.erikinkinen.fi/erix/lib-ipc/pulls/184) and [LibStdio #16](https://git.erikinkinen.fi/erix/lib-stdio/pulls/16). - [x] Carry terminal sources through original-owner preparation and retirement. - [x] Preserve first failures and prevent replay after cleanup or completed creation. - [x] Compile and exercise the matched original-owner provider graph. - [ ] Run the guest realm lifecycle with original stream-owner terminal preparation: after completed creation, a malformed sender reply must retire that exact realm before releasing retained sources, without replay or additional authority. This branch also includes the completed downstream features from #94, #95, #96.
erikinkinen added this to the Alpha 1 milestone 2026-11-02 04:36:06 +01:00
feat: Prepare restricted realm terminal control sources
Some checks failed
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / rust (push) Failing after 25s
a78fed512b
Retain original stream ownership while preparing exactly the requested terminal control rights. Failed preflight stays cleanup-only, and a malformed sender reply after completed creation retires the exact realm before its source custody can be released.
ci: retain the public source graph on this feature branch
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 32s
CI / rust (push) Successful in 4m21s
f2b43a06a8
Select the existing public providers without changing the feature source or its test matrix.
ci: Use shared development dependency profiles
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 9s
CI / rust (push) Successful in 1m53s
2fdf3d5774
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.
Align contribution guidance with concise commit messages by including validation only when it explains a related issue.
ci: Select the provider policy explicitly
All checks were successful
CI / markdown (push) Successful in 4s
CI / rust (push) Successful in 2m25s
d3e941e353
Adopt the shared main/release and feature source contract. Actual CI reference metadata selects main providers for main and release builds, while feature builds retain their explicitly declared companions.
feat: Merge docs: Keep commit validation references relevant
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m3s
3986ec24eb
Integrate the reviewed prepared history into feature/realm-terminal-control-preparation. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#94
docs: Correct the canonical realm plan header size
All checks were successful
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m0s
a6bdd9b55e
Describe the 176-byte minor-eleven header consistently with the shared codec and Launchd plan storage arithmetic.
feat: Merge docs: Correct the canonical realm plan header size
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m21s
f30fbc55c5
Integrate the reviewed prepared history into feature/realm-terminal-control-preparation. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#95
docs: Align source and wire contracts
All checks were successful
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m2s
89058f061d
Distinguish authored main-branch manifests from immutable provider selection, and correct the remaining stale realm configuration version.
feat: Merge docs: Align source and wire contracts
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m18s
e80fa40603
Integrate the reviewed prepared history into feature/realm-terminal-control-preparation. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#96
Author
Owner

Merged the approved downstream work from #94, #95, #96. The upstream PR retains its own remaining scope and completion requirements.

Merged the approved downstream work from #94, #95, #96. The upstream PR retains its own remaining scope and completion requirements.
All checks were successful
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / rust (push) Successful in 2m18s
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/realm-terminal-control-preparation:feature/realm-terminal-control-preparation'
git switch 'feature/realm-terminal-control-preparation'

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/original-stream-receiver-adoption'
git merge --no-ff 'feature/realm-terminal-control-preparation'
git switch 'feature/realm-terminal-control-preparation'
git rebase 'feature/original-stream-receiver-adoption'
git switch 'feature/original-stream-receiver-adoption'
git merge --ff-only 'feature/realm-terminal-control-preparation'
git switch 'feature/realm-terminal-control-preparation'
git rebase 'feature/original-stream-receiver-adoption'
git switch 'feature/original-stream-receiver-adoption'
git merge --no-ff 'feature/realm-terminal-control-preparation'
git switch 'feature/original-stream-receiver-adoption'
git merge --squash 'feature/realm-terminal-control-preparation'
git switch 'feature/original-stream-receiver-adoption'
git merge --ff-only 'feature/realm-terminal-control-preparation'
git switch 'feature/original-stream-receiver-adoption'
git merge 'feature/realm-terminal-control-preparation'
git push origin 'feature/original-stream-receiver-adoption'
Sign in to join this conversation.
No description provided.