v2: prove frozen v1 and platform compatibility #17

Open
bryce wants to merge 6 commits from feature/v2-compatibility-next into feature/proxy-fencing-next
Owner

Adds an executable compatibility admission matrix for the immutable v1.0.1 baseline, proves old/current daemon-plugin-client interoperability, and records fail-closed Linux semantics plus explicitly compile-only non-Linux evidence.

Formal workflow state remains ready pending independent review. This PR does not publish v2.

Adds an executable compatibility admission matrix for the immutable v1.0.1 baseline, proves old/current daemon-plugin-client interoperability, and records fail-closed Linux semantics plus explicitly compile-only non-Linux evidence. Formal workflow state remains ready pending independent review. This PR does not publish v2.
bryce requested review from linus 2026-10-26 22:27:36 -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/v2-compatibility-next:feature/v2-compatibility-next"
git switch "feature/v2-compatibility-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/proxy-fencing-next"
git merge --no-ff "feature/v2-compatibility-next"
git switch "feature/v2-compatibility-next"
git rebase "feature/proxy-fencing-next"
git switch "feature/proxy-fencing-next"
git merge --ff-only "feature/v2-compatibility-next"
git switch "feature/v2-compatibility-next"
git rebase "feature/proxy-fencing-next"
git switch "feature/proxy-fencing-next"
git merge --no-ff "feature/v2-compatibility-next"
git switch "feature/proxy-fencing-next"
git merge --squash "feature/v2-compatibility-next"
git switch "feature/proxy-fencing-next"
git merge --ff-only "feature/v2-compatibility-next"
git switch "feature/proxy-fencing-next"
git merge "feature/v2-compatibility-next"
git push origin "feature/proxy-fencing-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!17
No description provided.