Skip to content

πŸ›πŸ§‘β€πŸ’» - Correct malformed workflow context in a new EV 07 corpus revisionΒ #985

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Pull Request

Which platforms are affected?

Linux, macOS

Description

The frozen EV-07 actions-readonly-metadata case claims a safe workflow but supplies root-level steps without jobs. The public #971 audit in PR #984 independently confirms malformed workflow structure. Read-only metadata permissions do not repair it.

Prepare one narrowly reviewed correction for a new corpus revision before #974. Preserve the original corpus.v1.json, labels, plans, predictions and failed scores byte-for-byte. Do not recategorize historical scorer rows or tune production prompts from this case alone.

Acceptance:

Reproducing the issue

Inspect the public audit row and observations at PR #984 head 6417074:
https://github.com/vypdev/copilot/blob/641707468d33e305b6b3efd8b35e797b8f00d41f/quality/bugbot/evidence/issue-971/adjudications.json

The supplied workflow has root steps and no jobs. GitHub places steps inside a job:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idsteps

Reproduce unchanged scores with node --test quality/bugbot/evidence/issue-971/audit.test.cjs.

copilot Version

Unreleased develop ccefb27; public evidence in #984. No release or qualified profile.

Additional context and comments

Derived from #971 under the authorized #950 execution goal; no duplicate was found for the exact case. Canonical index: #950 (comment) . Preserve all historical attempts and 27-issue traceability. BUGBOT_VERIFICATION_MODE remains disabled; zero model calls and evaluated-PR writes. No installation, release, activation, protection change or research time/turn/read/token cap.

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 [-]Correct malformed workflow context in a new EV-07 corpus revision[/-] [+]πŸ› - Correct malformed workflow context in a new EV 07 corpus revision[/+] 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. changed the title [-]πŸ› - Correct malformed workflow context in a new EV 07 corpus revision[/-] [+]πŸ›πŸ§‘β€πŸ’» - Correct malformed workflow context in a new EV 07 corpus revision[/+] on Nov 19, 2026
  9. added
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 19, 2026
  10. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Implementation plan

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

    1. Review project conventions and historical evidence
    2. Define the versioned corpus correction
      • Add a new 174-case corpus revision with stable case IDs and complete valid workflow context for the same scenario.
      • Document the derivation and diff; preserve corpus.v1.json, labels, plans, predictions, failed scores, and read-only metadata behavior byte-for-byte.
    3. Independently review expected results
      • Review the corrected case's expected result and retain the original malformed shape as causal evidence.
      • Limit controls to six: malformed original, corrected workflow, authorized read-only metadata, invalid structural negative, all stable IDs, and historical hashes.
    4. Update benchmark guidance and evidence
      • Update relevant benchmark guidance and catalogued evidence; use the official SDD review if the contract changes.
      • Preserve historical scorer rows and avoid production prompt tuning based only on this case.
    5. Verify and deliver through the Action workflow

    Acceptance: A reviewed new versioned 174-case corpus contains valid complete workflow context for the corrected case, an explicit derivation and stable IDs, while corpus.v1.json and all named historical artifacts retain their original hashes; the focused controls and required checks pass, and delivery includes final-SHA checks and review.

    Need something else? Mention the bot with a question or use /copilot help.

  11. added
    size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.
    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

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:workingWork can proceed on the verified branch or without a branch.

Type

Projects

  • Status
    In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions