A fork's page says in one plain line how it follows its upstream and when it last took from it #11387

A fork's repository page now has one line saying how it follows its upstream and when it last took from it. I did not call keep_plan; the work was small enough to land in one pass.

What it says

• Takes updates from owner/name · last took 2 days ago, Sends offers to owner/name, or Not following owner/name.
• The · last took … part appears only once the fork has taken code from its upstream.
• The line links to the existing following card on the forks page (/owner/name/forks#following), which is where the mode is changed. No new setting.
• A repository that is not a fork shows nothing.
• If the reader cannot read the upstream, the line says "its upstream" and does not name it.
• The line is server-rendered and escaped, in src/web/pages/repo.ts.

One word table for page and MCP

• followStandingLine and agoWords are in src/actions/follow_words.ts.
• followStanding in src/actions/follow.ts is the one function the page and the MCP both call.
• The following tool answer now carries line, and so does the follow_mode answer. This is an extra field on existing tools, not a new tool.
• "Last took" is the newest push event recorded as followed for that fork, both for fast-forwards and merges. It is read by lastTookAt in src/core/fork_follow.ts. No migration.

Tests and checks

• test/fork-standing-line.test.ts covers each mode's words, the last take, a root repository saying nothing, and a private upstream not named to an anonymous reader.
• I ran the gate, tsc, design-lint, mcp-size, and the following, fork and MCP test files. All pass.
• scripts/fast.ts named about 2,200 files, so I picked the covering files myself.
• No look was taken; the sandbox has no browser.

Not done

• A fork's mode at its upstream's name for a forge spawned from a parent, where the forge chain and the upstream name come from the chain, is not special-cased. The line says "its upstream" there only if the parent repo is unreadable.
• I did not raise any MCP ceiling.

Try it

• Open a fork's page, e.g. /bob/lib.
• Call the following or follow_mode tool for the same line.
• The push needed a Try: commit, which is the second commit.

Closes #11297

A fork's repository page now has one line saying how it follows its upstream and when it last took from it. I did not call keep_plan; the work was small enough to land in one pass.

What it says

• Takes updates from owner/name · last took 2 days ago, Sends offers to owner/name, or Not following owner/name.
• The · last took … part appears only once the fork has taken code from its upstream.
• The line links to the existing following card on the forks page (/owner/name/forks#following), which is where the mode is changed. No new setting.
• A repository that is not a fork shows nothing.
• If the reader cannot read the upstream, the line says "its upstream" and does not name it.
• The line is server-rendered and escaped, in src/web/pages/repo.ts.

One word table for page and MCP

• followStandingLine and agoWords are in src/actions/follow_words.ts.
• followStanding in src/actions/follow.ts is the one function the page and the MCP both call.
• The following tool answer now carries line, and so does the follow_mode answer. This is an extra field on existing tools, not a new tool.
• "Last took" is the newest push event recorded as followed for that fork, both for fast-forwards and merges. It is read by lastTookAt in src/core/fork_follow.ts. No migration.

Tests and checks

• test/fork-standing-line.test.ts covers each mode's words, the last take, a root repository saying nothing, and a private upstream not named to an anonymous reader.
• I ran the gate, tsc, design-lint, mcp-size, and the following, fork and MCP test files. All pass.
• scripts/fast.ts named about 2,200 files, so I picked the covering files myself.
• No look was taken; the sandbox has no browser.

Not done

• A fork's mode at its upstream's name for a forge spawned from a parent, where the forge chain and the upstream name come from the chain, is not special-cased. The line says "its upstream" there only if the parent repo is unreadable.
• I did not raise any MCP ceiling.

Try it

• Open a fork's page, e.g. /bob/lib.
• Call the following or follow_mode tool for the same line.
• The push needed a Try: commit, which is the second commit.

A fork now says in one plain line how it follows its upstream and when it last took from it. The page, the MCP and the terminal all say it, from followStanding. tsc, scripts/gate.ts, scripts/design-lint.ts and 209 related tests pass. fast.ts found the diff too broad to name its tests, so I ran the follow, fork, MCP, upstream and repo-page suites by hand rather than the full check.

What changed

• Terminal: the forks screen in src/tui/screens/forks.ts shows the line under its head. It refreshes after m and after t.
• One line on the page: the standing line now uses the same markup as the neighbouring lines (div.small.muted with the sync icon) and links to /forks#following. It shows only when behindLine and originAheadLine are both silent, so a page carries one line about how it stands. I left followingLine alone: it is an admin card about the upstream URL, not the fork's standing.
• Docs: a new section in docs/features/follow-mode.md covers the line in all three doors and what "last took" means.
• lastTookAt: it now reads the newest followed push first and stops at the first hit (ORDER BY seq DESC LIMIT 1). The existing event_repo_kind_seq index on (repo_id, kind, seq) serves it, so it no longer scans every push.

What counts as a take Every followed push on the fork's own repo counts: the automatic fast-forward, a clean merge from takeUpdates/takeOrTell, and a spawned forge's take of its parent forge (spawn/take.ts). I kept the forge-to-forge take on purpose, since followModeOf already reads that chain for the mode. The doc says so. A different repo's pushes never count, because the query is per repo.

Tests added (test/fork-standing-line.test.ts)

• Real takes: a parent push that fast-forwards the fork on its own, and a merge taken through the real take_updates MCP tool. Each starts from a cleared event log and checks that lastTookAt becomes set.
• MCP line: from the real following and follow_mode tools.
• Private upstream: the fork's owner, who cannot read it, is not shown the name; the upstream's owner, who can, is. I did not cover a logged-in non-owner reader who can read the upstream, so that case remains untested.
• Terminal: the forks screen shows the line.

Not done

• I did not benchmark a busy repo. The index and the LIMIT 1 should keep the query cheap, but I did not measure it against the 50 ms budget.
• test/fork-standing-line.test.ts carries four dynamic await import(...) calls that should be plain top-of-file imports.

Try it Open /bob/lib or a fork's /forks page, or run the following MCP tool on a fork and read line.

🤖 Generated with Claude Code

The failing check is fixed and pushed. The header comment on lastTookAt in src/core/fork_follow.ts was over the 160-column limit. I wrapped it over several lines, and the wording is the same.

test/header-width.test.ts now passes (2 pass, 0 fail) and bun x tsc --noEmit is clean. I did not re-run the full suite here, since the forge runs it on the push. Nothing else changed in the pull.