zara-coding: reject unsupported verification evidence statuses #359

Open
nsaspy wants to merge 0 commits from rage/244-evidence-status into main
Owner

RED-first slice for #244 under #1.

Exact RED head d173c6f924235444e04298cd31f5e95628074db5 requires unsupported verification status values to fail before any protocol write. Canonical passed/failed remain the intended typed outcomes.

No Core changes, shell/eval expansion, or cross-plugin runtime.

RED-first slice for #244 under #1. Exact RED head `d173c6f924235444e04298cd31f5e95628074db5` requires unsupported verification status values to fail before any protocol write. Canonical `passed`/`failed` remain the intended typed outcomes. No Core changes, shell/eval expansion, or cross-plugin runtime.
Some checks failed
CI / test (pull_request) Failing after 20s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/244-evidence-status:rage/244-evidence-status
git switch rage/244-evidence-status

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 main
git merge --no-ff rage/244-evidence-status
git switch rage/244-evidence-status
git rebase main
git switch main
git merge --ff-only rage/244-evidence-status
git switch rage/244-evidence-status
git rebase main
git switch main
git merge --no-ff rage/244-evidence-status
git switch main
git merge --squash rage/244-evidence-status
git switch main
git merge --ff-only rage/244-evidence-status
git switch main
git merge rage/244-evidence-status
git push origin main
Sign in to join this conversation.
No description provided.