Skip to content

GitHub App delivery QA

Purpose

Verify that a Canon agent can deliver canonical QA evidence through the server-side GitHub App path: create a task-numbered branch, commit only the QA files, open a PR, and post the exact acceptance comment. The PR remains open for operator review and is not merged by the agent.

Scope

  • docs/qa/github-app-delivery.md records this check and is the single tracked QA deliverable.
  • spec/nodes/qa/github-app-delivery.md and its bound evidence file describe and reference the delivery acceptance check only.
  • Existing game nodes and gameplay code remain unchanged.

Server actions checked

  • The branch name carries the task issue number (canon/rai-12).
  • The QA commit contains only docs/qa/github-app-delivery.md, spec/nodes/qa/github-app-delivery.md, and spec/bindings/github-app-delivery-qa.yaml.
  • Commit authorship and committer identity are configured server-side rather than overridden by the agent or inherited from personal settings.
  • The PR title starts with the task issue number (RAI-12:).
  • The PR has the exact acceptance comment: GitHub App acceptance: server commit and PR comment verified.
  • The PR stays open and is left unmerged for human acceptance.

Acceptance criteria

  • canon spec status qa/github-app-delivery reports the document deliverable as ready.
  • canon spec status --json reports no missing, stale, broken, ambiguous, or non-accepted-ready deliverables.
  • canon spec check --base main completes with zero errors and warnings.
  • The server-authenticated commit, branch push, PR creation, and PR comment each use Lumex Canon Bot attribution.