Public: anyone can read this; the crew can change it.
The sitemap lists /explore and every public repository's page #4120
/sitemap.xml now lists /explore. Each public, unarchived repository's home also carries a taken from its last push. bun x tsc --noEmit and test/standards.test.ts pass (16 tests).
stopped closed without shipping deploy de81220
Held
holds this, : steward tick: red on its own merge with main (the queue gated it alone and it failed); held so the queue lands the rest - rebase, fix, push, then the hold comes off
No rule sends it to review or lands it until it is released. A person can still ship it.
7 earlier comments · 1 event
The full gate on land was red; the pull is open again. Red tests:
- branches on a mirror go through the origin > deleting a branch removes it upstream first
- the crew, with a stand-in Claude Code: already done > (unnamed)
- branches on a mirror go through the origin > deleting a branch removes it upstream first [142.55ms] [shard 201]
- the crew, with a stand-in Claude Code: already done > (unnamed) [6.08ms] [shard 203]
- the crew, with a stand-in Claude Code: already done > (unnamed) [0.26ms] [shard 203]
/sitemap.xml now lists /explore and each public repository's page, with the repository's last push as lastmod. The list is capped at 50,000 URLs. This push only removes the timing assertion from the cold-build test.
- Timing assertion: I removed the
expect(ms).toBeLessThan(500)check fromtest/standards.test.ts, as @juniper asked. TheEXPLAIN QUERY PLANtest still pins the last-push lookup to theevent_repo_kind_timeindex. The cap, the entry order and the kept body are still asserted. - Seed suite cost:
test/standards.test.tsruns in about 5 s locally. I left the 50,100-repo seed at that size and did not check its cost in the forge check. - Migration timestamp:
20261022120000-event-last-push.tsis the newest file insrc/core/migrations. I did not check it against the release cut. - Red tests from the full gate: I did not change anything for the branch-deletion-on-a-mirror and "already done" crew failures. Both suites pass when I run them here:
test/branches.test.tsandtest/crew-already-done.test.ts, 16 of 16. My change touches only the sitemap, listings and the migration, none of which those suites cover. The failures were reported on shards 201 and 203 and look like load-dependent flakes. If they stay red on this push, the forge's log is the next place to look.
To try it, open /sitemap.xml on the preview.
🤖 Generated with Claude Code
Preview /sitemap.xml answers 200 as application/xml with / and /explore, escaped, security headers intact. Public-only and archived exclusion reuse PUBLIC_VISIBLE, outputs are escaped, the index migration is additive, and tests cover explore, lastmod, archived, the cap, the query plan and the kept body. No web UI is touched, so the design system is not in play. Two next steps: (1) the seeded 50,100-repo suite costs about 5s on every run, so consider shrinking it by parametrising the cap, or confirm its cost in the forge check; (2) warm the kept sitemap body in the background so the first crawler hit each minute does not pay the ~120ms cold build.
The full gate on land was red; the pull is open again. Red tests:
- browsing an origin repository on the web > the origins paths route answers for the account that connected it
- browsing an origin repository on the web > a native repository names two places, not three
- browsing an origin repository on the web > Mirror from a browse lands on a job page with a live checklist
- browsing an origin repository on the web > after the mirror, the workbench is where the page reads from
- browsing an origin repository on the web > pinning fills the third place with a diamond
- browsing an origin repository on the web > every where trail is drawn from §5's where strip, not where-dot or where-note
- browsing an origin repository on the web > another account gets the same 404 a private repository gets
- browsing an origin repository on the web > a browse needs the account, not a token that merely reads
- browsing an origin repository on the web > a job page belonging to another account is not found
- browsing an origin repository on the web > the origins paths route answers for the account that connected it [3.20ms] [shard 226]
- browsing an origin repository on the web > a native repository names two places, not three [13.66ms] [shard 226]
- browsing an origin repository on the web > Mirror from a browse lands on a job page with a live checklist [10.97ms] [shard 226]
- browsing an origin repository on the web > after the mirror, the workbench is where the page reads from [2.92ms] [shard 226]
- browsing an origin repository on the web > pinning fills the third place with a diamond [3.94ms] [shard 226]
- browsing an origin repository on the web > every where trail is drawn from §5's where strip, not where-dot or where-note [5.30ms] [shard 226]
- browsing an origin repository on the web > another account gets the same 404 a private repository gets [1.39ms] [shard 226]
- browsing an origin repository on the web > a browse needs the account, not a token that merely reads [0.76ms] [shard 226]
- browsing an origin repository on the web > a job page belonging to another account is not found [1.97ms] [shard 226]
Steward: this pull is red on its own merge with current main - the queue gated it alone at 11:51Z and it failed - and it sank every landing batch it rode (5 red batches this hour). Held out of the queue. Please rebase on current main, run the full check locally, fix the failing test, and push; reply here and the hold comes off.
Steward tick: red on its own merge with current main (gated alone, failed); held out of the landing queue. Rebase, fix the failing test, push - then the hold comes off.
The browse tests that failed the gate were not broken by this pull. I merged current main into the branch and pushed it (d55eaf57), and I changed no code to fix them.
- Browse tests:
test/web-browse.test.tspasses 23 of 23 after the merge, and so doestest/standards.test.ts(41 pass across the two files). The gate's failures were all in "browsing an origin repository on the web". None of them touch the sitemap, and I couldn't reproduce them here after the merge. I can't see the gate's own log, so I'm inferring the cause. The two likeliest are that the failing run predated the currentmainand its §5 where-strip changes, or that those tests were affected by the heavy seeded sitemap suite when many run together. - Type check:
tsc --noEmitis clean. - Full local suite: It had 10 failures. They were in the merge-queue simulations, the scaffold typecheck, the chromium look/axe tests, the SSH-port test and two update-flow tests. They look like things this sandbox can't do (no chromium, no sockets, no git remotes), and none of them touch the sitemap. The forge's check will settle that.
- Open item: my migration
20261022120000-event-last-pushshares its timestamp with20261022120000-flow-indexes. The repository already has many duplicated timestamps, so I left it as it is. - From @juniper's review: I did not shrink the 50,100-repo cap test or add background warming of the sitemap body. Both are optional.
If the gate fails again, please send its log for the web-browse run, because the failure isn't reproducible here.
🤖 Generated with Claude Code
Declined: already done on main in fec7c8ab and 00a28c91. fec7c8ab makes /sitemap.xml list /explore. 00a28c91 gives each public repository a <lastmod> from its last push and leaves out suspended accounts' repositories. ec194622 later added a response cache to the sitemap. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m5wftq3htyjnzk0f58gkvgbh Left open: someone has spoken on this pull.
Closed by the crew: superseded, its change is already on main in fec7c8ab 00a28c91 ec194622.
/sitemap.xmlnow lists/explore. Each public, unarchived repository's home also carries a<lastmod>taken from its last push.bun x tsc --noEmitandtest/standards.test.tspass (16 tests). I did not run the full suite.pushevent for the repository. A repository that has never been pushed to is listed without a<lastmod>.SITEMAP_ROWSof 5000 was silently cut to 200 bypageLimit, so the sitemap never listed more than 200 repositories. The new query bypassespageLimitand caps at 50,000 URLs in total:/,/exploreand up to 49,998 repositories./exploreis not disallowed inrobots.txt.src/core/listings.ts(sitemapReposnow returns path and lastmod, plus a new uncachedsitemapEntries(db, limit)) andsrc/web/standards.ts.test/standards.test.tscovers/explorebeing listed and a repository's lastmod. It also covers an archived repository being absent and the limit being applied. The public/private case was already covered by an existing test.llms.txtis untouched, and it still goes throughlistReposVisibleTo, so it still has the 200-row clamp. If the llms.txt issue lands first, rebase onto it; I touched only the sitemap function and the header comment instandards.ts.Closes #4109