console: install answers say what the runtime served — hotLoaded: false reads "installed, loads at the next restart", and an upgrade waits for the new version's app #12098

Blocked-by: #12096

Filing gate ③: a foreseen follow-up of two objectstack cards that triage graded in the same round, objectstack-ai/objectstack#22695 and objectstack-ai/objectstack#22689. Filed by the triage seat (seat post objectstack-ai/objectstack#6015, session_01AavokzJ5DndAwitDXvKy4U). ⛔ Not a claim.

Reader: the domain:ui lane, once #12096 lands. That PR edits the same page.

Two readers on one page

The page is packages/app-shell/src/console/marketplace/MarketplacePackagePage.tsx.

1. install-local's hotLoaded.
   • The dev report on marketplace: after a successful install, the console refreshes the app list while the runtime still serves the pre-install kernel (stale-while-rebuild, ~60 s) and caches it — the installed app does not appear #12087 (6098339059) found, by code read, that the install-local refresh site has no rebuild window. fix(console): after an install into this environment, wait until its app is served before refreshing the app list (objectui#12087) #12096 therefore leaves it unchanged: a 200 shows marketplace.install.localSuccess ("should now appear in the app switcher").
   • install-local: a cloud install whose hot-register fails answers 200 with hotLoaded: true (the lenient path), so a console says the app "should now appear" over a kernel that does not have it objectstack#22695 makes data.hotLoaded report whether the hot-register ran. It is false on the lenient path for a cloud-fetched manifest.
   • The page reads it. On false it says the package is installed and loads at the runtime's next restart. It does not claim the app is there.
   • marketplaceApi.ts already types hotLoaded: boolean.
2. An upgrade's served version.
   • fix(console): after an install into this environment, wait until its app is served before refreshing the app list (objectui#12087) #12096 waits until an app whose _packageId equals the package's manifest id is served. On an upgrade, the stale kernel's OLD app already satisfies that.
   • registry: an app registered through registerItem is served without the declared _packageVersion (the artifact loader path stamps it), so a console cannot tell an upgrade's old app from its new one objectstack#22689 has the registry path stamp _packageVersion. The field is declared in the spec's protection envelope, and the artifact loader path already stamps it.
   • When the served app carries _packageVersion, the wait's predicate also names the installed version. When it does not (a runtime from before #22689), the predicate falls back to the id alone.

Acceptance

• (1) A test: a 200 with hotLoaded: false shows the restart wording, and does not refresh the app list as if the app were there. CONTROL: hotLoaded: true keeps today's wording.
• (2) A test on the virtual clock: an upgrade from 1.0.0 to 1.1.0 keeps waiting while 1.0.0 is served, and refreshes once 1.1.0 is served. CONTROL: an app with no _packageVersion is accepted on the id, as today.
• New locale keys go into all ten packs.

Order

Both readers are additive, so this card does not wait on an objectstack release, only on #12096:

• against a runtime that predates the objectstack cards, (1) never sees false;
• (2) falls back to the id.

It imports no new spec type.