Files
Quadrapassel/docs/BUILDS.md
T

6.2 KiB

Numbered game disks

Brian requested this delivery convention on November 11, 2026: QUADPSLxx.DSK, with a two-digit build number and fresh high scores for each new delivered build. Begin at 01. The current delivery is 05; the next changed delivery is 06. This number identifies the game disk, independently of the VCC Plus application build.

Build Date Filename Contents / validation
01 2026-11-11 QUADPSL01.DSK Title spacing, credits, scoring labels and extra standard-library mute; historical artifact in Git
02 2026-11-11 QUADPSL02.DSK Initial shared-row/axis fix; Brian reported actual joystick failure after DOS load
03 2026-11-11 QUADPSL03.DSK Internal candidate; native test exposed target calibration argument error; withdrawn
04 2026-11-11 QUADPSL04.DSK Correct target argument loads, stable fire, scene readiness; native emulated joystick checks pass
05 2026-11-11 QUADPSL05.DSK Fire 2 hard drop once per press; actual standard right-port press/held/repress and input regression checks pass on official build54

Build 01 is 161,280 bytes, SHA-256: 4ac171e87c51dfd99b302b9e035a91a59c030144e5ae0661a6d2dfc84ba3a63f. It contains only QUAD.BIN, WORDS.DAT and QPTEXT.DAT, plus the existing DOS boot track. Neither QPSAVE file is present, so the game starts with default preferences and an empty scoreboard, creating save data through the normal save path.

The official build recipe continues producing the clean Quadrapassel.DSK staging artifact. After a successful qualified build, inspect its directory for unexpected files and personal QPSAVE data, then copy it without overwriting to the next QUADPSLxx.DSK. Verify the copy hash equals the official artifact hash and record the delivery here. Rebuilding unchanged content does not consume a new number; a changed delivered candidate does. Do not reuse an old numbered filename, migrate personal scores automatically, or overwrite/remount a user's disk. Keep numbered deliveries distinct from writable playtest copies.

The name change alone required no guest code rebuild or new gameplay test: build 01's bytes match the already-tested artifact. It does not establish that the reported normal-window buzzing is fixed. Existing personal score disks and backups were left unchanged.

Brian authorized committing and pushing the implementation and build 01 on November 11. The Git commit adding QUADPSL01.DSK records its source snapshot; use git log -- QUADPSL01.DSK to identify that commit. The game bytes were qualified before committing and are unchanged from the official artifact.

At the build-01 stage, Brian requested cleanup of obsolete builds. Build 01 was then the only retained current game delivery. Compiled objects, generated staging files, old probe/ staging images and host test scratch were removed after verification. Personal score backups and the mounted disk remain untouched; ignored WAV/JSON diagnostic evidence is retained while the normal-window buzz is unresolved. Historical source and selected evidence remain in Git.

Historical build 02 pristine SHA-256: 4e3af2440a3195ee5864498e39a779362988257d8a39cfc1c413157ace287a3c. The old build-01 filename was observed loaded in VCC Plus, so that local disk is left untouched during cleanup. Its pristine historical artifact remains in Git history; it is excluded from future commits to protect any personal save writes.

Withdrawn internal build 03 SHA-256: 80c511fe9c9b1a0faaeffa688dec6d73de39280f8eb3c9ce584727fc396f09ca. Its official Release build/isolated run identities are in JOYSTICK_FIX.md. It starts with default settings and empty scores. Code/const end $7ACD, static end $13FD; the 1024-byte stack reserve is unchanged. The writable build-02 file is preserved locally and backed up byte-identically under ignored personal media; it is retired from tracking rather than resetting its saved contents.

Build 04 is the preceding clean delivery, SHA-256: 1cddb6bdf17857b915e96a6929e14181bad05cfae73278a4919add26fea0ba45. QUAD.bin is 26,581 bytes, SHA-256: f79dd5b4ba32ab592bd2b1cb21bea2847b58bd88a1343a9507e1e72e26fe6767. Official native build53 Release disk builds FC462D93 / A7A18927 passed; code/const end $7AD4, static end $13FD, 1024-byte stack reserve. Native right-port emulated analog/button checks passed for left/right, four lasting T turns and steering after keyboard resume. Physical hardware/controller, left port and 128 KB remain pending. See CMOC_JOYSTICK_ARGUMENTS.md for cause, evidence and exact limits. Pristine QUADPSL04.DSK contains only QUAD.BIN, WORDS.DAT, QPTEXT.DAT and the DOS launcher; empty scores/default settings. The app mounted a separate working copy. Withdrawn pristine build03 and unmounted test scratch are removed during cleanup; personal build01/build02 images and backups are retained unchanged.

Build 05 is the current clean delivery (161,280 bytes), SHA-256: d05ab25fd90171b048cce54f3af18ca6d0bd81335e138044ff05315e99cbf582. QUAD.bin is 26,623 bytes, SHA-256: ed5460993770f80bd1560001892ef34d4845ddf9eafe40fc732d1033a9c84290. Official build54 project 273E195B-8BFC-495F-A1F8-E1469759B910 revision0, Release build CC51E81E-B5E2-4670-B8FA-15785BAFEB51, artifact F137D778-646A-43AE-9CF1-92A658464FF3, zero diagnostics. Its outputs exactly match the earlier native build53 C671F741 candidate; the compiler workaround remains. Code/const end $7AFE, static end $13FD, original 1024-byte stack reserve. The directory contains QUAD.BIN, WORDS.DAT and QPTEXT.DAT plus DOS launcher; 50 free granules, no QPSAVE files. The numbered copy was created exclusively and its hash checked after the owned run stopped.

Actual MC6809/512 KB standard right-port joystick tests passed Fire 2 held for 180 fields (one lock), neutral then press (second lock), both horizontal walls, lasting primary release rotation, Up hard drop, keyboard pause/resume then joystick LEFT. Input traces confirm actual analog/button states and neutral release, not guest keyboard aliases. The owned run stopped with disk retained, zero writes and unchanged pristine hash. Details and qualification limits: SECONDARY_BUTTON.md. The old build04 file and byte-identical backup remain locally, retired from tracking; personal build01/build02 and backups are untouched.