Fix live rollback Manager evidence routing - #4
Merged
Merged
Conversation
Route the workflow through the Manager room and collect role-owned evidence only from the Manager and Team rooms.
WilliamClifton-dev
added a commit
that referenced
this pull request
Aug 22, 2026
…A-256 The P3 follow-up originally wrapped sigstore cosign (commit b30c303). On design review against docs/architecture/agentloom-architecture.md the cosign path was rejected. The architecture commits to a trust model of "evidence + self-attested digest + reproducible replay" (sections 6.1 #4, 12.1, 12.4, ADR-005); cosign is not in that model, and the project already publishes the submission SHA-256 in the GitHub release body — GitHub Releases with a published digest is the same trust model that PyPI and crates.io use, and it is the existing third-party anchor. This commit: - Rewrites docs/security/signing-submission.md to lead with the GitHub-Releases-plus-SHA-256 verification flow, with a four-step curl + shasum recipe and the cross-checks for a fresh-clone Lite gate. Records the three reasons cosign was rejected (architecture trust model, evidence-schema digest redundancy, GitHub-Releases already is a third-party anchor). - Adds deploy/signing/DEPRECATED.md explaining why sign-submission-package.ps1 is kept as an opt-in helper for operators with an internal sigstore requirement, and why it must not be wired into the public-main CI. - Patches deploy/signing/sign-submission-package.ps1 with a Write-Warning at the top so a future operator who reaches for it sees the deprecation notice before the script runs. The script itself is unchanged in behaviour. test-results.txt is byte-stable; ruff / mypy / pip-audit / pytest (376 passed / 3 skipped / 0 failed) all remain green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification
Live E2E status
The workflow reached the real Manager, but DashScope returned HTTP 503 for qwen3.7-plus on all four built-in retries. No role markers or success evidence were produced, and the failed run is not represented as successful.