Skip to content

Add behavioral contracts for Squad activation label linkage #1960

Closed

Description

@bradygaster

Parent: #1957

Blocked by: implementation of temporary-ID targeting, fast-path parity, reporting, and capacity safeguards under this epic.

Problem

Existing tests primarily assert prompt phrases and frontmatter. That allowed an invalid assumption about returned issue numbers to pass while CI remained green.

Scope

Add focused tests that verify the compiled gh-aw contract and the linkage invariants for both activation paths.

Success criteria

  • Tests inspect compiled safe-output schemas/configuration, not only source prose.
  • Tests prove every new create_issue request has a unique temporary ID and its add_labels request targets the same ID.
  • Tests fail for omitted targets, implicit triggering-issue targets, duplicate temporary IDs, predicted issue numbers, or dependence on a synchronously returned real number.
  • Tests cover existing/reused issue targeting separately.
  • Tests cover base labels, roster labels, @copilot, multi-owner epics, non-roster omissions, truthful summaries, reruns, and capacity boundaries.
  • Both /squad plan activate and /squad activate are covered.
  • Targeted tests and strict compilation pass.

Out of scope

Live GitHub E2E execution and checker distribution.

Activity

  1. added
    squadSquad triage inbox — Lead will assign to a member
    type:choreMaintenance, refactoring, cleanup
    next-upPriority queue — next issues to work
    triagedIssue has been triaged
    gh-awGitHub Agentic Workflows integration
    on Aug 31, 2026
  2. github-actions commented on Sep 10, 2026

    @github-actions
    Contributor

    🔄 Ralph — Auto-Triage

    Assigned to: Flight
    Reason: No module, routing, or role keyword match — routed to Lead/Architect
    Source: lead-fallback

    Ralph auto-triaged this issue using routing rules.
    To reassign, swap the squad:* label.

  3. github-actions commented on Sep 10, 2026

    @github-actions
    Contributor

    🔄 Ralph — Auto-Triage

    Assigned to: Flight
    Reason: No module, routing, or role keyword match — routed to Lead/Architect
    Source: lead-fallback

    Ralph auto-triaged this issue using routing rules.
    To reassign, swap the squad:* label.

  4. github-actions commented on Sep 11, 2026

    @github-actions
    Contributor

    🔄 Ralph — Auto-Triage

    Assigned to: Flight
    Reason: No module, routing, or role keyword match — routed to Lead/Architect
    Source: lead-fallback

    Ralph auto-triaged this issue using routing rules.
    To reassign, swap the squad:* label.

  5. bradygaster commented on Sep 11, 2026

    @bradygaster
    CollaboratorAuthor

    Closing as completed following backlog cleanup: the associated fix, validation, or tracking work has been completed.

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

    gh-awGitHub Agentic Workflows integrationnext-upPriority queue — next issues to workpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a memberstatus:backlogBacklog itemtestingtriagedIssue has been triagedtype:choreMaintenance, refactoring, cleanup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions