v2: complete lease, fencing, and authenticated proxy candidate #16

Open
bryce wants to merge 13 commits from feature/proxy-fencing-next into feature/artifacts-placement-next
Owner

Scope

Completes the source candidate for v2-remote-execution.proxy-fencing without changing formal workflow state or publishing v2.

  • durable signed lease renewal and permanent node expiry fencing
  • signed operation catalogs and connection-bound route assertions
  • real delegated-cgroup routing and post-dispatch identity checks
  • bounded node-originated mTLS proxy stream with server-owned challenge
  • explicit ready/accepted publication handshake
  • canonical response correlation, stale/mixed denial, one-use stream and shutdown custody

Evidence

  • executable candidate: e81d19b315cd2fe5583e57e139c1b91c62f4d6bd
  • evidence/review head: ac487e0c88651fc169300af66b06c0b64f5b6789
  • full repository PASS; kernel 621.747s
  • affected race partitions PASS
  • vet, SDK, FreeBSD production build, workflow/docs and source manifest PASS

See workflow/features/v2-remote-execution.proxy-fencing/evidence/candidate-2026-10-26.md. Independent cold review is still required before formal admission.

## Scope Completes the source candidate for `v2-remote-execution.proxy-fencing` without changing formal workflow state or publishing v2. - durable signed lease renewal and permanent node expiry fencing - signed operation catalogs and connection-bound route assertions - real delegated-cgroup routing and post-dispatch identity checks - bounded node-originated mTLS proxy stream with server-owned challenge - explicit ready/accepted publication handshake - canonical response correlation, stale/mixed denial, one-use stream and shutdown custody ## Evidence - executable candidate: `e81d19b315cd2fe5583e57e139c1b91c62f4d6bd` - evidence/review head: `ac487e0c88651fc169300af66b06c0b64f5b6789` - full repository PASS; kernel 621.747s - affected race partitions PASS - vet, SDK, FreeBSD production build, workflow/docs and source manifest PASS See `workflow/features/v2-remote-execution.proxy-fencing/evidence/candidate-2026-10-26.md`. Independent cold review is still required before formal admission.
bryce requested review from linus 2026-10-26 22:20:05 -05:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin "feature/proxy-fencing-next:feature/proxy-fencing-next"
git switch "feature/proxy-fencing-next"

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/artifacts-placement-next"
git merge --no-ff "feature/proxy-fencing-next"
git switch "feature/proxy-fencing-next"
git rebase "feature/artifacts-placement-next"
git switch "feature/artifacts-placement-next"
git merge --ff-only "feature/proxy-fencing-next"
git switch "feature/proxy-fencing-next"
git rebase "feature/artifacts-placement-next"
git switch "feature/artifacts-placement-next"
git merge --no-ff "feature/proxy-fencing-next"
git switch "feature/artifacts-placement-next"
git merge --squash "feature/proxy-fencing-next"
git switch "feature/artifacts-placement-next"
git merge --ff-only "feature/proxy-fencing-next"
git switch "feature/artifacts-placement-next"
git merge "feature/proxy-fencing-next"
git push origin "feature/artifacts-placement-next"
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
agents/plugin-system!16
No description provided.