Flows
/<owner>/<repo>/flows is one picture per repository (#9434): on the left what flows in — the origin it was forked from, the upstream and sources it follows, the npm packages its package.json pins with the newest release upstream — and on the right what flows out: its forks and the mirror it pushes to. Each line has its state and when it last moved. The page draws it as that picture (#9595): sources left, the repository's name between, followers right, stacked below 900 px as Flows in, Packages, Flows out; no script, and the arrows are decoration only.
- No crew, no model. Reading pins, comparing versions (
src/flows/semver.ts), the gap (patch, minor, major), and the page are deterministic. Test:test/flows.test.ts, no credential. - Read upstream. An admin of the repository taps Read upstream releases now (same-origin POST); the radar asks the npm registry for each exact pin and stores the answer in
dep_latest. The page itself never touches the network. - Doors. A Flows entry in the repository header's More menu (and the palette, from the same
repoStepslist), and the terminal's Flows of a repository verb (src/tui/screens/flows.ts). Both read throughreadFlows(canRead,visibleForks) and start the radar throughstartRadar(src/flows/start.ts): admin only, never an agent. - Bounded. A run asks four packages at a time within 30 s total; a repository has one run at a time; one identity gets four runs a minute. Followed and upstream URLs are shown without userinfo, query or fragment.
- Pins. Only exact floors (
1.2.3,^1.2.3,~1.2.3) are compared; tags and URLs are skipped. Names are validated before they reach a URL.
- Link health (#9561). Every line carries a health badge: healthy, news, diverged, unreadable, not read lately (no comparison in 90 minutes) or paused (
followHealth,src/flows/view.ts). A mirror's own origin shows as a line from the head reading inorigin-ahead.md. - Probe. The clock already compares heads (
checkDuefor the upstream and sources,runAheadReadsfor an origin); an admin's Compare heads now (POST /:owner/:name/flows/probe,src/flows/probe.ts) runs the same reads on ask: admin only, never an agent, one at a time, four a minute. - Bounded. A probe reads at most 8 enabled sources, four at a time, and answers within 30 s; it announces itself (
repo.links_probed, readers of the repository) so an open page offers the refresh. An origin line is stale on the same 90-minute rule; every origin reading records when it was taken. - Terminal. The Flows screen shows the same lines with health tones and the same gates:
ccompares heads (admin),ppulls in what's new (writer,takeFromOrigin),onames the page that offers a pull to the parent. A guest sees only what they may read. - Actions. A writer of a mirror with news sees Pull in what's new (the existing
sync/take, which refuses a diverged mirror); a writer of a fork sees Offer what's useful (the existing pull-to-parent page).
- Advisories. The same Read upstream releases now also asks the npm registry's bulk advisory endpoint about each exact pin and stores a one-line answer (severity, title,
(+N more)when there are several) indep_latest.advisory. A package with one shows an advisory badge and the text on the page and in the terminal (depState,src/flows/radar.ts, words both). They refresh only on that button: the page never calls the registry. The advisory ask is a second request per package inside the same 30 s run deadline. - Forks. Each fork out reads fork, takes updates or fork, told of updates (its
fork_followmode), and its last-moved time is its newest push (its creation until it has one). A fork following its parent is the only "follower" the forge records; there is no table of people following a repository. - Forges that follow. A child forge holding a proposal token for the repository is a forge follows line (its origin without userinfo or query; last use of the token, else when it was minted; token ended once expired). Only people who can write to the repository see these lines, page and terminal alike.
Left out: the CHANGELOG sections between pin and newest (dropped until a lookup can read one within a byte bound); the nightly radar is below; code scanning (and the release block on a new high finding); per-line buttons (actions are listed under the columns); counting a fork's commits ahead of its parent; GitHub release tags; the all-repositories admin view is admin-flows.md. Each is its own pull on top of dep_latest and readFlows.
The nightly radar (#9592)
Every night at 05:07 UTC (src/nightly/radar.ts, scheduled by src/nightly/service.ts with the other nights; off in a preview or without FORGE_TOKEN) the radar reads upstream for every unarchived repository that pins packages and files what is worth taking (src/flows/file.ts): one issue per dependency, Update <name> to <version>, whose newest stable release is above the pin. The body says what changed, why it helps and what could break, by the size of the gap. Never a duplicate: a dependency with an open update issue gets none, and a release already filed (even if closed) is not filed again. On an autonomous repository the issue is assigned to a builder on the crew (the crew's own pick, so the week's pace still holds it) and the body says the crew takes it; otherwise it is assigned to the repository's owner and waits for a person. Running it now: there is no button that files; Read upstream releases now only refreshes the readings, and the filing happens at the night's slot (the same radarNight a test calls). The issues are authored as the repository's owner, like every other job's (flake hunt, culprit, keeper). Resilience shows when it last ran and what it filed.