Clarify component contracts #6

Open
erikinkinen wants to merge 7 commits from feature/component-contract-docs into feature/block-durability-barriers
Owner

Describe the component responsibilities and current durability contract in the shared documentation format. Keep historical dependency-selection details out of the component overview.

Depends on the preceding feature branch feature/block-durability-barriers; this PR contains only the next feature in the stack.

  • Preserve the original source changes and squash dependency-pin churn.
  • Check the component contracts, durability boundaries and shared documentation format.

This branch also includes the completed downstream features from #7.

Describe the component responsibilities and current durability contract in the shared documentation format. Keep historical dependency-selection details out of the component overview. Depends on the preceding feature branch `feature/block-durability-barriers`; this PR contains only the next feature in the stack. - [x] Preserve the original source changes and squash dependency-pin churn. - [x] Check the component contracts, durability boundaries and shared documentation format. This branch also includes the completed downstream features from #7.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:46:19 +01:00
docs: Clarify component contracts
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / test (push) Failing after 44s
6661415cc1
Describe the component responsibilities and current durability contract in the shared documentation format. Keep historical dependency-selection details out of the component overview.
docs: Describe outstanding durability evidence directly
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 50s
348f52ef44
Retain the authored, unrun controls and the original native acceptance
requirements. Describe the outstanding evidence without obsolete process notes.
ci: retain the public source graph on this feature branch
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 27s
CI / test (push) Successful in 2m43s
2d3ec26c73
Select the existing public providers without changing the feature source or its test matrix.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / test (push) Failing after 26s
7a99e74625
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.
Keep Cargo declarations on canonical internal main branches while CI retains exact selected original commits. Distinguish branch-context resolution from immutable catalog and CI-helper inputs, and remove obsolete manifest revision instructions.
ci: Select the provider policy explicitly
All checks were successful
CI / test (push) Successful in 1m10s
CI / markdown (push) Successful in 3s
5adda228b6
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: Clarify component dependency source selection
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 1m4s
12d2d9e0d9
Integrate the reviewed prepared history into feature/component-contract-docs. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#7
Author
Owner

Merged the approved downstream work from #7. The upstream PR retains its own remaining scope and completion requirements.

Merged the approved downstream work from #7. The upstream PR retains its own remaining scope and completion requirements.
erikinkinen changed title from WIP: Clarify component contracts to Clarify component contracts 2026-11-14 16:37:46 +01:00
Author
Owner

Reconciled the documentation with #5’s repaired runtime in the prepared branch. It preserves the completed #7 feature through a signed merge, keeps Cargo/native checks unchanged and removes stale dependency-pin and unrun-status text.

Removed WIP. The prepared head 48cdefc9 is ready for review; original branches remain intact. Mounted-device durability and guest rebuilding remain separate integration requirements.

Reconciled the documentation with #5’s repaired runtime in [the prepared branch](https://git.erikinkinen.fi/erix/blockd/src/branch/feature/clarify-component-contracts-merge-ready-48cdefc9). It preserves the completed #7 feature through a signed merge, keeps Cargo/native checks unchanged and removes stale dependency-pin and unrun-status text. Removed WIP. The prepared head `48cdefc9` is ready for review; original branches remain intact. Mounted-device durability and guest rebuilding remain separate integration requirements.
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 1m4s
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
  • ARCHITECTURE.md
  • ROADMAP.md
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/component-contract-docs:feature/component-contract-docs'
git switch 'feature/component-contract-docs'

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/block-durability-barriers'
git merge --no-ff 'feature/component-contract-docs'
git switch 'feature/component-contract-docs'
git rebase 'feature/block-durability-barriers'
git switch 'feature/block-durability-barriers'
git merge --ff-only 'feature/component-contract-docs'
git switch 'feature/component-contract-docs'
git rebase 'feature/block-durability-barriers'
git switch 'feature/block-durability-barriers'
git merge --no-ff 'feature/component-contract-docs'
git switch 'feature/block-durability-barriers'
git merge --squash 'feature/component-contract-docs'
git switch 'feature/block-durability-barriers'
git merge --ff-only 'feature/component-contract-docs'
git switch 'feature/block-durability-barriers'
git merge 'feature/component-contract-docs'
git push origin 'feature/block-durability-barriers'
Sign in to join this conversation.
No description provided.