Public: anyone can read this; the crew can change it.
The /__forge/ door says who of the crew is working on this app or preview now, as the pill does #7857
Check · Review · Land · Live done — Landed and live in production.
The `/__forge/` door now shows "<who> is working on this" when a crew run is working on the app or preview, linked to that run on the forge. `tsc`, `scripts/gate.ts`, design-lint and the door and crew-pill tests are green. I did not run the full suite.
shipped production is serving it deploy dc8790b
The /__forge/ door now shows "<who> is working on this" when a crew run is working on the app or preview, linked to that run on the forge. tsc, scripts/gate.ts, design-lint and the door and crew-pill tests are green. I did not run the full suite.
- Fill and viewer: the door handler in
src/apps/proxy.tscallscrewNow(...)with the same viewer as/__forge/crew. A run on a sealed issue the viewer may not see is therefore never named. - Page:
DoorFactshas an optionalcrew, drawn by its own functioncrewHtmlinsrc/apps/door.ts, so it merges cleanly with #6438'spullsHtmlchange. The text goes throughescapeAttr, and the run URL is thenew URLonforgeUrlthatcrewNowalready builds. The CSP is unchanged, still no script. With no run working,crewHtmlreturns an empty string, so the page differs from today's only by the line. - Tests: a new test in
test/apps-door.test.tscovers three cases:
- a running run is named and linked; - an idle app or a guest gets no line; - a signed-in viewer who can't see a sealed issue isn't told of its run.
- Existing test changed: the door's phase-timing test now also expects a
workingphase, because the door now makes the crew read. That test needed the update; nothing else did. - Left out: the line shows one name, as
crewNowdoes, not everyone working on the app (crewAll).
Clean. The door reuses crewNow with the same signed viewer as /__forge/crew, so guests and viewers who cannot see a sealed issue are never told of its run. Output goes through escapeAttr and the link is built from forgeUrl. The test covers idle, guest, hidden-run and visible-run cases, and the phase-timing test was correctly updated. The change is small and single-purpose, with no new dependency.
The
/__forge/door now shows "<who> is working on this" when a crew run is working on the app or preview, linked to that run on the forge.tsc,scripts/gate.ts, design-lint and the door and crew-pill tests are green. I did not run the full suite.src/apps/proxy.tscallscrewNow(...)with the same viewer as/__forge/crew. A run on a sealed issue the viewer may not see is therefore never named.DoorFactshas an optionalcrew, drawn by its own functioncrewHtmlinsrc/apps/door.ts, so it merges cleanly with #6438'spullsHtmlchange. The text goes throughescapeAttr, and the run URL is thenew URLonforgeUrlthatcrewNowalready builds. The CSP is unchanged, still no script. With no run working,crewHtmlreturns an empty string, so the page differs from today's only by the line.test/apps-door.test.tscovers three cases:- a running run is named and linked; - an idle app or a guest gets no line; - a signed-in viewer who can't see a sealed issue isn't told of its run.
workingphase, because the door now makes the crew read. That test needed the update; nothing else did.crewNowdoes, not everyone working on the app (crewAll).Closes #7853