274 — tp overview: every level 3 story and idea across the forges, on one page (#274)

Why

Agent flow works end to end in one repository, and tp story query says where one story stands. Nothing shows every story and idea in flight. The human's attention is one pool across every project they work on, and the phases that need them, a called story and a story not yet defined, are found today by listing issues one repository at a time. The manual's overview is that one view, and is the first item of its epic "Agent flow 2": the level has to be seen working before it is tuned.

This story builds the part of the overview that the flow's labels and pull requests already answer. The rows that need something recorded that is not recorded yet (stuck and stale, landings since the human's review, dark features) wait for the stories that record it.

What changes

  • tp overview: serves one local page (lofigui) and prints its URL. Each load reads the forges afresh; the page does not refresh itself.
  • The page groups every open issue of the flow, in the order of what needs the human: called stories, stories not yet defined, raw ideas, roadmap items, stories in development, stories in review. Each row is the repository, the issue number linked to the forge, and the title; a story in review also links its pull request.
  • overview: in the user config (~/.config/task-plus/local.yaml): the forges to read, each a host, an owner and a token_env. Forgejo only. tp overview fetches the tokens itself, as tp release does.
  • A repository is covered when it belongs to a listed owner, has an open issue carrying one of the flow's labels, and its task-plus.yml on the default branch declares maturity.code: 3. No list of repositories is kept, and no checkout is read.
  • docs/overview.md, which the docs index lists; overview among the key commands in CLAUDE.md.

Acceptance

Which group an open issue is shown in. The repository is level 3; "pull request" is an open one whose head branch is story/<N>-… for issue N.

story called defined Other flow label Pull request Group
yes yes any — any called
yes no no — any not yet defined
yes no yes — none in development
yes no yes — open in review, with the pull request linked
no — — idea — raw ideas
no — — roadmap — roadmap items
no — — none — not shown

Which repositories are read:

Repository Outcome
owner listed, maturity.code: 3 on the default branch its issues shown
owner listed, a lower level or no task-plus.yml none of its issues shown, whatever their labels
owner listed, level 3, no open issue of the flow not on the page
owner not listed not read

The page and the command:

Condition Outcome
issues in every group, from two forges six groups in the order above, each with its count; within a group by repository, then issue number
a group with no issues its heading shown with "none"
the page loaded again after a label changed on a forge the issue is in its new group
one forge unreachable, or its token missing the page names the forge and why, and shows the other forges' issues
no overview: in the user config error naming the file and the three fields; nothing served
the port taken the next free port; the URL printed is the one served

Out of scope

  • The limit and the count against it (#275), and the refusal at the limit (the manual's "Agent flow 3").
  • The manual's other overview rows: stuck and stale stories, landings since the last human review, dark features.
  • Roadmap items in ROADMAP.md order, by epic: here they are by repository and issue number.
  • GitHub and GitLab: no repository of ours keeps the flow's issues there.
  • A text form for a terminal or an agent.
  • The manual's "Not built" line, in the manual's repository.

Decisions

none

Done when

  • tests express the acceptance table and pass
  • spec updated
  • ADR written if a fork was resolved
  • changelog entry
  • issue closed with a link to the release