docs: Explain retained framebuffer check boundaries #5

Manually merged
Owner

Document how the inherited service-check workflow retains source and Cargo metadata owners through component checks. Describe the selected-source and catalog-provider recipes in the relevant README, architecture and roadmap sections.

  • Explain the source and metadata lifetimes through Cargo checks.
  • Distinguish explicit catalog identities from upstream main.
  • Keep physical resource admission and guest framebuffer acceptance open in the owning runtime feature.

Builds on owned framebuffer invocations. This PR changes documentation only.

Document how the inherited service-check workflow retains source and Cargo metadata owners through component checks. Describe the selected-source and catalog-provider recipes in the relevant README, architecture and roadmap sections. - [x] Explain the source and metadata lifetimes through Cargo checks. - [x] Distinguish explicit catalog identities from upstream `main`. - [x] Keep physical resource admission and guest framebuffer acceptance open in the owning runtime feature. Builds on [owned framebuffer invocations](https://git.erikinkinen.fi/erix/fbcond/pulls/4). This PR changes documentation only.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 04:06:44 +01:00
ci: retain source owners across framebuffer service checks
Some checks failed
CI / test (catalog) (pull_request) Has been skipped
CI / test (ci) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / test (ci) (push) Failing after 31s
CI / test (catalog) (push) Successful in 4m8s
9b08522cc7
Run complete host and native service checks through maintained original-source and Cargo owners. Keep ordinary CI and the explicit public framebuffer supplier graph as independent recipes; preserve authored main declarations and separate physical resource and guest acceptance.
ci: select public providers for both retained source checks
All checks were successful
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 14s
CI / test (catalog) (push) Successful in 8m53s
CI / test (public-feature-providers) (push) Successful in 8m46s
488fc93014
Keep the existing feature source and both complete service check matrices. Select the public feature providers through an explicit repository catalog.
ci: Select reviewed development source contexts
Some checks failed
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (catalog) (push) Has been cancelled
CI / test (public-feature-providers) (push) Has been cancelled
CI / markdown (push) Has been cancelled
24ff9f1260
Keep both retained service source recipes and their full command matrix while resolving each explicit companion context once.
ci: Declare policy helper and output boundaries
All checks were successful
CI / test (public-feature-providers) (push) Successful in 8m13s
CI / test (catalog) (push) Successful in 8m23s
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
bf4135c9c5
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.
docs: Clarify retained framebuffer check boundaries
Some checks failed
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 2s
CI / test (catalog) (push) Has been cancelled
CI / test (public-feature-providers) (push) Has been cancelled
1be8767cf1
docs: Wrap the framebuffer source-selection note
All checks were successful
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (public-feature-providers) (push) Successful in 3m43s
CI / test (catalog) (push) Successful in 3m53s
65b0a47006
erikinkinen changed title from WIP: Adopt retained framebuffer Cargo checks to docs: Explain retained framebuffer check boundaries 2026-11-13 02:54:51 +01:00
Author
Owner

The documents now describe their respective build, lifetime and roadmap boundaries without repeating the same generic paragraph. Both inherited source recipes complete, and this documentation change is ready for review. Runtime framebuffer acceptance remains with #4.

The documents now describe their respective build, lifetime and roadmap boundaries without repeating the same generic paragraph. Both inherited source recipes complete, and this documentation change is ready for review. Runtime framebuffer acceptance remains with #4.
docs: Explain the public CI provider catalog
All checks were successful
CI / markdown (push) Successful in 4s
CI / test (catalog) (push) Successful in 6m24s
CI / test (public-feature-providers) (push) Successful in 5m26s
852645883c
Retain the documentation from #6 on its current destination, which already contains the shared CI workflow changes.
docs: Merge Explain the public CI provider catalog
All checks were successful
CI / test (catalog) (pull_request) Has been skipped
CI / test (public-feature-providers) (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (public-feature-providers) (push) Successful in 4m14s
CI / markdown (push) Successful in 2s
CI / test (catalog) (push) Successful in 4m28s
fb6c35c9d1
erikinkinen manually merged commit 527e54adb1 into feature/owned-framebuffer-invocations 2026-11-21 06:11:44 +01:00
Sign in to join this conversation.
No description provided.