Launcher, packaging and logistics
Questions about the Simca Launcher (Steam-like): Offline Mode, User-Initiated Updates, Package Spec, Sign-in module of the catalog.
Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made
Planned C0527
Simca Launcher (single entry point) is item LNCH-0001 in the “Launcher core and first install” section of Simca Launcher. In the catalog it covers: Steam-like launcher that installs, starts, updates and manages Simca packages; the only place to pick, add or remove elements. Nothing is built.
Planned C0528
Launcher reuse: keep previous generation depends on Simca Launcher (single entry point). By itself it covers: Keep the last working generation until the next success. These are catalog links between planned items in “Launcher fork/redesign of the an earlier launcher (decision record)”.
Planned C0529
For Launcher start performs no network request (LNCH-0036) the catalog says: Starting the launcher or the app makes no network call in any mode. It is core priority within “Offline and online modes” and sits in both Lite and Pro. It is not a feature yet.
Planned C0530
It works offline and offers an optional online action the user must choose. For Launcher update download with resume (LNCH-0056) the catalog text is: Resumable download for weak connections. Under “Updates: user-initiated, signed packages”, and not built.
Planned C0531
No: there is no released app. LNCH-0079 (Launcher free package indicator), filed under “Package spec, element selection and package manifest”, is described as: Shows when the selection consists only of elements in the free pricing class.
Planned C0532
No: there is no released app. LNCH-0093 (Launcher online network sign-in), filed under “Online network sign-in (only for online features)”, is described as: Optional sign-in to the online network, user-initiated; never required for offline operation.
Planned C0533
Launcher wrong platform package is item LNCH-0108 in the “Failsafe, security and edge cases” section of Simca Launcher. In the catalog it covers: Reject packages built for another platform. Nothing is built.
Planned C0534
Launcher close hides, quit is explicit depends on Simca Launcher (single entry point). By itself it covers: Closing the window keeps the launcher resident only if the user chose that; quit always available. These are catalog links between planned items in “Launcher core and first install”.
Planned C0535
Launcher manifest rollback and freeze protection is item LNCH-0052 in the “Updates: user-initiated, signed packages” section of Simca Launcher. In the catalog it covers: Reject older manifests and, when online, expired manifests; offline use cannot detect expiry, which is shown as a note. Nothing is built.
Planned C0536
Launcher read-only catalog preview offline is item LNCH-0089 in the “Package spec, element selection and package manifest” section of Simca Launcher. In the catalog it covers: Browse an embedded catalog snapshot with no network. Nothing is built.