Repository navigation
Open
Labels
documentationsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:docs-devrelAssigned to docs-devrel (Documentation & DevRel Engineer)Assigned to docs-devrel (Documentation & DevRel Engineer)wave1:P10Wave 1 PR group P10Wave 1 PR group P10wave:1-nextWave 1 — immediate next sprintWave 1 — immediate next sprint
Description
Problem
A fresh eShop fork cannot be driven fully autonomously from installation through /squad plan activate by one uninterrupted GitHub.com Agents-tab prompt because two required human gates remain: review/merge of the workflow-installation PR and review/merge of the generated Cast PR. GitHub documents steering an active cloud-agent session, but does not document an indefinite wait or automatic resume after a completed session/PR merge. Copilot-authored workflow changes also require a human Approve and run workflows action by default.
Evidence
- Squad prerequisites are on
devthrough PRs fix(gh-aw): install workflow runtime guards #2038, fix(gh-aw): gate merge continuation dispatch #2040, feat(gh-aw): automate Squad bootstrap #2041, fix(gh-aw): chunk bootstrap payload transport #2043, fix(gh-aw): bridge automatic bootstrap into triage #2044, Fix Fact Checker model resolution in plan validation #2045, and Fix failed validation lifecycle retry output #2046. - Current
devsources strict-compile as all seven source/lock pairs with only the documented dispatcher bot-trigger warning. - Reference journey: https://github.com/octodemo/eshop-bradyg-dev/blob/main/docs/squad-planning-journey.md
- Bootstrap run: https://github.com/octodemo/eshop-bradyg-dev/actions/runs/34909790188
- Activation run: https://github.com/octodemo/eshop-bradyg-dev/actions/runs/34987615314
- GitHub session docs: https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents
- GitHub workflow-approval docs: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/configuring-agent-settings#allowing-github-actions-workflows-to-run-automatically-when-copilot-pushes
Deliverable
Publish a copy/paste Agents-tab orchestration prompt that:
- Installs the seven supported
@devworkflows on an isolated branch. - Verifies the safe-update allowlist and performs approval plus a final plain strict compile.
- Stops at the installation PR with explicit human merge instructions.
- Resumes idempotently after merge, verifies bootstrap issue + draft Cast PR, and stops for Cast review/merge.
- Resumes after Cast merge, posts and monitors granular commands through
/squad plan activate. - Treats a completed/stopped Agents-tab session as requiring a new session seeded from repository/issue state rather than promising automatic continuity.
- Includes recovery checks for duplicate PRs/issues, failed runs with durable outputs, and activation issue-count verification.
Ownership and target
- Assignee: @bradygaster
- Target date: 2026-09-18
- Reviewer:
squad:agentic-workflows-devowner
Metadata
Metadata
Assignees
Labels
documentationsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:docs-devrelAssigned to docs-devrel (Documentation & DevRel Engineer)Assigned to docs-devrel (Documentation & DevRel Engineer)wave1:P10Wave 1 PR group P10Wave 1 PR group P10wave:1-nextWave 1 — immediate next sprintWave 1 — immediate next sprint
Activity
github-actions commentedon Sep 15, 2026
📋 Assigned to agentic-workflows-dev (Agentic Workflows Engineer)
Issue: #2048 — Document Agents-tab Squad bootstrap pause/resume journey
agentic-workflows-dev will pick this up in the next Copilot session.
bradygaster commentedon Sep 15, 2026
Cycle 2 correction: a Copilot App/Agents orchestration session that has a user-authenticated GitHub CLI/API credential can post the planning slash-command comments itself. GitHub attributes those comments and the resulting
issue_commentworkflow runs to the credential owner, so Squad’sgithub.actorcollaborator-permission gate authorizes triage, planning, acceptance, and activation when that user has write, maintain, or admin access. The default Copilot cloud-agent GitHub MCP token is read-only; a GitHub.com cloud session therefore needs an explicitly configured write-capable user token/tool, while the local Copilot App can use its authenticatedghsession. Human gates remain for workflow approval and merging the installation and Cast PRs.github-actions commentedon Sep 28, 2026
📋 Assigned to docs-devrel (Documentation & DevRel Engineer)
Issue: #2048 — Document Agents-tab Squad bootstrap pause/resume journey
docs-devrel will pick this up in the next Copilot session.
bradygaster commentedon Sep 28, 2026
Final readiness gates for the Agents-tab journey documentation:
devSHA.#2074/#2069 remain orthogonal and do not gate this documentation follow-through.
docs: add Agents-tab Squad journey
docs: correct Agents-tab Squad journey
docs: restore gh-aw documentation contracts
docs: restore hosted evidence placeholders
docs: pin Agents-tab workflow topology
13 remaining items
docs: add Agents-tab Squad journey
docs: correct Agents-tab Squad journey
docs: restore hosted evidence placeholders
docs: pin Agents-tab workflow topology
docs: restore pending hosted pin
docs: identify corrected hosted-rerun candidate
docs: record final review trust architecture
docs: correct review authority provisioning status
docs: bind Agents journey to review authority
docs: document Agents review trust journey
docs: reconcile native Squad review journey
docs: reconcile Agents guide merge conflict
Merge latest dev into Agents journey documentation