Packs: launch a Business pack and a Gamer pack you can start a forge from (the page is empty today) #11006

Owner, 2026-11-10: "packs and displays are bad."

/packs today, signed in as the owner:

• One sentence ("A whole forge to start from…"), then a "Mirror the upstreams" button.
• No pack is shown. There is nothing to look at, pick or start from. Earlier he asked that packs come from the forge, not GitHub.

Done when /packs is worth opening, or it leaves the nav:

1. What it shows: each pack is a card with its name, the apps inside (with live links and a preview), how many repos it has and how fresh they are, and one button, Start a forge from this, which spawns a child with it.
2. Where packs come from: they are built from repos on this forge, marked as packs, in the same way as template repos (#10305 and P14). Nothing is fetched from GitHub. Mirroring upstreams is a detail inside a pack, not the page's action.
3. When there are no packs, the empty state says what a pack is and offers "make one from these repos". The admin can mark repos straight from there.
4. If it can't be good this week, hide it: remove Packs from the nav and the menu until it is. A hollow page costs more trust than a missing one.
5. Proof: before and after screenshots at phone and desktop width in the pull. A cold reader can say what a pack is in one sentence.

Under P14 Templates (#10266).

Owner, 2026-11-10: "i want a business and a gamer pack."

These are the first two packs, so the page launches with both. Start from his repos on this forge; read each one and keep only those that run and look good:

• Business pack: realty-desk, deal-clock, listing-launch, speed-to-lead, form-engines, business-spawner, bazaar.
• Gamer pack: games-shelf, sandbox-game, pixel-plays, scrims, chess, pong, voxel, gamers, cs-engine, survivor-guide.

Each pack has:

• a one-line pitch;
• its apps as cards, with live links and previews;
• a crew brief that suits it: business pack crew on leads, forms and money; gamer pack crew on play feel and animation;
• Start a forge from this.

If an app is broken, leave it out and list it in the pull rather than shipping it. Proof: start a forge from each pack, and every app in it answers live.

Owner, 2026-11-10: "that lets me start a forge with a few curated repos. i want to be able to edit which repos are in them."

This is part of done. A pack is a curated list of repos that you edit in the forge itself, not something in code:

• On the pack page, an admin sees Edit.

- Add a repo with a search box over the repos he can see. - Remove one with a single tap. - Drag to reorder; the order is the order the cards show in. - Rename the pack, and change its pitch and crew brief. - Every change saves at once and shows a short history: who, what, when.

• Make a new pack from /packs ("New pack") and from a repo's menu ("Add to pack…").
• Starting a forge copies the pack as it stands at that moment. Later edits don't touch forges that already exist.
• The API and MCP can do the same: GET/PUT /api/v1/packs/{name} with {title, pitch, brief, repos:[owner/name…]}, so an agent can curate packs too.
• Seed it with the Business and Gamer lists above as the first two packs, then he trims them himself.
• Proof:

- A test covers edit, start and the copy staying fixed. - A phone-width walk shows adding and removing a repo.