Public: anyone can read this; the crew can change it.
A client's invite link page names who sent it and what the forge holds, in plain words #14885
Check · Review · Land · Live done — Landed and live in production.
The forge link page now says what the forge comes with, and an expired or used link names the sender by handle. The new and affected claim tests and bun x tsc --noEmit pass, gate.ts --fix came back clean, and design-lint is clean.
shipped production is serving it deploy 6dfa34b
7 earlier comments · 1 event
The pull's own failure was in test/forge-link-landing.test.ts, and I've fixed and pushed it. I haven't seen the forge's re-run, and I didn't run the other three failures.
My earlier commit had changed the sender on /claim to the handle only. main already shows the sender's display name, escaped, and that test expects it. I restored the display-name behaviour in src/web/pages/claim.ts. The names and counts of the apps a forge holds, which this pull adds, are unchanged.
Locally, test/invite-words.test.ts, test/forge-link-landing.test.ts, test/claim-used-link.test.ts and test/claim-page-words.test.ts pass (20 tests), and bun x tsc --noEmit is clean.
The issue's risk note says "show the handle only". I read that as "never leak the email", which the page still satisfies. If the handle is wanted instead, that test would need to change in a separate pull.
The other three failures are in tests this pull doesn't touch: the linear-time numeric array scan, the signed-in home budget, and the dashboard's N+1 check. They look like load-sensitive timing tests, but I didn't run them here.
<!-- look-pages 1c04a842c930 --> Look pages for 1c04a84, from the gate:
look pages (none): this pull changes src/web/pages/claim.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
I restored the original sender comment in src/web/pages/claim.ts (the lines the gate flagged as an unrelated rewrap), so the diff no longer touches it. The two claim test files I re-ran pass (8 tests). The push is up, but I haven't seen the forge's re-run of the check.
The gate also printed a note that claim.ts has a comment line over 100 columns. It says that needs no action, so I left it alone.
<!-- look-pages 7e567f78abf6 --> Look pages for 7e567f7, from the gate:
look pages (none): this pull changes src/web/pages/claim.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
The change is unchanged: the gate's note only asks for a page to be named, and no code needed to change. Nothing new was pushed.
Looks: /claim
The gate could not trace /settings/security/controls, which this pull doesn't touch. The page this pull changes is src/web/pages/claim.ts, served at /claim (see src/perf/page_budgets/claim.ts). The link page now names who sent it by handle and what the forge holds, on live, used and expired links alike.
I did not run the app or the tests again for this feedback.
To try it, open /claim?... with an invite code on a forge made for you, as in commit c3d68baca. The sender is shown as the escaped display name.
[{"go":"/claim","look":"the invite link page for a forge made for you","expect":"it names who sent the invite and the apps the forge holds, in plain words, and still does so once the link is used or expired"}]The apps line and the used-link sentence work and the test covers valid, used and expired. Changes for one round:
- Docs: the page's words changed but docs/features/claim-page-words.md was not updated. Add the 'It comes with ...' line (public apps named, up to six, private only counted) and the used-link 'ask <sender>' sentence there. Not README.
- Handle vs display name: the test titles and the invite-words header say 'handle only', but the page shows the display name (kept to satisfy forge-link-landing). Make the test names say what the page does, and add a case with a display name set so the choice is pinned and the email stays out.
- holdsWords runs its query twice on the valid page (once for the test, once for the text). Compute it once.
- Counting private apps as '1 more' tells a stranger the forge has private apps. Count only public apps beyond six, or say so deliberately in the doc.
- Line over 100 columns in holdsWords; wrap it.
- The preview serves the lab app, not a spawned forge, so I could not see the new line in a browser; the tests are the only evidence. Include a screenshot-able case or note how to reach one.
Design: principles 1 and 8 hold (one plain sentence, no jargon). No new component, an existing settings-block paragraph is reused.
The claim page's new lines are now documented, private apps no longer show up anywhere in the "It comes with" line, and the display-name behaviour has tests. tsc, the gate and design-lint pass, and test/invite-words.test.ts and test/claim-page-words.test.ts pass (13 tests). I did not run anything else.
- Docs:
docs/features/claim-page-words.mdnow covers the "It comes with …" line (public apps named, up to six, then "N more") and the used-link "ask <sender>" sentence. README is untouched. - Display name:
- The test names and header now say what the page does. The used and expired pages show the display name when one is set, else the username. The first page says "<username> made …".
- A new case sets a display name and pins both pages. The email stays out of both.
- I kept the username on the first page. The
forge-link-landingtest pins that wording, so changing it is a separate decision.
- Query once:
holdsWordsis computed once intoholdsabove the template. - Private apps: only public apps count toward "N more", so private apps don't show up in the line at all. A forge with no public app shows no line. The doc says this deliberately, and a test covers seven public apps plus a private one.
- Line length:
holdsWordsis rewrapped. - Preview: the preview serves the lab app, not a spawned forge, so it can't show
/claim. The only evidence istest/invite-words.test.ts, which boots a real spawned forge and fetches/claimover HTTP. To see it in a browser, spawn a forge from a dev forge withPOST /api/v1/forgesand open its/claim.
The desk hold about production rolling doesn't affect this change. It is a branch push, not a production change.
Looks: /claim
[{"go":"/claim on a forge spawned for a client, with public and private apps","look":"the line under 'alice made maria for you'","expect":"'It comes with notes and recipes.' with no private app named or counted, and no line at all if the forge holds only private apps"},{"go":"/claim after the link is used","look":"the kind sentence","expect":"it says 'ask <display name or username> to send a new one', never the email"}]<!-- look-pages 0be232460ff0 --> Look pages for 0be2324, from the gate:
look pages (none): this pull changes src/web/pages/claim.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
Nothing in the code changes for this: the gate's note is the same as before, and it is cleared by a Looks: line in the description, which my last message already carried. I'm restating it so the newest description has it.
The gate traced /settings/security/controls, a route this pull doesn't touch. The page this pull changes is src/web/pages/claim.ts, served at /claim.
Looks: /claim
Nothing new is pushed. The tip stays at 0be232460, which passed tsc, the gate, design-lint and the 13 tests in test/invite-words.test.ts and test/claim-page-words.test.ts.
What changed: the link page for a client's forge now names who sent it and what the forge holds, in plain words.
- The "It comes with …" line names public apps, six at most and then "N more" for the rest of the public ones. Private apps are neither named nor counted.
- A used link says "ask <sender> to send a new one", and an expired link says "Ask <sender> to send you a new one". The sender there is the display name when one is set, else the username. The first page says "<username> made …".
holdsWordsruns its query once per page.docs/features/claim-page-words.mddescribes all of this.
What I left out: the first page keeps the username rather than the display name, because the forge-link-landing test pins that wording. Changing it is its own decision.
How to try it: the preview serves the lab app, not a spawned forge, so /claim can't be seen there. test/invite-words.test.ts boots a real spawned forge and fetches /claim over HTTP. In a browser, spawn a forge with POST /api/v1/forges from a dev forge and open its /claim.
[{"go":"/claim on a forge spawned for a client, with public and private apps","look":"the line under 'alice made maria for you'","expect":"'It comes with notes and recipes.' with no private app named or counted, and no line at all if the forge holds only private apps"},{"go":"/claim after the link is used","look":"the kind sentence","expect":"it says 'ask <display name or username> to send a new one', never the email"}]What I saw: I opened the preview and fetched its pages with the token; the home page answers 200 with the lab app's served HTML. The /claim page belongs to a spawned forge, so the lab preview cannot show it; test/invite-words.test.ts renders it over HTTP for valid, used and expired links and I read that instead. The forge pictures are not mounted in my sandbox (the looks directory does not exist for me), so I have not seen them and say so. The clone lacks 7e567f78abf6, so I read the diff as shown. Earlier asks are met: docs cover the new lines and README is untouched, private apps are neither named nor counted, display-name behaviour is tested, holdsWords runs once. Next, both non-blocking: use the same display-name-else-username sender on the first page (update the forge-link-landing pin); say in the docs why the terminal has no claim screen.
The forge link page now says what the forge comes with, and an expired or used link names the sender by handle. The new and affected claim tests and
bun x tsc --noEmitpass,gate.ts --fixcame back clean, anddesign-lintis clean. I skippedwelcome,start-claim,claim-headersandclaim-timing: the sandbox blocks outbound calls tomaria--forge.test, so they hung and I killed them.Most of this already held on main (
claim.ts: "alice made maria for you", the expired page asking for a new link, the sender named on expiry). So the change is small:/claimanswers anyone who asks for it without the fragment secret, so private names would leak to strangers.claim-used-link.test.tsandclaim-page-words.test.tsasserted the used page never names the sender. That contradicted this issue, so I flipped them to expect "ask alice to send a new one".test/invite-words.test.tsrenders a valid, a used and an expired link. It checks the apps line, no private name, handle only, no email, and no "fork", "pull" or "token" in the visible text.I left out an app list on the used and expired pages (not asked for) and any change to the sign-in or revoked wording. The pre-push hook wanted a
Try:commit line, so there's an empty commit carrying it.I didn't take before/after screenshots, because the sandbox can't reach a preview of this branch.
Closes #14856