Sync VCC Plus 3.7.1 build 67 source

Refresh reviewed MCP output export, four-drive owned playtests, bounded BASIC readiness, and pinned CMOC 0.1.101 source/patches. Preserve independent source-edition identity, empty libraries, notices and privacy boundaries.

Validated 74 export/privacy checks, pinned dependency sources, and an independent unsigned universal Release build. A subsequent documentation-only correction removes an excluded qualification link; all build inputs remain identical.
This commit is contained in:
Brian Holman committed 2026-11-17 08:42:27 -07:00
1 parent 4abc194001
commit 5534005799
54 files changed
+2950 -435

No files matched your search

+59 -13
View File
@@ -5,6 +5,9 @@ A fresh C connection with **Allow Disposable Playtests** can advertise
`exchange_playtest_media` tools. Check live discovery and `get_capabilities`
before planning exchanges. Existing connections keep their original schemas;
new tools require a newly reviewed connection and a restarted client helper.
Fresh multi-drive grants additionally declare strict Boolean
`playtestMultiDrive: true` with toolset 13 or later. Legacy media grants retain
their FD0-only schema; an app update does not expand an old connection.
This feature operates only on an owned disposable guest, never the ordinary
shared run or personal mounted media.
@@ -61,11 +64,32 @@ counts and a truncation flag identify omitted history. `list_playtest_disks`
keeps its older primary-boot-disk-only contract. Additional world/data disks
are not advertised as primary boot selections.
The drive is **FD0**. No tool accepts a host pathname, another drive number,
arbitrary bytes, another project's disks or a personal guest. Product IDs bind
On a fresh multi-drive connection, `exchange_playtest_media` accepts integer
`drive` 0–3 for **FD0–FD3**; omission means FD0. Legacy media connections remain
FD0-only. No tool accepts a host pathname, arbitrary bytes, another project's
disks or a personal guest. Product IDs bind
to the current artifact, not just a filename. Listing and insertion recheck the
project/revision/artifact and any retained disk's exact provenance and bytes.
## Read a coherent four-drive receipt
Fresh multi-drive results carry `media_contract_version: 2` and a `drives` array
with exactly four bounded observations. Each row identifies numeric `drive`,
`label` (`FD0` through `FD3`), `inserted`/`disk_present`, current `media_id`, byte
count, original/current hashes, generation, dirty state and effective protection.
The host associates the row with product/base provenance, media key and available
retained identities. A media inventory row's nullable `drive` identifies current
placement; product identity remains independent of placement.
`disk_reads` and `disk_writes` count guest-transferred data bytes over the worker's
lifetime. `mount_read_bytes` and `mount_write_bytes` reset at a media-generation
change. They are not counts of completed Save commands. Use guest save/reload,
exact before/after hashes and the relevant generation's activity together. A
rewritten identical value can have activity without a changed content hash.
Read-only listing/capture does not advance emulation. Established top-level disk
fields continue to describe FD0; top-level retained primary fields still identify
the reviewed primary product even when it was moved to another drive.
## Exchange at a guest prompt
1. Boot the primary disk through the project's declared commands.
@@ -75,16 +99,30 @@ project/revision/artifact and any retained disk's exact provenance and bytes.
4. Insert a listed private copy with its exact current hash:
```json
{"run_id":"<owned run>","request_id":"insert-data-1","action":"insert","media_id":"<listed media ID>","media_sha256":"<listed current SHA-256>"}
{"run_id":"<owned run>","request_id":"insert-data-1","action":"insert","drive":1,"media_id":"<listed media ID>","media_sha256":"<listed current SHA-256>"}
```
To leave FD0 empty, omit both selection fields:
This example leaves Home in FD0 and inserts Data in FD1. To leave FD1 empty,
omit both selection fields and name that drive:
```json
{"run_id":"<owned run>","request_id":"eject-data-1","action":"eject"}
{"run_id":"<owned run>","request_id":"eject-data-1","action":"eject","drive":1}
```
An exchange also requires an idle floppy controller. A paused CPU or stopped
`drive` must be a whole number from 0 through 3; booleans, fractional numbers and
out-of-range values are refused. A fresh multi-drive insert also accepts strict
Boolean `write_protected`. Omission preserves that copy's current setting; false
cannot remove format-imposed protection. Eject forbids this option and the
media/hash insertion fields. Protection belongs to the private copy and survives
exchange, restart and retention independently of its content hash.
The same writable private copy cannot be mounted in two drives at once. Eject
then insert to move it; matching bytes alone do not make two independent copies
the same object. An exchange affects only its target drive and never changes
BASIC's current/default drive.
An exchange also requires an idle shared floppy controller, including activity
associated with a different drive. A paused CPU or stopped
motor alone does not prove an incomplete guest transaction has finished. The
app refuses an exchange while a command is pending; it never cancels the guest's
disk I/O to force a swap. Continue through the guest's normal recovery path and
@@ -97,14 +135,16 @@ provenance, stale-ownership or retention refusal before commit leaves the old
paused disk and its dirty bytes intact. The same private copy is reused when switching back.
Exchanges do not reset the guest, advance its field clock, type keys or modify
RAM/registers. The response reports `previous_media`, retained snapshot identity,
RAM/registers. The response reports `target_drive`, `previous_media`, retained snapshot identity,
new selection, `media_generation`, hashes, dirty state and the unchanged clock,
with `guest_advanced: false` and `guest_reset: false`. Normal input resumes the
guest so it can read the newly inserted disk itself. Capture the framebuffer
and inspect the game's response; a successful mount is not proof that the game
accepted the media.
Reuse a request ID only with the identical selection. The cached receipt prevents
Reuse a request ID only with the identical selection, target drive and explicit
protection choice. An omitted drive and explicit drive 0 are normalized to the
same selection. The cached receipt prevents
a retry from performing another exchange; different arguments conflict. Exchanges
consume the existing owned mutation-request budget, not emulated fields. The
normal input, audio, startup and ownership limits remain in force.
@@ -142,12 +182,18 @@ place; do not create another request to repeat an uncertain operation in that ru
## Save, restart and retain every disk
For a one-drive application, insert Home at its save prompt, use its real Save
command, then insert Data to continue. `restart_playtest` cold-boots the currently
inserted private disk through the declared commands; it keeps all the other
private copies and their changes. Insert the boot disk first when the current
data disk cannot boot. Restart does not automatically choose another disk.
command, then insert Data to continue. A multi-drive application can instead
keep Home in FD0 and Data in FD1 and decide its own save routing.
`restart_playtest` cold-boots through the declared commands while preserving
all current drive assignments, bytes and protection. Ensure FD0 contains the
intended boot disk before a DOS boot. Restart does not secretly move the primary
product to FD0 or choose a bootable disk. Startup mount maps are not part of
this interface: insert into other drives through explicit paused exchanges.
`stop_playtest` retains every disk in the owned set, even when FD0 is empty.
`stop_playtest` freezes the mounted state coherently and drains the four drives
through separate bounded exports before worker exit. It retains every disk in
the owned set, including ejected copies and when FD0 is empty. A combined reply
does not concatenate four full disk images across the 1 MiB transport limit.
`retained_media` returns an individual immutable disk ID/hash and product
provenance for each. The established top-level `retained_disk_id` and
`retained_disk_sha256` refer to the primary Home copy. Cleanup remains possible