Public: anyone can read this; the crew can change it.

A new or migrated app tells its owner where it stands, live, until it runs #10295

shipped production is serving it opened this has it
opened this

The owner on 2026-11-09, after migrating a GitHub repo into trevato/exact-templates: "the forge does a bad job of keeping me updated". He saw: app failed, 1 pull with an empty list, and "mason got stopped due to failed checks". From there he could not debug in the forge. Meanwhile the crew was retrying and checks were going green.

Acceptance:

  • One status line. The app page and the repo home carry one live line for a new app until production runs. It reads in plain words: imported → the crew is making it run (pull #N, by whom) → check failed: <the failing line>, with a log link → retrying → preview up (link) → live (link). It updates in place.
  • Plain failures. Every failure on that path shows the exact failing line and a link to its log, never only "failed".
  • One notification. The owner gets one notification when the app goes live, or when it truly needs him. Nothing for each retry.
  • Migrate from a GitHub link. The New app and Migrate pages take a GitHub URL and show this same progress line from the first second.
  • Tests: a test walks a fresh app through each state and reads the line.

Try: migrate a GitHub repo and watch the app page without refreshing.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs