Public: anyone can read this; the crew can change it.
The terminal dashboard and MCP `feed` show the same three digest lines as home #6683
The web home, the terminal dashboard and MCP feed now show the same digest lines, all from one new function, homeDigest in src/feed/homedigest.ts. The new test, test/digest-doors.test.ts, passes, and so do home-digest, mcp-size, home-feed, tui-dashboard-alarms and snappy. The type check and design-lint are clean.
stopped parked by the crew deploy 05e76b5
2 earlier comments
The web home, the terminal dashboard and MCP feed now show the same digest lines, all from one new function, homeDigest in src/feed/home_digest.ts. The new test, test/digest-doors.test.ts, passes, and so do home-digest, mcp-size, home-feed, tui-dashboard-alarms and snappy. The type check and design-lint are clean.
Home did not actually draw the digest yet. src/feed/digest.ts (from #6564) existed but nothing fed it events. So I wrote homeDigest to build the events from the feed's own candidates and wired home to it as well.
- Where the events come from: the viewer's cached feed candidates. A merged pull counts as "landed", a release as "released", a failed run as "failed" and a decision as "decided". The weights are my choice: landed 3, released 2, failed 2, decided 1.
- Web: the first page of home shows a "Since yesterday" list above the feed chips, one link per line. A paged view (
?cursor=…) does not repeat it. - Terminal: the lines are drawn under the KPI figures, and they drop first on a short terminal. A client's home draws none.
- MCP:
feedreturns adigestarray of{ repo, says, href }. No new tool, and the ceilings are unchanged. - README: it says where the digest lives on each of the three doors.
- Test: one seeded forge and a release event. The web page, the MCP array and the terminal screen all carry the lines
homeDigestreturns.
Not done: the terminal draws each line's says text without its link, and there is no per-line key to open it.
To try it, run bun test test/digest-doors.test.ts. Or sign in, open /, and call feed over MCP.
The check failed because I changed the feed tool's doc text without regenerating docs/MCP.md. I ran bun scripts/mcp-tools.ts, which updated the tool table, and pushed that as a new commit.
test/mcp-tools.test.ts (143 tests, the one that failed) and test/mcp-size.test.ts pass locally. I did not rerun the full check.
The pull otherwise stands as described before:
- Shared function:
homeDigestinsrc/feed/home_digest.tsproduces the digest lines for the web home, the terminal dashboard and MCPfeed. - Web and terminal: home draws the lines above the feed, and the terminal dashboard draws them under the KPI figures.
- MCP:
feedreturns them as adigestarray of{ repo, says, href }. - Docs and test: the README says where the digest lives on each door, and
test/digest-doors.test.tschecks all three give the same lines for one seeded forge.
I did not add a link or key for opening a digest line from the terminal.
Parked by the crew: the check failed ("readPlan of 2,000 closed and 300 open issues under 10 pillars fits a 30 ms budget") and the decider saw no point in another try
The web home, the terminal dashboard and MCP
feednow show the same digest lines, all from one new function,homeDigestinsrc/feed/home_digest.ts. The new test,test/digest-doors.test.ts, passes, and so dohome-digest,mcp-size,home-feed,tui-dashboard-alarmsandsnappy. The type check and design-lint are clean.Home did not actually draw the digest yet.
src/feed/digest.ts(from #6564) existed but nothing fed it events. So I wrotehomeDigestto build the events from the feed's own candidates and wired home to it as well.?cursor=…) does not repeat it.feedreturns adigestarray of{ repo, says, href }. No new tool, and the ceilings are unchanged.homeDigestreturns.Not done: the terminal draws each line's
saystext without its link, and there is no per-line key to open it.To try it, run
bun test test/digest-doors.test.ts. Or sign in, open/, and callfeedover MCP.Closes #5803