The dev drive on another PC still had no live aircraft after that PC's launcher
went live: its API log kept saying "the DHP answered, but this PC has no DHP
sign-in yet", and launcher.json was never rewritten, i.e. no sign-in ever
completed there. Root cause is the window, not the operator: the action panel
offers Sign in only when nothing is installed, an update is due, or no operator
is remembered (actionFor). The operator is remembered IN launcher.json, which
travels with the drive, while the sign-in lives in that PC's Credential
Manager - so a drive on a new PC shows Launch as if nothing were missing, and
Sign in sits in Settings > Account where nothing points to it.
Under Launch, while online and not signed in, the panel now says ODIAN will run
on this PC's own data without live aircraft, with a Sign in link. Launch stays
the button: a sign-in that cannot complete must not stop ODIAN.
New mock scenario `new-pc` (online, installed, operator remembered, no
sign-in). Spot-check: npm run dev -> ?scenario=new-pc shows the line; its Sign
in link runs the sign-in and the line goes, the status bar then reading
"Signed in as". svelte-check: 0 errors.
- Tauri 2 + Svelte 5 hub in ODIAN dark: patch notes and roadmap, install and
update progress, local stack status, settings with DHP and MCP addresses.
- crates/odian-packs: Rust installer for pack format v1 (signed manifests,
resumable verified downloads from a DHP or an ODIAN drive), byte-compatible
with ODIAN_MCP_Server's Python odian_packs.
- Local stack on 127.0.0.1: Postgres -> Engine API -> tile server -> Odian.exe,
one Job Object, clean shutdown; database snapshot restore on a fresh PC only.
- Keycloak sign-in through the DHP's MCP, remembered until Sign out with a
launcher session that renews the Engine token silently.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
JIMMY_JFEXP