Reject incomplete install packages and exclude inherited guest disk

This commit is contained in:
bholman committed 2026-11-18 16:33:51 -07:00
1 parent 8088c1fbf6
commit 9b8e25d977
9 files changed
+277 -25

No files matched your search

+10
View File
@@ -160,6 +160,16 @@ timing evidence. Do not add an inventory hash to an old receipt and present it a
newly qualified. Packaging-only changes need not alter RTL, but do not waive this
receipt requirement.
Select that new fit explicitly when packaging; `-Build` defaults to `build/fpga`
only when omitted. Use fresh output names to preserve previous packages:
```powershell
# Complete local install package using your separately supplied verified ROMs.
.\windows\Package-Release.ps1 -Build build/fpga-qualified -Output dist/coco3plus-qualified
# Public core/source package; all separately supplied/assembled ROMs omitted.
.\windows\Package-Release.ps1 -Build build/fpga-qualified -Output dist/coco3plus-qualified-public -PublicPackage
```
The real local-package guards can target a new qualified build and package
without moving or editing historical evidence. From the checkout in PowerShell:
+11 -1
View File
@@ -107,6 +107,13 @@ 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`.
Before any SSH or target access, the installer validates format and local-ROM
state, SHA-256 syntax, the canonical digest-addressed RBF, the launcher's RBF
reference and `coco3plus` namespace, exact boot-ROM identities and default CFG.
An SSC-enabled local package also needs both exact chip ROM identities and the
matching 1024-byte `f4`/`f5` path records. Incomplete or contradictory packages are
rejected locally; `--without-ssc` remains supported with its matching CFG.
## First launch and recovery
Choose Computer → Coco 3 Plus. It should reach Disk Extended Color BASIC.
@@ -127,7 +134,10 @@ but some supporting files may already have been replaced: restore their backed-u
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.
`load_command_sent` value means the command write was attempted but not confirmed.
A true value confirms only that the MiSTer command write succeeded; it does not
confirm guest startup. `startup_observed` remains false until separate hardware
observation, which this installer does not perform.
When the old launcher needs restoration, restore _Computer/Coco 3 Plus.mgl from
the remote backup directory. Its previously addressed RBF remains in place.
+5
View File
@@ -42,6 +42,11 @@ Before public source or binary release, complete the component review for:
objects or resolve their publication status.
- GPL-covered framework modules: retain notices, applicable GPL texts and build
materials/corresponding source obligations for combined distributions.
- `docs/Boot.vhd` is an inherited 224,016-byte guest virtual-disk image, not VHDL
source. `changes.txt` describes `boot.vhd` as an autorun/mounted disk containing
demonstration software. Its software/content provenance and redistribution
terms require separate review. It is excluded from the downloadable source
payload; the inherited Git object remains in the preserved full history.
This list identifies release-review work. It does not revoke or replace original
component terms, establish a blanket prohibition, or claim that review is complete.