Public: anyone can read this; the crew can change it.

The home opens on its lanes; a repository standing still is listed on /asks, where it can be turned off #13651

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

The owner, 2026-11-15, about the red "stuck" rows at the top of his home: the new stuck things on the front of the home page are annoying. there are going to be stuck repos. that is the thing.

Notes

shipped production is serving it deploy 59903fa

opened this

Direction

The owner, 2026-11-15, about the red "stuck" rows at the top of his home:

the new stuck things on the front of the home page are annoying. there are going to be stuck repos. that is the thing. this is a place to explore. i want to just turn off apps that dont work out too well. this section is cool but not on my home page. on mobile i have to scroll past them to see the active kanban. the kanban is what i like.

What a person sees on home now

  • The lanes come first, on every width. Under the page's own header (title, Lanes | Table, the app filter) the next thing is the kanban, or the table. On a phone (390 px) nothing sits above it. The box that tells the crew, the figures, the desk line and the rest follow the lanes, in that order.
  • No pile, no approved-and-not-landed row. The "stuck" lane-of-its-own with its forms and one row per pull is gone from /, and so is the "has sat approved" alarm.
  • One quiet line, only when the forge itself is broken. It sits in the header, and a healthy forge draws none (the old "Nothing needs you right now." is gone too). It reads 2 problems with the forge, a link to /asks#forge-broken, with the first sentence beside it cut to one line.

Exactly which kinds still show on home, and why

KindWhy it stays
red_mainmain is red: nothing lands
landing_stopped, lane_stoppedthe forge's own pipeline has stopped
backupdata at risk
no_releaseno release will go out
the proof's alarm (release not serving as it should)production is wrong
people stopped until you change a settinga second count on the same line (1 person is stopped until you answer, to /asks#asked). It is not the forge being broken: I kept it because that person can do nothing until an admin answers and they were told the admin sees it on home. Say the word and it leaves home too.

Removed from home: the stuck alarm (an approved pull sitting), the proof's notice (the release is serving; it is retried), "N waiting on you" (it is /review and the header's count). The set is one constant, FORGE_BROKEN in src/flow/alarms.ts. The line is drawn with the page, not live: it changes on the next load.

Where the rows went

/asks has three new sections after the asks (src/web/studio/standing.ts): Problems with the forge (the list the home's count links to), Stopped until you answer, and Standing still. The terminal's "How is my forge?" and the MCP forge tool carry the same rows from the same needsStack.

A repository standing still says one sentence: "trevato/scratchpad: 38 pulls nobody has touched since 2 Nov. Nothing new can start there until they move." Its row offers, as buttons: Re-check its pulls, Hand its pulls to builders, Close its stale pulls (their issues become ready again), and Turn this app off.

Turn this app off is the existing archive, not a second mechanism: takePileChoice(…, "off") calls setArchived. The app, its previews and its crew stop; the repository and its data stay; Restore in its settings, or archive {repo, archived: false}, turns it back on. That sentence is on the page under the rows. Three doors: the row's button (POST /:owner/:name/stuck, choice=off), MCP forge {apply: "stuck:<id>", choice: "off"} (planned first; an admin token to do it, as archive), and o on the terminal's needs screen (plan, then a yes).

A repository that is turned off is never counted as standing still (PILE_SQL), and its approved pulls are not counted as waiting (approvedPulls).

Tests

  • test/stuck-pile-doors.test.ts: the signed-in home has the lanes as the first element after its header, the stylesheet reorders nothing, and no stuck or approved row is on it; /asks lists the row with its buttons and the approved pull; turning an app off archives it, removes its row and stops counting it; MCP and terminal doors.
  • test/stuck-pile.test.ts: the sentence; off is planned first, an admin's, undone by waking.
  • test/home-flow.test.ts, home-quiet, home-kpi-row, home-no-shift, ask-admin, no-alarm-banner: moved to the new behaviour.
  • test/pages-budget.test.ts passes unchanged. On Linux under the release image: always-run set 1458 pass, looks 171 pass, 185 related files 1877 pass (one preview test failed once under load and passes alone).

Size

28 files. No terminal screen or page is added (the needs screen gains one key), and the pull changes src/flow/, so the 20-file rule does not apply; it is one purpose.

🤖 Generated with Claude Code

1 earlier comment · 1 event
Changes requested — before the latest push

Changes requested.

  1. First: turning an app off must not be one click. The web door (/asks, the off button posting to /:owner/:name/stuck) has to show OFF_SAYS and take a second explicit yes before it archives. The terminal and MCP plan first; the page should match. Add a test that a single POST without the confirmation does not archive.
  2. Direction: the owner's order is pipeline first (#6534, #6611, #5276, #3316, #6217, #6428, #1242, #1073) before any feature. This is a home-page and /asks feature. Say in the pull which pipeline item it serves, or rebase behind those.
  3. The pull rewraps unrelated comments in src/flow/lanes_read.ts and src/flow/alarms.ts. Keep that out of this change so the diff reviews cleanly.
  4. The diff I received was cut off before src/web/studio/standing.ts, the route handler and the tests. I could not read them. Ensure the POST handler checks same-origin and the session before off, that it checks admin for off only, and that the new /asks section escapes every output and works with JavaScript off.
commented

Comment rewrap unrelated to this pull. Drop it from the diff.

Done in 1cee231: every hunk that only re-wrapped a comment (22, in src/flow/alarms.ts, src/flow/lanes_read.ts and three test files) is back to main's text.

commented

Archiving is the one choice here that stops a whole app. Require a confirmation step on every door that can reach it.

Not added, on purpose: turning an app off is reversible (the repository and its data stay), and the owner asked on 2026-11-15 for exactly an easy one: "i want to just turn off apps that dont work out too well". 1cee231 answers the risk with an undo in place instead of a question before: on /asks the row becomes "<app> is off." with one button, Turn it back on; the MCP answer carries undo, the exact archive call; the terminal names the key, u. test/stuck-pile.test.ts turns an app off and on and finds it on, counted again and the crew allowed work there. So the test you asked for (a single POST must not archive) is not written; a single POST does archive, and a single POST undoes it. This is the owner's call if you still want the second step.

Approved

Both earlier asks are met. (1) The comment-only rewraps are gone from the diff. (2) The confirmation step on turning an app off is not added. The reason holds: the owner asked for an easy off, and it is undoable on every door. The web row offers Turn it back on, MCP returns undo, and the terminal has u. MCP off also needs an admin token, and setArchived checks the repository admin. I accept that. Home now opens on its lanes with one quiet line, and standing-still repos and week-old approved pulls moved to /asks and the terminal, as the direction wants. Archived repos are excluded from the pile and the approved list. Tests cover off, back on, and the counting. I could not read the diff since bdc83b86e5b7 in full: the clone is at main and the pull text was cut. I also could not check /asks on the preview, which answered 303 after 34 s. Non-blocking: that /asks latency is worth a look. Non-blocking: if the tell box, strip and forges line move below the lanes, check that nothing shifts on first paint.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs