WIP: Retain original scope Close through provider refusal #99

Draft
erikinkinen wants to merge 3 commits from feature/original-scope-close-through-provider-refusal into feature/native-first-submission-ordering
Owner

A source audit found that Close refused a scope while any original child pin remained, including a blocked Wait pin. Transient provider cleanup refusal also propagated to the runtime fail-stop path. Dispose the complete original scope and its own candidates, abandon every older reply before fallible cleanup and retain only the actual Close reply boundary. Remove the permanent child-pin guard and consolidate duplicated scope disposal.

Refs #1. Depends on #98.

  • Include the implementation and its source changes.
  • Correct the concurrent module path: the selected source refers to missing src/exact_invocation/concurrent.rs, preventing formatting and compilation.
A source audit found that Close refused a scope while any original child pin remained, including a blocked Wait pin. Transient provider cleanup refusal also propagated to the runtime fail-stop path. Dispose the complete original scope and its own candidates, abandon every older reply before fallible cleanup and retain only the actual Close reply boundary. Remove the permanent child-pin guard and consolidate duplicated scope disposal. Refs #1. Depends on #98. - [x] Include the implementation and its source changes. - [ ] Correct the `concurrent` module path: the selected source refers to missing `src/exact_invocation/concurrent.rs`, preventing formatting and compilation.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 16:37:29 +01:00
fix: Retain original scope Close through provider refusal
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Failing after 11s
CI / test (push) Failing after 1m40s
df5d37d5eb
A source audit found that Close refused a scope while any original child pin remained, including a blocked Wait pin. Transient provider cleanup refusal also propagated to the runtime fail-stop path. Dispose the complete original scope and its own candidates, abandon every older reply before fallible cleanup and retain only the actual Close reply boundary. Remove the permanent child-pin guard and consolidate duplicated scope disposal.
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
44a3aeb2cb
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 10s
CI / test (push) Failing after 1m46s
683d8c00c0
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 10s
CI / test (push) Failing after 1m46s
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/original-scope-close-through-provider-refusal:feature/original-scope-close-through-provider-refusal'
git switch 'feature/original-scope-close-through-provider-refusal'

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/native-first-submission-ordering'
git merge --no-ff 'feature/original-scope-close-through-provider-refusal'
git switch 'feature/original-scope-close-through-provider-refusal'
git rebase 'feature/native-first-submission-ordering'
git switch 'feature/native-first-submission-ordering'
git merge --ff-only 'feature/original-scope-close-through-provider-refusal'
git switch 'feature/original-scope-close-through-provider-refusal'
git rebase 'feature/native-first-submission-ordering'
git switch 'feature/native-first-submission-ordering'
git merge --no-ff 'feature/original-scope-close-through-provider-refusal'
git switch 'feature/native-first-submission-ordering'
git merge --squash 'feature/original-scope-close-through-provider-refusal'
git switch 'feature/native-first-submission-ordering'
git merge --ff-only 'feature/original-scope-close-through-provider-refusal'
git switch 'feature/native-first-submission-ordering'
git merge 'feature/original-scope-close-through-provider-refusal'
git push origin 'feature/native-first-submission-ordering'
Sign in to join this conversation.
No description provided.