App: project-level page with PR / issues panels + agent dispatcher (controlplane)

[heavygee]

Problem

"Projects" in the current UI are just session containers. For a git-attached project there's a real meta-layer that's invisible: open PRs (yours / others), open issues, recent CI runs, branch state. The operator currently checks GitHub directly, which is friction and breaks the "stay in HAPI" flow.

Proposal

A dedicated Project page for git-attached projects with:

Widgets

1. Open PRs panel -- yours / others, status (draft / open / changes-requested / approved), last activity, CI state.
2. Open issues panel -- yours / assigned-to-you / unassigned, label filters.
3. Recent activity feed -- commits, PR comments, issue updates -- chronological.
4. Spawn agent from idea -- a "new agent" button with a prompt textbox, creates a session in the project with the initial concept.
5. Inter-session graph -- shows which sessions are working on which PRs/issues (via UX: TL;DR-first response rendering with expand-to-full setting #9 references).

Dispatcher behaviour

• Watch GitHub activity via webhook or poll.
• Surface "PR has new review comment", "CI failed on your branch", "Issue assigned to you".
• Optional auto-dispatch: when configured, "PR has changes-requested" automatically spawns a peer agent to address the review.

Meta-agent skill

A dedicated github-meta agent skill (consultable from other agents) that knows how to:

• Enumerate open PRs/issues for a repo
• Fetch a PR's review comments
• Trigger reruns of CI workflows
• Cross-reference PRs to the sessions working on them

Reference agent in session 82a4fe63 for prior art.

Acceptance

• Project page renders for any session whose project has a .git directory
• PRs and issues panels populated via gh CLI or GitHub API
• Spawn-agent button works and the new session links back to the project page
• GitHub activity feed refreshes on a polling interval (default 60s) or via webhook
• github-meta skill registered and callable from other agents

Notes

• This is the controlplane / overseer notion. Project page = the operational dashboard.
• Pair with UI: things-to-do inbox with keyboard shortcut and auto-routing agent #6 (agent files future ideas) -- ideas filed by agents show up in the issues panel.
• Pair with UX: TL;DR-first response rendering with expand-to-full setting #9 (@session refs) -- the inter-session graph uses these.
• See related: chat search + memory for the dispatcher itself in App: project-level page with PR / issues panels + agent dispatcher (controlplane) #14.

[heavygee]

Fleet Overseer architecture cross-reference (#19)

The Overseer architecture treats "the Overseer IS the controlplane, with voice as its native UI." This project-page / dispatcher work is adjacent controlplane surface; its dashboard + GitHub-activity widgets land around Steps 3-4 (#25, #26). Cross-referenced rather than absorbed — see the umbrella #19 for the full build sequence.