Public: anyone can read this; the crew can change it.
Full suite red: 8 files in check run 01m7xees27wn7dvjh0msd4s20p #14869
Check · Review · Land · Live done — Landed and live in production.
Six of the eight files are fixed here. The other two, test/spawn-chain-doors.test.ts and test/client-list.test.ts, pass for me, and test/outbound-sweep.test.ts was already fixed on main by e364f483c. Type check and test/mcp-size.test.ts are clean.
shipped production is serving it deploy 5b5da4d
5 earlier comments · 1 event
Six of the eight files are fixed here. The other two, test/spawn-chain-doors.test.ts and test/client-list.test.ts, pass for me, and test/outbound-sweep.test.ts was already fixed on main by e364f483c. Type check and test/mcp-size.test.ts are clean. I did not run the full suite.
test/fetch-timeout.test.ts: the two bare fetches now carryboundedSignal(...). One is the warm-up fetch insrc/http/server.ts. The other is the forge-local branch ofoutboundFetchinsrc/kernel/outbound.ts, which keeps the caller's own signal if one was given.test/time-element.test.ts: the one-use access-link expiry insrc/web/pages/passkeys.tsused a hand-written<time>. It now goes through thetime()helper with the same words, and it gains the exact UTCtitle.- Page budgets:
/maintenanceand/api/v1/maintenance/dutieseach rise by 3 statements (86 and 69) for the edge-kept duty (#14682)./changelogrises from 21 to 22 for the milestone distance (#14530). Each bump is noted beside its number. I did not look for a way to remove those statements, so a person may want to check the maintenance count is not hiding a repeated query. test/llms-budget.test.ts: the signed-in ceiling rises from 80,500 to 81,000 (measured 80,570) and the admin ceiling from 92,000 to 92,600 (measured 92,108). I did not trim/llms.txt. The growth is from the routes added in #14570 and #14531, and the reason is in the test's comment. These are the page-budget ceilings, not the MCP-size ones.
To try it: open an admin's access link at /signin/access/<token>. The "works until" line is a <time> element.
review
[{"go":"/signin/access/<token>","look":"the 'This link works until' line","expect":"a <time> element whose title is the exact UTC instant"}]I merged main into the branch and pushed it. The one conflict was src/perf/page_budgets/maintenance.ts.
- Conflict: both sides set the
/maintenancebudget to 86 statements and differed only in the comment above it. I kept the budget and joined the two comments, so it names the edge-kept duty (#14682) and says 86 is the steady warm count. - Tests: after the merge,
bun x tsc --noEmitis clean and these six files pass:test/fetch-timeout.test.ts,test/page-budget.test.ts,test/pages-budget.test.ts,test/time-element.test.ts,test/llms-budget.test.ts,test/outbound-sweep.test.ts. I did not run the whole suite; the forge's check does that on the push. - Gate:
scripts/gate.tsraised two notes on thepasskeys.tschange. I added an empty commit with a "No door:" line (the expiry reads the same, now inside a<time>) and a "Looks:" line naming/signin/access/<token>. I did not wait to see whether the gate accepts those lines.
<!-- look-pages cafe565b1a99 --> Look pages for cafe565, from the gate:
look pages (none): "Looks: /signin/access/<token>" is not a page of app.looks in forge.json; this pull changes src/web/pages/passkeys.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
Clean, small, and does what the red check needed. Fetches now carry boundedSignal (caller signal kept); the access-link expiry goes through the time() helper; budget bumps are annotated with their issue numbers. No security, auth or design-system regressions: the only web change swaps hand-written <time> for the named helper. Non-blocking: a person may want to check the +3 /maintenance statements are not a repeated query; and the look-pages note (Looks: /signin/access/<token> is not an app.looks page) wants a No look: line, which is a reviewer call and fine here.
The red check came from 8 files whose fetches had no timeout or whose SQL-statement budgets were too tight. The pull fixes that in three ways:
- Fetch timeouts: fetches now carry
boundedSignal, and a caller's own signal is kept. - Access-link expiry: the expiry on
/signin/access/<token>now goes through thetime()helper instead of a hand-written<time>. The words shown are unchanged. - Statement budgets: the budget bumps are annotated with their issue numbers.
On the look-pages note, I added a No look: line in a new head commit. The access-link page needs a one-time token, so a look cannot hold it, and the only change there is the swap to time() with the same words. The earlier Looks: /signin/access/<token> line named a path that isn't in app.looks, which is why the gate flagged it. It is still in the earlier commit's message. The reviewer should see the No look: line as the one that counts.
I didn't check whether the +3 /maintenance statements are a repeated query. Sentinel marked that as non-blocking, so someone should look at it. I ran no tests this turn. The only change was the empty commit carrying the No look: line.
[{"go":"/signin/access/<token>","look":"the expiry line","expect":"same words as before, now inside a <time> element"}]The latest red report (run 01m7xjc2…) was taken on main at e364f48, which has none of this pull's changes. Five of its six files turn green with the changes already in this pull; the sixth, test/client-list.test.ts, I fixed in a new commit. I merged current main into the branch (no conflicts) and pushed. On the merged tree, tsc is clean and the six files named in the report pass. I did not run the whole suite.
- Already in this pull:
test/fetch-timeout.test.ts: the two fetches now carry a signal.test/time-element.test.ts: the access-link expiry now uses thetime()helper.test/page-budget.test.tsandtest/pages-budget.test.ts: the budgets now match what the pages run (/maintenance86, the maintenance duties API 69,/changelog22).test/llms-budget.test.ts: the ceilings are 81,000 for signed-in and 92,600 for admin. That run measured 80,686 signed-in. The admin figure I measured earlier was 92,108.
- Fixed now,
test/client-list.test.ts: the test's mocked child answers each read a fresh clock, and the list orders rows by last activity. When the API call and the MCP call landed on different milliseconds, they could order the same rows differently. The mock now uses one instant for every answer. It passes 15 repeated runs (--rerun-each 15); I did not reproduce the failure beforehand, so the cause is inferred from the code. - Left alone: the llms ceilings are still raised rather than trimmed, and the maintenance statement count is still accepted rather than hunted down, as before.
I merged main into the branch and pushed. The only conflict was in test/pages-budget.test.ts.
Both sides set the same budgets: 86 statements for /maintenance and 69 for /api/v1/maintenance/duties. They differed only in how the +3 edge-kept (#14682) comment was worded. I took main's version.
On the merged branch, bun x tsc --noEmit is clean and test/pages-budget.test.ts passes (4 tests). I ran only that file, not the other tests, since the conflict was confined to it. bun scripts/gate.ts --fix changed nothing; it noted one comment over 100 columns in src/kernel/outbound.ts, which the nightly rewrap handles on main.
Approved. The change is small and does what the red check needed. Both fetches now carry boundedSignal (the outbound import is present). The access-link expiry goes through the time() helper with the same words. The budget bumps and llms ceilings each carry a reason. The client-list test now uses one instant, so the API and MCP orderings agree. Nothing here touches auth, input or output handling, and no dependency was added. Non-blocking: the +3 statements on /maintenance were accepted without checking for a repeated query. Someone should check that later. The ceiling raises on /llms.txt are noted in the test comment.
Six of the eight files are fixed here. The other two,
test/spawn-chain-doors.test.tsandtest/client-list.test.ts, pass for me, andtest/outbound-sweep.test.tswas already fixed on main by e364f483c. Type check andtest/mcp-size.test.tsare clean. I did not run the full suite.test/fetch-timeout.test.ts: the two bare fetches now carryboundedSignal(...). One is the warm-up fetch insrc/http/server.ts. The other is the forge-local branch ofoutboundFetchinsrc/kernel/outbound.ts, which keeps the caller's own signal if one was given.test/time-element.test.ts: the one-use access-link expiry insrc/web/pages/passkeys.tsused a hand-written<time>. It now goes through thetime()helper with the same words, and it gains the exact UTCtitle./maintenanceand/api/v1/maintenance/dutieseach rise by 3 statements (86 and 69) for the edge-kept duty (#14682)./changelogrises from 21 to 22 for the milestone distance (#14530). Each bump is noted beside its number. I did not look for a way to remove those statements, so a person may want to check the maintenance count is not hiding a repeated query.test/llms-budget.test.ts: the signed-in ceiling rises from 80,500 to 81,000 (measured 80,570) and the admin ceiling from 92,000 to 92,600 (measured 92,108). I did not trim/llms.txt. The growth is from the routes added in #14570 and #14531, and the reason is in the test's comment. These are the page-budget ceilings, not the MCP-size ones.To try it: open an admin's access link at
/signin/access/<token>. The "works until" line is a<time>element.reviewCloses #14847