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
Prepare and verify trusted-default installation of the serialized Bugbot status publisher. Deliver one independently reviewable result at the rollout prerequisite, not corpus prerequisite stage.
Scope and acceptance criteria
- Read the current authenticated default branch and workflow installation state; do not assume master or overwrite a changed workflow. Prepare a minimal reviewed installation artifact/PR through the established maintainer route; coordinate with existing setup update work Add safe installation updates to Setup Studio and CLI, preserving repository workflows and configuration #814.
- Keep publication code pinned to the reviewed trusted revision, the existing self-hosted runner policy, repository/PR serialization, source-authorized wakeups, private PR access and last-verified preservation. Consumer templates keep their current defaults.
- At least six controls distinguish absent, exact installed, incompatible/foreign installation, stale source, denied private read and duplicate/replaced wakeup. Link actual native canary evidence only when it has genuinely run on an explicitly authorized test PR.
- Record reviewed manifest/hash, destination SHA and native result. Installation/default-branch merge requires explicit maintainer authorization; do not add deploy, release or verification-enforcement configuration.
- Production stays disabled and EV-07 remains independent. A prepared artifact or develop merge alone cannot close installation acceptance as passed.
Current issues or inefficiencies
PR #951 delivered the short serialized writer on develop, but the inspected master snapshot lacked copilot_bugbot_status_card.yml. Packaged controls and live Check fallback do not prove installation or successful dispatch on the default branch.
Observed baseline: unreleased develop ccefb27627cd627ccdb7d5666fd174c2ac1da07b from merged PR #951.
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: Rollout prerequisite, not corpus prerequisite.
- Blocked by: 🐛🧑💻 - Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID #976
- 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.
Documentation and implementation boundary
Documentation: docs/bugbot/failure-scenarios.mdx, docs/security-operations/security/self-hosted-runners.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
[-]Prepare and verify trusted-default installation of the serialized Bugbot status publisher[/-][+]🔧 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/+]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.[-]🔧 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/-][+]🔧🧑💻 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/+]vypbot commentedon Nov 19, 2026
Implementation plan
Acceptance: A reviewed installation artifact records its manifest and hash, destination SHA, and native result, and documents all six control outcomes; installation acceptance is marked passed only after verified default-branch installation and genuinely run authorized native evidence, with explicit maintainer authorization for installation or merge.
Need something else? Mention the bot with a question or use
/copilot help.chore-977-prepare-and-verify-trusted-default-installation-of-the-seri…
vypbot commentedon Nov 19, 2026
Progress · 45% estimated
Assessed head
c7d6d6a2· 1/11 supported1 need implementation · 9 need verification or clarification
Implementation still needed
Verification or clarification needed
4 more pending requirements.
Issue · Linked pull request · Full assessment