WIP: Mediate original device durability barriers #4

Draft
erikinkinen wants to merge 7 commits from feature/block-durability-barriers into feature/ci-source-acquisition
Owner

Carry explicit durability requests through the retained device transport and report only the device guarantees actually established. Keep the original provider and request lifetime attached to the durability boundary.

Depends on the preceding feature branch feature/ci-source-acquisition; this PR contains only the next feature in the stack.

  • Preserve the original source changes and squash dependency-pin churn.
  • Complete the feature acceptance checks and required regression coverage.

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

Carry explicit durability requests through the retained device transport and report only the device guarantees actually established. Keep the original provider and request lifetime attached to the durability boundary. Depends on the preceding feature branch `feature/ci-source-acquisition`; this PR contains only the next feature in the stack. - [x] Preserve the original source changes and squash dependency-pin churn. - [ ] Complete the feature acceptance checks and required regression coverage. This branch also includes the completed downstream features from #5.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:46:25 +01:00
feat: Mediate original device durability barriers
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 43s
aacb314c63
Carry explicit durability requests through the retained device transport and report only the device guarantees actually established. Keep the original provider and request lifetime attached to the durability boundary.
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 5s
CI / test (push) Failing after 52s
049c6b7b52
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 10s
CI / test (push) Successful in 2m53s
0e4a093c8e
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 20s
c26851937c
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 / markdown (push) Successful in 2s
CI / test (push) Successful in 1m7s
82a8bb0ff6
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 1m3s
b0a3d394e7
Integrate the reviewed prepared history into feature/block-durability-barriers. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#5
Author
Owner

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

Merged the approved downstream work from #5. The upstream PR retains its own remaining scope and completion 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 1m3s
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/block-durability-barriers:feature/block-durability-barriers'
git switch 'feature/block-durability-barriers'

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