Repository navigation
Description
Is there an existing issue for this?
- I have searched the existing issues.
What area does this task affect?
CI/CD
Task description
Make the Bugbot approval-receipt producer trust boundary explicit and reproducible. Deliver one independently reviewable result at the before any enforced activation stage.
Scope and acceptance criteria
- Write the exact trust claim and prerequisite for any future enforced profile. Distinguish authenticated run/data provenance, trusted executable/workflow revision and operator producer attestation; do not call a matching artifact an independent code attestation.
- Keep a runnable packaged regression for a fabricated clean current receipt with guarded policy and each changed path: bundle, workflow and action.yml. The decision must remain protected-path with zero approval writes, independently of any later stale-head fence.
- At least eight consumer/packaged cases cover those three protected edits, a foreign run, foreign SHA, foreign App, prior policy/attempt and the ordinary valid authorized producer path. Preserve same-SHA policy change and rollback fences.
- Document whether stronger producer evidence is required and any unavailable prerequisite. If architecture/public policy must change, use the official SDD review before implementation. This bounded audit must not invent or auto-enable an attestation system.
- Keep the existing verified result, human decisions, read-only shadow pilots and production disabled. This issue does not reopen the refuted broad claim as a proven approval exploit.
Current issues or inefficiencies
Run/repository/SHA/artifact identity is not independent attestation of producer code. The reported action-edit approval route was not reproduced: guarded-policy packaged controls reject edits to build/**, the workflow and action.yml as protected-path. The narrower producer-trust limitation remains.
Observed baseline: unreleased develop ccefb27627cd627ccdb7d5666fd174c2ac1da07b from merged PR #951.
- src/data/repository/pull_request/approval_bugbot_verification.ts
- src/data/repository/pull_request/pull_request_approval_repository.ts
- src/domain/pull_request_approval_policy.ts
- quality/bugbot/evidence/issue-950/cursor-rollback-shadow/packaged-rollback.cjs
Expected impact
Make this one pending result independently inspectable and reproducible, with its actual passed, failed or unavailable evidence.
Completion does not authorize release, producer trust, profile qualification from partial measurements, or production activation.
Additional context or comments
Priority and dependencies
- Priority: medium. Stage: Before any enforced activation.
- Blocked by: None; may be prepared independently.
- Follow-up to ✨🧑💻 - Verify Bugbot findings against repository evidence before publication #950 and merged PR feat: Verify Bugbot findings against repository evidence before publication (#950) #951, not a request to reopen or extend that delivery.
- Final closure and observed limitations. Review thread.
Documentation and implementation boundary
Documentation: docs/pull-requests/guarded-approval.mdx, docs/bugbot/quality-observability.mdx.
Keep Clean Architecture and current coverage/contract gates. When a later implementation changes a public contract, update its catalogued SDD, tests and docs together and validate specifications; update Graphify after code changes.
Read the effective #950 contract in the owning SDD and its current reconciliation amendments; historical pilot deadlines are not current investigation limits.
Fixed invariants and planning state
Backlog only: no in-progress, branch creation, model execution, deployment or activation requested by this planning step.
Keep BUGBOT_VERIFICATION_MODE=disabled. Evaluated PRs must have zero write attempts; retain frozen pilots and independent evaluator/oracle evidence.
Token usage is optional telemetry and cannot stop investigation or reject a supported verdict. Elapsed time and turn count do not impose research cutoffs; explicit cancellation and evidence/SHA integrity remain mandatory. Post-run latency qualification criteria remain distinct from session deadlines.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
Activity
[-]Make the Bugbot approval-receipt producer trust boundary explicit and reproducible[/-][+]🔧 - Make the Bugbot approval receipt producer trust boundary explicit and reproducible[/+]vypbot commentedon Nov 19, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]🔧 - Make the Bugbot approval receipt producer trust boundary explicit and reproducible[/-][+]🔧🧑💻 - Make the Bugbot approval receipt producer trust boundary explicit and reproducible[/+]vypbot commentedon Nov 19, 2026
Implementation plan
Acceptance: A reviewer can run the packaged regression and verify all required cases, including protected-path outcomes with zero approval writes for each protected edit; the trust-boundary documentation distinguishes provenance, trusted revision, and operator attestation, records any unavailable prerequisite, and confirms production remains disabled.
Need something else? Mention the bot with a question or use
/copilot help.chore-980-make-the-bugbot-approval-receipt-producer-trust-boundary-ex…
chore-980-make-the-bugbot-approval-receipt-producer-trust-boundary-ex…
chore-980-make-the-bugbot-approval-receipt-producer-trust-boundary-ex…
vypbot commentedon Nov 19, 2026
Progress · 75% estimated
Assessed head
6efac734· 6/10 supported0 need implementation · 4 need verification or clarification
Verification or clarification needed
Issue · Linked pull request · Full assessment