docs: Explain retained framebuffer check boundaries #5
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/fbcond!5
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/owned-framebuffer-cargo-provider-route"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
main.Builds on owned framebuffer invocations. This PR changes documentation only.
WIP: Adopt retained framebuffer Cargo checksto docs: Explain retained framebuffer check boundariesThe 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.