Absorb: show a feature's feed items #9901

An absorbed app's page now shows what the feed holds about that app, and the same items are available over the API and the MCP. The tsc and gate checks printed nothing, and bun test on test/features.test.ts, test/features-empty.test.ts and test/mcp-size.test.ts passes (38 tests). I did not run the design-lint, and scripts/fast.ts named 1319 test files (7 changed), so I ran only the tests I picked and left the rest to the forge's check.

What changed

• Per-app feed: readFeedPage takes an optional repoId and keeps only that repository's items before ranking. The app's mute does not hide them there. featureFeed in src/actions/features.ts wraps it. Anyone who can read the repository can see its feed items, and because the items come from the viewer's own feed, nobody sees one they couldn't see there.
• Page: Settings › Features › the app has an "In the feed" section with the 10 latest items. Each links to its source.
• API: GET /api/v1/features/:slug/feed returns {items, next_cursor: null}. There is no paging; it returns the top 20.
• MCP: the existing features tool takes feed: true with a slug. It is not a new tool, and I did not touch the ceilings in test/mcp-size.test.ts.
• Docs and test: docs/features/absorb.md has an "Its feed items" section, and the "Not done yet" list no longer names #9884. A new test in test/features.test.ts covers the three doors: an item in the app's repository shows up, one in another repository does not, and a stranger gets a 404.

What I left out

• Apps posting items: the issue's wording could mean apps posting items of their own. I took it to mean the feed items about the app's repository, so an app cannot post items yet. The doc says so.
• Paging and a summary on the app strip: I added neither.

Try it: sign in as a site admin, open /settings/features/<slug>, and look under "In the feed".

Closes #9884

An absorbed app's page now shows what the feed holds about that app, and the same items are available over the API and the MCP. The tsc and gate checks printed nothing, and bun test on test/features.test.ts, test/features-empty.test.ts and test/mcp-size.test.ts passes (38 tests). I did not run the design-lint, and scripts/fast.ts named 1319 test files (7 changed), so I ran only the tests I picked and left the rest to the forge's check.

What changed

• Per-app feed: readFeedPage takes an optional repoId and keeps only that repository's items before ranking. The app's mute does not hide them there. featureFeed in src/actions/features.ts wraps it. Anyone who can read the repository can see its feed items, and because the items come from the viewer's own feed, nobody sees one they couldn't see there.
• Page: Settings › Features › the app has an "In the feed" section with the 10 latest items. Each links to its source.
• API: GET /api/v1/features/:slug/feed returns {items, next_cursor: null}. There is no paging; it returns the top 20.
• MCP: the existing features tool takes feed: true with a slug. It is not a new tool, and I did not touch the ceilings in test/mcp-size.test.ts.
• Docs and test: docs/features/absorb.md has an "Its feed items" section, and the "Not done yet" list no longer names #9884. A new test in test/features.test.ts covers the three doors: an item in the app's repository shows up, one in another repository does not, and a stranger gets a 404.

What I left out

• Apps posting items: the issue's wording could mean apps posting items of their own. I took it to mean the feed items about the app's repository, so an app cannot post items yet. The doc says so.
• Paging and a summary on the app strip: I added neither.

Try it: sign in as a site admin, open /settings/features/<slug>, and look under "In the feed".

The gate failed because no commit message had a "Try:" line. I added an empty commit with one and pushed it. I haven't seen the forge's new check result yet, and the code and tests are unchanged from before.

What changed

• An absorbed app's page (/settings/features/<slug>) has an "In the feed" section. It lists the 10 latest feed items about that app's repository.
• The same items come from GET /api/v1/features/:slug/feed and from the existing features MCP tool with slug and feed: true. No new MCP tool, and test/mcp-size.test.ts ceilings are untouched.
• Only people who can read the repository see its items, and a muted app still shows them there.
• docs/features/absorb.md has an "Its feed items" section, and #9884 is gone from "Not done yet".
• A new test in test/features.test.ts covers the page, API and MCP.

Left out

• Apps cannot post feed items of their own; this shows what the feed already holds about the app.
• The API list has no paging; it returns the top 20.

Try it: sign in as a site admin, open /settings/features/<slug> and look under "In the feed", or call GET /api/v1/features/<slug>/feed.

This pull shows a feature's feed items on its settings page and over the API and MCP. It also adds the missing OpenAPI row for GET /api/v1/features/{slug}/feed.

• Fix for the failed check: the new feed route had no OpenAPI description, which failed the "every registered /api/v1 route has an OpenAPI row" test. I added src/contract/openapi/routes/getApiV1FeaturesSlugFeed.ts and regenerated the route index. That test, test/openapi-routes.test.ts and test/features.test.ts now pass, and tsc --noEmit is clean.
• Cart test: the second failure, "a pin's cart > a captured cart plays sandboxed…" in test/build-cart.test.ts, passes when I run its file alone, and the pull doesn't touch it. I treated it as flaky under sharding and made no change, so I can't rule out that it fails again in the full check.
• Not run: I did not run the full suite or bun scripts/gate.ts here. The forge's check does the full suite on push.

To try it: open /settings/features/<slug> as a site admin and read "In the feed", or GET /api/v1/features/<slug>/feed.

A feature's feed items now show in the terminal as well as on the page, the API and MCP. This push addresses all of sentinel's points except one, direction (point 4), where I haven't changed anything.

What changed

• Terminal screen. src/tui/screens/featurefeed.ts adds a "Feature feeds" palette entry, registered in ENTRIES in src/tui/screens/entries.ts.

- The entry is offered to any signed-in person. - The list is absorbedForNav, the menu's own read, which only includes apps the person may read. - enter opens an app's items, read through the same getFeature and feedOf as the other doors.

• One read per page. featurePage already holds the FeatureView, so the new feedOf(app, actor, view) takes it directly.

- There is no second getFeature and no second readable() call. - The API route still uses featureFeed(slug), which makes the one getFeature call. - Guests get [].

• Page rows.

- Layout. Each row is the actor (or the app) plus the feed's own time(). The raw reason and the "the crew" fallback are gone. - Empty line. The empty line is "Nothing yet." - Link guard. A row only becomes a link when link is an internal path (starts with /, not //).

• MCP. feed: true together with absorb or settings now returns invalid instead of dropping the write. I also fixed the import order in the three files sentinel named.
• Docs. docs/features/absorb.md now says the terminal has "Feature feeds".

Tests

• test/features.test.ts is split into:

- repo filter through the API and MCP; - a muted app's items still show in its own feed while the home feed hides them; - the page, plus a stranger and an unauthenticated caller both getting 404; - a guest on a public feature getting []; - an app with no declared feature getting 422 not_a_feature; - the MCP refusal.

• test/features-tui.test.ts covers opening the screen from the palette and seeing an item.
• These pass: features, features-tui, apps-features, contract, mcp and three feed suites. bun x tsc --noEmit, scripts/gate.ts and scripts/design-lint.ts are clean.
• scripts/fast.ts named 1538 test files, so I ran the files that cover the change instead of the diff-named set.

Not done

• Direction. I can't change the owner's ordering. The change is small, touches no pipeline code, and a person can hold the merge behind the pipeline queue.
• Pagination. There is no paging of the feed in any door, because the page shows 10 items and the API returns up to 20.
• Unabsorbed features. The terminal screen lists absorbed apps only. The page still covers declared-but-unabsorbed features for admins.

To try it, open /settings/features/<slug> as a site admin and read "In the feed", or use GET /api/v1/features/<slug>/feed. In the terminal, press ctrl+k and choose "Feature feeds".

The gate failed because the pull adds a terminal screen, src/tui/screens/featurefeed.ts, and no commit message said why it goes ahead of the pipeline. I've pushed an empty commit, 08e26052, with a Why now: line: issue #9884 asks for it, sentinel required the terminal door, and the change is small and touches no pipeline code.

I added a commit instead of rewriting the earlier ones, because force pushes are refused. I haven't re-run the gate or any tests this round, since only a commit message changed. The earlier push passed bun scripts/gate.ts locally, which makes sense because I didn't have the pull's commit messages to check.

The forge's check will run again on this push.

I merged main into the branch, resolved the three conflicts keeping both sides, and pushed (7eaeaf74). bun x tsc --noEmit and scripts/gate.ts are clean. test/features.test.ts, test/feature-tools.test.ts and test/features-tui.test.ts pass (47 tests); I did not run the full suite.

• src/http/mcp/tools/features.ts: it keeps main's callFeatureTool import and the tool and args inputs, plus this pull's feedOf and feed. The doc string now lists feed? next to tool?, args?.
• test/features.test.ts: it keeps main's MCP tools test and all of this pull's feed tests.
• docs/features/absorb.md: it keeps main's "MCP tools" section and drops "show its feed items (#9884)" from "Not done yet". The first "Not done yet" sentence on main still says the forge doesn't yet "serve its MCP tools inside /mcp (#9885)". I took main's wording there, so that sentence now omits #9885.
• One addition: main's tool branch runs before the feed check, so feed: true with tool would have silently ignored feed. It now returns invalid, the same as feed with absorb or settings. This case has no test of its own.
• Commit message: the merge commit carries a Why now: line, since the gate asks for one.

The three palette-roster failures were mine, and I've fixed them. I couldn't reproduce the other two, the media and org-owners failures.

test/palette-roster.test.ts lists the palette's entries in order, and the new "Feature feeds" entry wasn't in it. I added it to the site-admin person, site-admin agent and member person lists. All 15 tests in that file pass now.

test/media.test.ts ("a kind with no renderer…") and test/org-owners.test.ts ("the upgrade takes every agent out of Owners…") both pass here, with and without my changes. They look like shard-order or flaky failures unrelated to this pull, but I haven't confirmed that. If they fail again on this push, send me the log.

Pushed as 21b722a4.

I merged main into the branch and pushed it as 6a0969f3. The only conflict was the "Not done yet" sentence in docs/features/absorb.md.

main had dropped #9887 from the list, so the health-on-/system item is gone. My side had dropped #9884. The merged sentence lists only the schedule (#9883) and secret settings (#9886). The merge commit carries a Why now: line, as the gate requires.

bun x tsc --noEmit and scripts/gate.ts pass. test/features.test.ts, test/features-tui.test.ts and test/apps-features.test.ts passed. I ran those with test/palette-roster.test.ts in one process, and one palette-roster test failed with "Cannot use a closed database". The stack trace points at an app run in src/apps/runtime.ts finishing after its test's database had closed. That failure is in a test about a pull's Files step, not this change. Run alone, test/palette-roster.test.ts passes all 15. I did not run the full suite; the forge's check does that on this push.