/flow lists approved pulls waiting on the merge queue, stale crew pulls to fold back, and work a crew fork never proposed #11466

/flow now shows the three waiting sections for a forge admin who is a person. I did not run the full suite; the forge runs it on this push. bun x tsc --noEmit, scripts/gate.ts and the design lint are clean. The new test file, plus the unreached, valves and pure-module flow tests, pass.

What changed

• Existing modules: approvedWait, staleFold and alarmUnproposed were already on main with unit tests, but nothing called them. They are unchanged.
• New builder: src/web/pages/flow-waiting.ts reads the rows and draws one card. Each section has its own id.

- Approved, waiting on the merge queue: one row per repository with the count and the oldest wait, linking to the oldest pull. - Stale crew pulls: no push for 7 days, oldest first, each with the fold-back note and a link to its issue. It only proposes; a person closes. - Work a crew fork never proposed: the alarm's sentence, then a link to each branch. The branch name goes through encodeURIComponent, and the alarm reads branches with the branches page's helpers, so none reaches a shell.

• Empty sections: a quiet section draws nothing, and when all three are quiet there is no card.
• Mount: src/web/pages/flow.ts gets one line, plus its import. flowPage is now async because the branch read is async. The router already accepts promises, so nothing else changed.
• Unreached list: the three modules are gone from scripts/unreached-allow.json.
• Docs and tests: docs/features/flow-waiting.md is new. test/flow-waiting.test.ts has one test per section on the page HTML, plus one for the quiet lane.

What I chose not to do

• No new action: each row links to the pull, the issue or the branch rather than posting the fold-back note itself. Posting it would be a new mutation, which the issue did not ask for.
• Admin view not public-filtered: the page is admin-only, so I did not filter to public repositories.
• Two queries not reused: I copied the SQL of readOldestApproved and the idle-pulls reader into this file instead of changing those modules, so pulls on other flow modules do not collide.

How to try it: sign in as a forge admin and open /flow. Without any waiting work the page looks as before. With an approved crew pull, a crew pull idle for 7 days, or a crew-fork branch 6 h old with no pull, a card appears under the backup row.

The pre-push hook asked for a commit saying how to try the change, so the branch has an empty Try: commit.

🤖 Generated with Claude Code

Closes #11455

/flow now shows the three waiting sections for a forge admin who is a person. I did not run the full suite; the forge runs it on this push. bun x tsc --noEmit, scripts/gate.ts and the design lint are clean. The new test file, plus the unreached, valves and pure-module flow tests, pass.

What changed

• Existing modules: approvedWait, staleFold and alarmUnproposed were already on main with unit tests, but nothing called them. They are unchanged.
• New builder: src/web/pages/flow-waiting.ts reads the rows and draws one card. Each section has its own id.

- Approved, waiting on the merge queue: one row per repository with the count and the oldest wait, linking to the oldest pull. - Stale crew pulls: no push for 7 days, oldest first, each with the fold-back note and a link to its issue. It only proposes; a person closes. - Work a crew fork never proposed: the alarm's sentence, then a link to each branch. The branch name goes through encodeURIComponent, and the alarm reads branches with the branches page's helpers, so none reaches a shell.

• Empty sections: a quiet section draws nothing, and when all three are quiet there is no card.
• Mount: src/web/pages/flow.ts gets one line, plus its import. flowPage is now async because the branch read is async. The router already accepts promises, so nothing else changed.
• Unreached list: the three modules are gone from scripts/unreached-allow.json.
• Docs and tests: docs/features/flow-waiting.md is new. test/flow-waiting.test.ts has one test per section on the page HTML, plus one for the quiet lane.

What I chose not to do

• No new action: each row links to the pull, the issue or the branch rather than posting the fold-back note itself. Posting it would be a new mutation, which the issue did not ask for.
• Admin view not public-filtered: the page is admin-only, so I did not filter to public repositories.
• Two queries not reused: I copied the SQL of readOldestApproved and the idle-pulls reader into this file instead of changing those modules, so pulls on other flow modules do not collide.

