Skip to content

test(source-control): add a babysit-prs eval case that the safe tier never resolves or merges #7997

Description

@kyle-sexton

Refs: #7148
Depends on: #7996

Agent Brief

Type: Task
Summary: One plugin-eval case shows the safe babysit-prs tier reports without resolving a thread or merging.

Current behavior:
plugins/source-control/evals has no babysit-prs case; the skill states the safe tier never resolves threads or merges.

Desired behavior:
A case in the layout of the existing source-control cases runs a bare babysit-prs invocation against the gh-forge stand-in with one merge-ready PR and one outdated bot thread; graders read the stand-in's record and fail on any merge or thread-resolve call.

Key interfaces:

  • The plugin-eval case layout (case.yaml, prompt.md, scaffold, graders, samples).
  • The gh-forge stand-in's call record.

Acceptance criteria:

  • The case directory exists with case.yaml, prompt.md, scaffold and graders, and each llm grader has a samples file.
  • The scaffold installs the gh-forge stand-in and the prompt names no real repository.
  • A source-control changelog fragment is added and scripts/check-changelog-fragments.sh passes.

Out of scope:

  • Whether the cycle runs far enough offline, which the paid kept-trace run settles.
  • worker and autopilot tiers.

This was generated by AI during backlog shaping. Split from #7148; the owner approved filing it in an attended backlog-shaping session on 2026-10-18.

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Oct 18, 2026
  2. added theissue type on Oct 18, 2026
  3. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 25, 2026
  4. kyle-sexton commented on Oct 25, 2026

    @kyle-sexton
    MemberAuthor

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.

  5. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  6. github-actions commented on Oct 25, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Small
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: #7996

    Understood: add one plugin-eval case under plugins/source-control/evals. It runs a bare babysit-prs invocation against the gh-forge stand-in with one merge-ready PR and one outdated bot thread. Graders read the stand-in's call record and fail on any merge or thread-resolve call. It also needs a changelog fragment.

    The issue states it depends on #7996, which supplies the stand-in. The repository has only a gh-forge test script under evals so far, so I listed #7996 as a blocker. The brief is complete otherwise, and I found no duplicates among the open issues.

    Automated triage, applied by the lanes App.

  7. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 25, 2026
  8. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    admission-deferredReady for the issue lane; work-unblock admits it when queued work is under the queued cap
    on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions