The terminal shows the front page as a stranger sees it, ranked with its numbers, and a site admin pins or hides an app after a plan, as MCP `front_page` does #7745

The terminal palette now has a "Front page" screen. It lists what a signed-out visitor sees, in order, and lets a site admin who is a person pin or hide apps. The new test/tui-front.test.ts passes, tsc is clean, and test/mcp-size.test.ts, test/palette.test.ts and test/tui-resilience.test.ts pass. scripts/fast.ts named 193 test files, about 15 minutes. I did not wait for that run, so the forge's check on this push is the first full run.

What changed

• The list: src/tui/screens/front.ts reads frontJson with no viewer, so the order matches MCP front_page and a private app never appears, for anyone. Each row has the repo, a featured or pinned mark, and the score parts: forks, ships, use (awake hours) and fresh (last ship date).
• Pin and hide: for a site admin who is a person, p pins an app first or unpins it, and h hides or shows it. Each keypress opens a confirm that shows the plan (the dry run through setFront) with the resulting pinned and hidden lists. The default choice is Cancel, and Apply calls setFront.
• Who gets the keys: a non-admin or an agent sees the list with neither key.
• Hidden rows: an admin also sees hidden public apps as extra rows at the end, so h can show one again.
• Palette entry: it sits in ENTRIES (src/tui/screens/entries.ts), as cloud, domains and owner do, rather than being added to src/tui/forge.ts. It is offered to every session, including signed-out ones.
• Tests: test/tui-front.test.ts covers the list order against the front_page tool, no private app, no keys for a non-admin or an agent, pin moving an app to first, and hide removing it and show restoring it. test/palette-roster.test.ts now lists "Front page" in all four rosters, which is a correction, since the roster test pins every entry.

Left out

• Weights are not editable here.
• There is no reordering of pins beyond "pin puts it first".
• Without the stranger's pictures and a running state an app is not on the shelf, so I added no screen text for that case.

To try it

• SSH to the app, open the palette with : or ctrl+k, and choose "Front page". As an admin, press p or h on a row.

Closes #7290

The terminal palette now has a "Front page" screen. It lists what a signed-out visitor sees, in order, and lets a site admin who is a person pin or hide apps. The new test/tui-front.test.ts passes, tsc is clean, and test/mcp-size.test.ts, test/palette.test.ts and test/tui-resilience.test.ts pass. scripts/fast.ts named 193 test files, about 15 minutes. I did not wait for that run, so the forge's check on this push is the first full run.

What changed

• The list: src/tui/screens/front.ts reads frontJson with no viewer, so the order matches MCP front_page and a private app never appears, for anyone. Each row has the repo, a featured or pinned mark, and the score parts: forks, ships, use (awake hours) and fresh (last ship date).
• Pin and hide: for a site admin who is a person, p pins an app first or unpins it, and h hides or shows it. Each keypress opens a confirm that shows the plan (the dry run through setFront) with the resulting pinned and hidden lists. The default choice is Cancel, and Apply calls setFront.
• Who gets the keys: a non-admin or an agent sees the list with neither key.
• Hidden rows: an admin also sees hidden public apps as extra rows at the end, so h can show one again.
• Palette entry: it sits in ENTRIES (src/tui/screens/entries.ts), as cloud, domains and owner do, rather than being added to src/tui/forge.ts. It is offered to every session, including signed-out ones.
• Tests: test/tui-front.test.ts covers the list order against the front_page tool, no private app, no keys for a non-admin or an agent, pin moving an app to first, and hide removing it and show restoring it. test/palette-roster.test.ts now lists "Front page" in all four rosters, which is a correction, since the roster test pins every entry.

Left out

• Weights are not editable here.
• There is no reordering of pins beyond "pin puts it first".
• Without the stranger's pictures and a running state an app is not on the shelf, so I added no screen text for that case.

To try it

• SSH to the app, open the palette with : or ctrl+k, and choose "Front page". As an admin, press p or h on a row.

I've pushed all three fixes to the same branch. tsc is clean, and test/tui-front.test.ts and test/front.test.ts pass. I did not rerun the wider palette and roster tests after this round. This round touched no palette entries.

1. Docs: docs/TOUR.md had no front-page section, so I added "The front page". It covers the web, API, MCP and terminal doors. The terminal entry describes the Front page screen and what p and h do, including that anyone else, signed out included, gets the list and neither key. I did not touch the README, since AGENTS.md caps it and sends how-tos to docs.
2. Tests:

- The "non-admin has neither key" test now checks that frontJson is unchanged after p and h. It covers a member and an admin agent, and the vacuous toBeDefined assertion is gone. - A new signed-out test checks the list shows the stranger's apps and no private one, and that p and h change neither the screen nor frontJson. - A new web-reach test starts a real server and pins the last app from the terminal. It checks that GET /api/v1/front then features it and that / contains it. It then unpins. I used /api/v1/front and / rather than SSE, because the stranger page reads the same frontJson.

1. Types: src/actions/front.ts now exports FrontJson and FrontRowJson, and frontJson returns FrontJson. The screen no longer casts or hand-writes the shape. It takes its signals type from FrontRowJson.

I merged origin/main into the branch and pushed. The check had failed because src/tui/screens/entries.ts conflicted with main's rewrite of the palette entries.

I kept main's new ENTRIES list and addEntries unchanged. I added the front import and put front in the list between domains and owner.

bun x tsc --noEmit is clean, and test/palette-roster.test.ts, test/tui-front.test.ts and test/palette.test.ts pass on the merged tree (22 tests). I did not rerun the full suite. The forge's check will run it on this push.