How to try it: sign in as a forge admin and open /flow. Without any waiting work the page looks as before. With an approved crew pull, a crew pull idle for 7 days, or a crew-fork branch 6 h old with no pull, a card appears under the backup row.

The pre-push hook asked for a commit saying how to try the change, so the branch has an empty Try: commit.

🤖 Generated with Claude Code

/flow now shows the three waiting sections for a forge admin: approved pulls waiting on the merge queue, stale crew pulls with their fold-back note, and crew-fork branches that never headed a pull. The check failed on the "both doors" rule, which wants a terminal screen for every new web page. I added no screen and put a "No door:" line in a new commit message instead, as the rule allows. scripts/gate.ts now passes locally and the push went through; I haven't seen the forge's re-check yet.

The "No door" reason is that the section is an admin-only addition to the /flow web page, and the issue scopes it to the web. I left the terminal valves screen alone. If you want the terminal to show the same three lists, that would be a follow-up issue.

The code, tests and docs are unchanged since the first push, apart from that gate-satisfying commit.

🤖 Generated with Claude Code

All four points are addressed and pushed. tsc, gate.ts and design-lint are clean, test/flow-waiting.test.ts passes (9 tests), and 65 palette-related tests across 8 files pass. scripts/fast.ts said the diff was too broad to name, so I picked those tests myself and did not run the full suite.

What changed

1. Both doors. There is a new palette entry, "Waiting", in src/tui/screens/waiting.ts. It calls the same readWaiting and lists the same three sections as text, with empty sections omitted. It is offered only to a forge admin who is a person, and waitingLines returns nothing for anyone else. It is registered in ENTRIES in src/tui/screens/entries.ts and named in docs/features/flow-waiting.md.
2. Wrong repo on a stale pull. staleFold is now generic over its input, so each pull carries its own repo through and the pull-number-plus-branch map is gone. A new test uses two repositories with the same pull number and branch, and each keeps its own repo and age.
3. Unproposed scan cost. readWaiting now holds the scan result for 60 seconds per process. A branch has to be at least 6 hours old to count, so a minute of staleness changes nothing visible. The web page and the terminal screen share it. forgetUnproposed() drops it, and I added it to the process-memory list in AGENTS.md and to the feature doc. The other two sections are plain queries and are read every time. A test shows the scan is held at 5 seconds and re-read at 61 seconds.
4. Tests.

- A guest and a non-admin get no waiting card on the page. - An approval followed by a later changes_requested keeps the lane quiet. - The terminal lines are empty for a guest, a crew member and a non-admin.

1. Design. I dropped the stale and unproposed intro paragraphs. The stale row now ends "; a person closes it", and the unproposed row already says "old, no pull".

I did not change the terminal valves screen or the shape of alarmUnproposed; the cache wraps it.

Try it: as a forge admin, open /flow, or open "Waiting" from the terminal palette.

🤖 Generated with Claude Code

/flow now lists approved pulls waiting, stale crew pulls to fold back, and crew-fork work that was never proposed. It is an admin-only section of the web page, and the terminal has the same three lists as a palette screen.

The check failed because my terminal screen's palette entry was titled "Waiting", the same as the existing entry that lists account requests. That broke two tests:

• request-access-limits opened the wrong screen when it typed "Waiting".
• palette-roster found an extra entry that shifted the order.

The fix:

• I renamed my entry to "Pulls to land" (id pulls-to-land) and updated docs/features/flow-waiting.md to match.
• I added the entry to the palette-roster test's expected list.
• The two failing tests, palette-roster and request-access-limits, now pass, and so do the flow-waiting tests; scripts/gate.ts and tsc are clean.

The 21 failures in shard 29 were not run or fixed here. They are the a red many pulls share, a failure outside a named test and a snapshot's parts groups, plus variant-deck, which failed with SQLiteError: out of memory. They look like the check machine running out of memory rather than anything this pull touches. If they recur on this push, that is the cause to chase.

To try it: sign in as a forge admin and open /flow. With an approved, stale or unproposed crew pull, a card names it. In the terminal, press Ctrl+K and type "Pulls to land".