Skip to content

🔧🧑‍💻 - Prepare and verify trusted default installation of the serialized Bugbot status publisher #977

Description

@efraespada

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

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.

Activity

  1. moved this to Todo in vypdevon Nov 19, 2026
  2. changed the title [-]Prepare and verify trusted-default installation of the serialized Bugbot status publisher[/-] [+]🔧 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/+] on Nov 19, 2026
  3. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    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 help to see the available commands, or mention @vypbot with your question.

  4. moved this from Todo to In Progress in vypdevon Nov 19, 2026
  5. added
    branchedIndicates that a branch has been created for this issue.
    on Nov 19, 2026
  6. changed the title [-]🔧 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/-] [+]🔧🧑‍💻 - Prepare and verify trusted default installation of the serialized Bugbot status publisher[/+] on Nov 19, 2026
  7. added
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 19, 2026
  8. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Confirm rollout prerequisites
    2. Prepare a reviewed installation artifact
      • Create a minimal artifact through the established maintainer route without overwriting a changed workflow.
      • Pin publication code to the reviewed trusted revision and preserve runner policy, serialization, authorized wakeups, private PR access, and last-verified state.
    3. Define installation control outcomes
      • Cover absent, exact, incompatible or foreign, stale-source, denied-private-read, and duplicate or replaced-wakeup states.
      • Keep consumer defaults unchanged; do not add deployment, release, or verification-enforcement configuration.
    4. Capture authorized verification evidence
      • Run a native canary only on an explicitly authorized test PR; otherwise record evidence as unavailable.
      • Record the reviewed manifest and hash, destination SHA, and native result; keep production disabled and EV-07 independent.
    5. Document acceptance status
      • Update the relevant contract, tests, and documentation together if a public contract changes; validate specifications and update Graphify after code changes.
      • Report the result as passed, failed, or unavailable; a prepared artifact or develop merge alone does not pass installation acceptance.

    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.

  9. added
    size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.
    45%Progress: 45%
    and removed on Nov 19, 2026
  10. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Progress · 45% estimated

    Assessed head c7d6d6a2 · 1/11 supported
    1 need implementation · 9 need verification or clarification

    Implementation still needed

    • R15 · - [ ] Read the current authenticated default branch and workflow installation state; do not assume master or overwrite a changed workflow. Prepare a minimal reviewed installation a — Complete the coordinated maintainer review and installation route, and record its receipt and destination SHA. Requirement source · Evidence at assessed head

    Verification or clarification needed

    • R11 · Prepare and verify trusted-default installation of the serialized Bugbot status publisher. Deliver one independently reviewable result at the rollout prerequisite, not corpus prere — Independently verify installed readiness and record an authorized-canary outcome or its unavailability. Requirement source · Evidence at assessed head
    • R16 · - [ ] Keep publication code pinned to the reviewed trusted revision, the existing self-hosted runner policy, repository/PR serialization, source-authorized wakeups, private PR acce — Verify the pinned producer's authorized wakeups, private reads and last-verified preservation. Requirement source · Evidence at assessed head
    • R18 · - [ ] Record reviewed manifest/hash, destination SHA and native result. Installation/default-branch merge requires explicit maintainer authorization; do not add deploy, release or — Independently confirm the reviewed receipt and destination SHA, and record the authorized-canary result or its unavailability. Requirement source · Evidence at assessed head
    • R19 · - [ ] Production stays disabled and EV-07 remains independent. A prepared artifact or develop merge alone cannot close installation acceptance as passed. — Verify production remains disabled and EV-07 evidence remains independent. Requirement source · Evidence at assessed head
    • R32 · Make this one pending result independently inspectable and reproducible, with its actual passed, failed or unavailable evidence. — Independently verify the reported controls, packaged outcomes and actual installation evidence or its unavailability. Requirement source · Evidence at assessed head

    4 more pending requirements.

    Issue · Linked pull request · Full assessment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

45%Progress: 45%branchedIndicates that a branch has been created for this issue.chorein-progressStart work on an admitted issue.maintenancepriority: mediumImportant but not urgent, should be addressed soon.size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.state:workingWork can proceed on the verified branch or without a branch.

Projects

  • Status
    In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions