Decide: Amiga Installer script (or stay drag-to-drawer only)

[sidick]

From docs/ROADMAP.md Phase 5 (marked maybe): an Amiga Installer script for guided setup — copy to a drawer, optional WBStartup with tooltypes, ENVARC: prefs.

Weigh against the core goal: runs from a single drawer, no installer — drag-to-a-drawer must stay the primary, always-works path. With icons + the AmigaGuide now in the archive (#36), the drawer experience is fairly complete for v1.0, so an installer doesn't carry its weight yet - staying drag-to-drawer only for the v1.0 release.

Moved to v2, reconsidered alongside translations (#67): once locale.library catalogs are involved, there's an actual guided-setup step worth scripting - picking/copying the right language catalog into LOCALE:Catalogs/<language>/ isn't a drag-to-drawer operation the way copying the program itself is. An Installer script becomes worth its weight specifically once that lands, not before. Decide once #67 is scoped, and either implement alongside it or close this out.

[sidick]

Re-reviewed now that #67 is closed: still not worth building yet.

#67 shipped the infrastructure (locale.library catalog loading, preferred-language fallback, the structural linter) but zero actual translations have been reviewed or shipped. locale/drafts/ holds four AI-drafted .ct files explicitly marked "NOT reviewed, NOT installed by anything" — its README requires a fluent-speaker review before any of them can be promoted. Until one is, there's no real catalog to guide a user into installing.

This issue's own reasoning ties the installer's value specifically to "picking/copying the right language catalog into LOCALE:Catalogs/<language>/" — with no shipped catalog, that step doesn't exist. Installing a translation today (per userdocs/Localization.md) is a one-line manual copy, which doesn't justify guided setup. The core "runs from a single drawer, no installer" principle still holds for everything actually shipping.

Decision: keep waiting. Revisit once a translation is actually reviewed and merged (not just drafted) — at that point the guided-copy step becomes real and this is worth scripting alongside it.