Harden release packaging and recoverable installation after review

This commit is contained in:
bholman committed 2026-11-18 16:26:25 -07:00
1 parent cb40fed3b9
commit 8088c1fbf6
14 files changed
+933 -101

No files matched your search

+48 -12
View File
@@ -27,11 +27,30 @@ activity. Installation returns to MENU, so the current guest session is ended.
```
If no address is given, the script prompts for one. It first validates every
local input, then checks remote access, stages files, verifies remote SHA-256,
returns to MENU, backs up replaced files, copies the overlay, checks installed
hashes, syncs the volume and optionally loads the launcher. A timestamped receipt
in ignored dist storage records the device and rollback path. It does not change
accounts, networking, Samba, the Linux installation or nonvolatile FPGA storage.
local input and writes a local per-attempt receipt naming the planned stage,
backup, destinations and temporary files. It then checks remote access, stages
and verifies every payload, and returns to MENU. All supporting assets are
installed and checked before activation: the uniquely addressed RBF, ROMs,
configuration/path files and notices. Existing saved configuration is preserved.
The volume is synced before the launcher is changed.
The launcher is the last asset installed. Its staged bytes are copied to a
temporary sibling beside the destination, SHA-256 checked, and atomically renamed
to _Computer/Coco 3 Plus.mgl. The installer checks the final bytes, syncs again
and optionally loads the launcher. This avoids exposing a new menu entry before
its supporting files are installed. Filesystem rename is not a claim of
power-loss certification or a transaction covering the entire SD card.
Receipts are retained in ignored release storage as
`install-receipt-<attempt>.json`; `install-receipt.json` holds the latest attempt's
complete JSON record. An existing latest receipt is also preserved before a new
attempt. Each phase and completed file is recorded. On failure or keyboard
interruption, the receipt retains the active phase/file, error and planned
recovery paths. Stage and backup files are not automatically deleted; an
already-existing remote attempt directory is rejected rather than merged.
The installer does not change accounts, networking, Samba, the Linux installation
or nonvolatile FPGA storage.
Only the Plus launcher, its uniquely addressed RBF, two boot ROMs and optional
SSC ROM/path records are installed. The stock core and other guest media remain.
@@ -82,6 +101,12 @@ artifact that omits all boot and SSC ROMs. Supply the required ROMs before manua
copy/launch. The SSH installer rejects this incomplete-ROM package and directs
you to make a complete local package from your own verified inputs.
The included `corresponding-source.zip` is a source-review payload, not a Git
checkout. It excludes historical RBFs, PDFs and Office files retained in the full
repository. Build scripts need Git metadata and the full project inventory.
Follow `SOURCE-CHECKOUT.txt` beside the archive to clone the repository and check
out the exact release revision before following `docs/BUILD_WINDOWS.md`.
## First launch and recovery
Choose Computer → Coco 3 Plus. It should reach Disk Extended Color BASIC.
@@ -96,10 +121,21 @@ welcome/help strings no longer expose the retired development name. The native
profile override remains `coco3plus`; changing the display identity does not
require abandoning the existing saved settings or media.
For rollback, return to MENU and restore `_Computer/Coco 3 Plus.mgl` from the
receipt's remote backup directory. Its previously addressed RBF remains in place.
Restore backed-up boot/SSC/path files if those inputs also need rollback. Existing
saved CFG was not overwritten. On a first installation, select the preserved
stock CoCo3 entry to use the original environment. Keep backup/staging folders
until physical cold-start and audio checks pass; failed installs retain their
staging evidence instead of deleting it automatically.
For rollback, return to MENU and use the receipt's stage/backup paths. If
failure happened before activation_attempted, the old launcher is unchanged,
but some supporting files may already have been replaced: restore their backed-up
versions if needed before loading the previous core. If activation was attempted,
launcher_activated: null means a transport failure left its outcome uncertain;
inspect the installed launcher rather than assuming it was rolled back. A null
loaded value likewise means the load command was attempted but not confirmed.
When the old launcher needs restoration, restore _Computer/Coco 3 Plus.mgl from
the remote backup directory. Its previously addressed RBF remains in place.
Restore backed-up boot/SSC/path files when those inputs also need rollback.
Existing saved CFG was not overwritten. On a first installation, select the
preserved stock CoCo3 entry to use the original environment. Keep backup/staging
folders until physical cold-start and audio checks pass.
Run python tests/test_install_mister.py to exercise launcher-last activation and
deliberate pre-activation interruption on a disposable local mock target. These
tests do not access a MiSTer or establish physical power-loss behavior.