WIP: Retain Seriald requests through owned invocation lifetimes #12

Draft
erikinkinen wants to merge 3 commits from feature/owned-serial-invocations into feature/terminal-peer-flow-bridge
Owner

Seriald now registers its public history reader and root/log writers for owned requests before READY. Claimed requests retain their original serving operation through result completion, and driver/HAL/provider calls retain native invocation custody through collection and positive retirement. Provider capabilities are admitted from native collection receipts separately from service payloads.

  • Register ordinary intake and preserve canonical service schemas and response budgets.
  • Migrate driver, HAL registration and provider resolution to owned calls.
  • Preserve provider pinning, stream retention, newline policy and input cursor ownership.
  • Select an IPC provider that supplies Com1PeerFlowProgressV1 and IPC_DRV_SERIAL_OP_LINE_CONFIGURATION_V1, then complete the existing feature acceptance checks.
  • Complete owned private TTY and physical forwarding through a durable native serving-chain lifetime resource.
  • Demonstrate the composed service in the release image.

The remaining TTY and physical-control work is described in the owned invocation contract.

Seriald now registers its public history reader and root/log writers for owned requests before READY. Claimed requests retain their original serving operation through result completion, and driver/HAL/provider calls retain native invocation custody through collection and positive retirement. Provider capabilities are admitted from native collection receipts separately from service payloads. - [x] Register ordinary intake and preserve canonical service schemas and response budgets. - [x] Migrate driver, HAL registration and provider resolution to owned calls. - [x] Preserve provider pinning, stream retention, newline policy and input cursor ownership. - [ ] Select an IPC provider that supplies `Com1PeerFlowProgressV1` and `IPC_DRV_SERIAL_OP_LINE_CONFIGURATION_V1`, then complete the existing feature acceptance checks. - [ ] Complete owned private TTY and physical forwarding through a durable native serving-chain lifetime resource. - [ ] Demonstrate the composed service in the release image. The remaining TTY and physical-control work is described in [the owned invocation contract](https://git.erikinkinen.fi/erix/seriald/src/branch/feature/owned-serial-invocations/docs/owned-invocations.md).
erikinkinen added this to the Alpha 1 milestone 2026-11-06 04:45:13 +01:00
feat: Retain owned serial service invocations
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Failing after 56s
CI / markdown (push) Failing after 6s
fbfc8064ff
Register ordinary history and output receivers before readiness and retain each claimed operation through exact result completion or acknowledgment. Route driver and Deviced calls through actual owned submission, collection and positive retirement, keeping native capability receipts separate from opaque service payloads.

Preserve provider pinning and physical-control duties. The private TTY and physical forwarding migration remains dependent on a durable native serving-chain lifetime resource and matching providers.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
3f432ddc66
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: Declare policy helper and output boundaries
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 6s
CI / test (push) Failing after 1m26s
5f368ce80c
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 6s
CI / test (push) Failing after 1m26s
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/owned-serial-invocations:feature/owned-serial-invocations'
git switch 'feature/owned-serial-invocations'

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/terminal-peer-flow-bridge'
git merge --no-ff 'feature/owned-serial-invocations'
git switch 'feature/owned-serial-invocations'
git rebase 'feature/terminal-peer-flow-bridge'
git switch 'feature/terminal-peer-flow-bridge'
git merge --ff-only 'feature/owned-serial-invocations'
git switch 'feature/owned-serial-invocations'
git rebase 'feature/terminal-peer-flow-bridge'
git switch 'feature/terminal-peer-flow-bridge'
git merge --no-ff 'feature/owned-serial-invocations'
git switch 'feature/terminal-peer-flow-bridge'
git merge --squash 'feature/owned-serial-invocations'
git switch 'feature/terminal-peer-flow-bridge'
git merge --ff-only 'feature/owned-serial-invocations'
git switch 'feature/terminal-peer-flow-bridge'
git merge 'feature/owned-serial-invocations'
git push origin 'feature/terminal-peer-flow-bridge'
Sign in to join this conversation.
No description provided.