Skip to content

πŸ›πŸ§‘β€πŸ’» - Bind Bugbot qualification execution to the pinned source and sanitized Git environmentΒ #970

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Pull Request, Commits

Which platforms are affected?

Linux, macOS

Description

The EV-07 source check inherits GIT_* variables, while the older normal-flow shadow runner loads root/src and records HEAD without proving those are the executed bytes. A redirected Git worktree or dirty source can weaken campaign provenance. No existing negative campaign becomes qualified by fixing these guards.

Scope and acceptance criteria

  • Sanitize Git process environment and local config influence consistently; prove the actual repository/source/lockfile against the selected committed pin before importing application modules or dispatching a model.
  • Use one reusable provenance check at these two existing boundaries. Record commit, tree, lockfile and actual driver/runtime digests; preserve historical runners and ledgers at their frozen commits.
  • At least 12 deterministic fixture controls cover clean admission; dirty, staged and untracked source; changed lockfile; foreign GIT_DIR/GIT_WORK_TREE/GIT_INDEX_FILE; injected Git configuration; missing pin; and refusal before imports/model work. No real model calls.
  • Document new-campaign reproduction and failure diagnostics. No new public Action setting or benchmark threshold change.

Reproducing the issue

Inspect requirePinnedImplementation in ev07-shadow/implementation.cjs and module loading in normal-flow-shadow/run.cjs. In a temporary Git fixture, keep a clean alternate worktree, dirty the actual source, and set GIT_WORK_TREE or GIT_DIR before the check. Also modify the application source or lockfile without changing HEAD.

Pinned source references:

copilot Version

Unreleased develop at ccefb27627cd627ccdb7d5666fd174c2ac1da07b (PR #951); this is not a released or activated profile.

Additional context and comments

Priority and dependencies

Documentation and implementation boundary

Documentation: docs/development/testing.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. added
    bugSomething isn't working
    bugfixSomething isn't working
    priority: highCritical issue, needs immediate attention.
    on Nov 19, 2026
  2. added theissue type on Nov 19, 2026
  3. moved this to Todo in vypdevon Nov 19, 2026
  4. changed the title [-]Bind Bugbot qualification execution to the pinned source and sanitized Git environment[/-] [+]πŸ› - Bind Bugbot qualification execution to the pinned source and sanitized Git environment[/+] on Nov 19, 2026
  5. 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.

  6. moved this from Todo to In Progress in vypdevon Nov 19, 2026
  7. added
    branchedIndicates that a branch has been created for this issue.
    on Nov 19, 2026
  8. 20 remaining items

  9. added
    size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.
    and removed
    size: XLIndicates that the issue or task is extra large in scope and complexity.
    on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

65%Progress: 65%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingin-progressStart work on an admitted issue.priority: highCritical issue, needs immediate attention.size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.state:awaiting-maintainerstate:blocked

Type

Projects

  • Status
    In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions