badline 0.13.0 → 0.14.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2a074ca0626351bec4132e06bc5e4ab951f7a4b18cf9e78ddc3c16adfd4194b8
-  data.tar.gz: 878629423f450e6c6440649b00d87646c1ff59d5ccb99801d5909fedc14f9108
+  metadata.gz: 320b4659e6c9945509741f928989b2378d38ae18a51c1dd5bbca706e3b3ada54
+  data.tar.gz: 9a6ce80ab26e74e325c8fb660f4ed1fabc64a6e3c1859b723b3816aebe3f4b55
 SHA512:
-  metadata.gz: 8eb5553980d187ccafd1ac4906b8a3d7fb6a80a8219375ef872f208411c362bf3724e721946ed166b91595177ce3adf38632e2b69008d9a4082032239cfcb697
-  data.tar.gz: dcb3a6ab34cceff4e85b56d09c2e38eaeab8350f57928c07e23ba7c6f5de38b32a88a0735802a2d196bb2ccf89a6a058579a47daf85ca8ac275f5b6bce90a975
+  metadata.gz: 0f4e3b6c6bc7c35eec18ea3a81165050183e92eeebab3c04b12472970b5b0a87d8ad860ceac81e411a39836c601239b3e708bcffbcb7f4eb6561599c1cda1522
+  data.tar.gz: 61d6698127237a45d99febd816088da06d227519b34455188babc7dafebb977613a61c1472ed348c691433a8c02f4dcbab0346f48083b71fc02035f64f7c8549

data/CHANGELOG.md

@@ -1,5 +1,54 @@
 # Changelog
 
+## [0.14.0](https://github.com/elektronaut/badline/compare/v0.13.0...v0.14.0) (2026-10-11)
+
+
+### Features
+
+* add the keyed snapshot record encoding ([1b87aed](https://github.com/elektronaut/badline/commit/1b87aeddea27f81cb1ccedbbef2bba58c2db0bb3))
+* boot the Plus/4 and the C16 to READY headless ([278020e](https://github.com/elektronaut/badline/commit/278020ee0256fa1d085391fd0e7a6679ac80dbcb))
+* bundle the 264 series ROMs and refuse badline plus4 until it runs ([7072ae7](https://github.com/elektronaut/badline/commit/7072ae7cb6e1ccd96a4e02eb1146b7b1bfaf7125))
+* give each machine its keyboard buffer layout ([0b64648](https://github.com/elektronaut/badline/commit/0b64648fec3cd56bbbee1ac4dc8fe446c84dd4b9))
+* keep the KERNAL's file variables in KernalTrap::Layout ([0ca7488](https://github.com/elektronaut/badline/commit/0ca7488505b2b7af9f358bdf6d3e86a1e1c768e3))
+* keyed snapshot fields for device 8 through the KERNAL traps ([cce36f2](https://github.com/elektronaut/badline/commit/cce36f2f740c5337cd2b0a66fe99394114409c32))
+* keyed snapshot fields for each machine's own state and setup ([ff251a6](https://github.com/elektronaut/badline/commit/ff251a62cbad4502f576628a4f4c5d3d6a22eaf8))
+* keyed snapshot fields for the 1541 ([f3f57b7](https://github.com/elektronaut/badline/commit/f3f57b7e24471e198304bfd90ba16c4abb7c4c16))
+* keyed snapshot fields for the 1571 ([5ceb741](https://github.com/elektronaut/badline/commit/5ceb7416a1902252d97c80aff22658a68e4abfb6))
+* keyed snapshot fields for the 1581 ([1c67e29](https://github.com/elektronaut/badline/commit/1c67e298c24e82e92cc5feddcc0153143d4eda8d))
+* keyed snapshot fields for the 6502 cores and the Z80 ([8ee592e](https://github.com/elektronaut/badline/commit/8ee592e5ee5b658c8f452cf4bdf9df044f8c19ab))
+* keyed snapshot fields for the C128's MMU ([aa861ca](https://github.com/elektronaut/badline/commit/aa861cac0a33d79f777b60310f0cb573024f2d60))
+* keyed snapshot fields for the cartridges ([349ae81](https://github.com/elektronaut/badline/commit/349ae81c7c002f5c1b94fa50cc994a6b7ec16915))
+* keyed snapshot fields for the CIA ([b5a6ff8](https://github.com/elektronaut/badline/commit/b5a6ff8b02026daa3ec6247ab4024d35efedb18e))
+* keyed snapshot fields for the datasette and its tape ([37a52f1](https://github.com/elektronaut/badline/commit/37a52f1018ab226a60395e1c98c6a362c0159f01))
+* keyed snapshot fields for the memories, RAM expansions and buses ([14b1a95](https://github.com/elektronaut/badline/commit/14b1a951a44c2bc23871208b9843489d4ca6963c))
+* keyed snapshot fields for the REU ([8088ac5](https://github.com/elektronaut/badline/commit/8088ac52c68667db7d6acdc6e0f0b629e165b0b3))
+* keyed snapshot fields for the SID ([b58f88d](https://github.com/elektronaut/badline/commit/b58f88d1a98346aba4dbec0dead306b3d36b32f7))
+* keyed snapshot fields for the VDC ([b894c3e](https://github.com/elektronaut/badline/commit/b894c3ef0b83988d17f03027b1831e7be3739be3))
+* keyed snapshot fields for the VIA ([52ab12c](https://github.com/elektronaut/badline/commit/52ab12cb129adedc8a3f0b7df469a1440eb72309))
+* keyed snapshot fields for the VIC-I and its sound ([a47d3e8](https://github.com/elektronaut/badline/commit/a47d3e823891e5d597141423f1675962ac266df7))
+* keyed snapshot fields for the VIC-II ([8fc8b4c](https://github.com/elektronaut/badline/commit/8fc8b4c39f8ae5cac781f51f0bbeab5134c3bc9f))
+* latch the VIC's sprite collisions when a snapshot settles ([a1c9429](https://github.com/elektronaut/badline/commit/a1c9429fefdbbc57407fb68baf057209d7163db1))
+* let a unit report its own adjustments when its snapshot loads ([3b3af19](https://github.com/elektronaut/badline/commit/3b3af19ef0d74b0a45fbea96feef107f26db12a6))
+* read Plus/4 CRT images ([450148d](https://github.com/elektronaut/badline/commit/450148db02c8057cc071f6d867707aa45a87c996))
+* read version 2 C16 tapes and time the datasette's read level ([7e78070](https://github.com/elektronaut/badline/commit/7e78070877394a4657e23699a3098f297469be05))
+* report a VIC-II line restarted from another renderer's snapshot ([6cb0607](https://github.com/elektronaut/badline/commit/6cb06075d410e59a8cd6f7d82d29757819e23e67))
+* run the 264 testbench's exitcode rows as testbench-plus4 and testbench-c16 ([862f14b](https://github.com/elektronaut/badline/commit/862f14bd474bdac92017f25a57a057cf1f42a63f))
+* run the Lorenz suite's plus4 build as lorenz-plus4 ([006efdd](https://github.com/elektronaut/badline/commit/006efddeb3a052714b99ff9b11ec18dd85cb6778))
+* save and load snapshots as BL-* modules ([25db1be](https://github.com/elektronaut/badline/commit/25db1be28817d292c314672c5401251d36d11902))
+* save snapshots at the next instruction boundary ([3f9ae3c](https://github.com/elektronaut/badline/commit/3f9ae3cf5392c194a1915801c9da4739832649e3))
+
+
+### Bug Fixes
+
+* boot C128 boot sectors on .g64 and .g71 images ([81ad184](https://github.com/elektronaut/badline/commit/81ad1842fdc66b5ddb5d2988eb699409741f376a))
+* draw the true drive's power LED, and the LEDs of a drive plugged in after start ([982c522](https://github.com/elektronaut/badline/commit/982c522c56c46d193ca5d15f49c59f221f04ad8e))
+* drive the datasette's write line from the CPU port's bit 3 ([b90c29d](https://github.com/elektronaut/badline/commit/b90c29dd758eb7867930c5f26dbd0ae510f430af))
+* let a held key go as the key it pressed across a C128 mode switch ([3a8d731](https://github.com/elektronaut/badline/commit/3a8d7313034f0b69057528b58ff247250b7e7168))
+* read the ROMs and I/O a C128 KERNAL bank maps when saving ([3e4db21](https://github.com/elektronaut/badline/commit/3e4db218959237fada950e4b65238203af10e3c6))
+* run the VIC-20's sound voices whether or not the host plays them ([13052c7](https://github.com/elektronaut/badline/commit/13052c7bbb9ca2b4ed678935ec6b88cc84bb2806))
+* take the C128's own keys in --at key= ([428047c](https://github.com/elektronaut/badline/commit/428047cc4eca55b70967048d49579840b90ea946))
+* type --at type= text on the C128's key matrix while the Z80 runs ([39d77ff](https://github.com/elektronaut/badline/commit/39d77ff29989a46c82184cd2dde03e8d470c553b))
+
 ## [0.13.0](https://github.com/elektronaut/badline/compare/v0.12.1...v0.13.0) (2026-10-11)
 
 
@@ -81,7 +130,6 @@
 * bundle the PET 64's KERNAL, 901246-01 ([9a029ec](https://github.com/elektronaut/badline/commit/9a029ecfe25c0d9a806d8858253c4c172e175b7f))
 
 
-### Miscellaneous Chores
 
 * release 0.10.1 ([9d6f6ba](https://github.com/elektronaut/badline/commit/9d6f6ba71a647f24f00a830fbc772531fbcb4d92))
 

data/CLAUDE.md

@@ -92,6 +92,13 @@ Z80), and names the first component that differs. It builds a C64 unless
 `--family vic20` or `--family c128` (with `--mode c64|c128`) says
 otherwise. Use it for refactors and speed work.
 
+`bin/snapshot_check` checks snapshots. For each scenario (`--list`) it saves
+twice, then saves, loads and saves again, and expects the same bytes each
+time. It then runs the saved and the loaded machine side by side and names
+the first difference. `--carts` does the same for every cartridge mapper,
+and `--diff A B` compares two snapshot files module by module. Run it on any
+change to a unit's saved state.
+
 ## Driving the emulator headlessly
 
 `exe/badline-ruby <media>` opens the SDL window, which is no use for checking
@@ -153,7 +160,7 @@ worktree and owns a different set of files.
 
 - `rake vendor:checkout` fetches SingleStepTests 65x02, the Z80 sample
   and VICE-testprogs into `vendor/`
-- `bundle exec rspec`: line coverage is about 97%. `spec/spec_helper.rb`
+- `bundle exec rspec`: line coverage is about 95%. `spec/spec_helper.rb`
   fails a whole-suite run (every spec file, no filters) below 90%, while
   single-file and filtered runs skip the floor. `:slow` specs are excluded
   by default: run them with `bundle exec rspec --tag slow`
@@ -200,12 +207,25 @@ the rows your change can't reach tell you nothing about it.
   `ruby --yjit bin/lorenz [image] [start_test] [max_cycles]` (resumes the
   chain at a named test, and `--stop-after NAME` ends it once that test is
   done). These take seconds to minutes
-- A pull request's CI is the verdict. It runs every suite on the Spinel
-  build, compared row by row against
-  `test/baselines/`, and every job is a required check. A row that moved
-  fails it. A pull request that changes only docs, or only a release's
-  version bump, skips the specs and suites; pushes to main always run
-  them. Re-record only those rows, in the same change:
+- A pull request's CI is the verdict, and a pull request merges on it
+  alone. It runs the specs, Rubocop, Minitest, the harness builds, the
+  Spinel checks, the native round trip, and the suites its changed files
+  can reach, on the Spinel build, compared row by row against
+  `test/baselines/`. `test/support/ci_reach.rb` maps paths to suites, and
+  a path it doesn't name runs every suite. A row that moved fails it. A
+  pull request that changes only docs, or only a release's version bump,
+  skips the specs and suites. A row that moves in a pull request's CI is
+  re-recorded in that pull request with its reason; nobody waits for
+  `suites.yml` to confirm it. A change that reaches a suite the map
+  doesn't name adds the path to `test/support/ci_reach.rb` in the same
+  pull request, and a change that adds a directory under `lib/badline/`
+  gives it a rule
+- The full suites run on main every two hours (`.github/workflows/suites.yml`).
+  Nobody waits for it, polls it or dispatches it to check a pull request.
+  Its result is a `suites` commit status and, when red, one `suites-red`
+  issue the planner owns. A red main never blocks a merge. A release
+  publishes only once its tagged commit is green
+- Re-record only the rows that moved, in the same change:
   `rake "regression:record:<suite>[filter,...]"` (quote it, because zsh
   globs the brackets). It runs only the matching tests on CRuby and
   splices their rows into the baseline, and every other row keeps its

data/CONTRIBUTING.md

@@ -91,9 +91,10 @@ bundle exec rubocop
 ## Tests and commits
 
 - Add tests for any behavior you change.
-- CI runs rubocop, the specs and every regression suite on each pull
-  request, and fails on any suite row that differs from its baseline in
-  `test/baselines/`. When a change moves rows on purpose, re-record just
+- CI runs rubocop, the specs and the regression suites a pull request's
+  changes can reach on each pull request, and fails on any suite row that
+  differs from its baseline in `test/baselines/`. Every suite runs on
+  `main` every two hours. When a change moves rows on purpose, re-record just
   those rows as [test/baselines/README.md](test/baselines/README.md)
   describes, and say why in the pull request.
 - Write commit messages using

data/README.md

@@ -107,6 +107,7 @@ differences noted in the table. `--help` lists the options for either.
 | `--script FILE` | Run the events in `FILE`, one `FRAME:EVENT` a line |
 | `--screenshot FILE` | Save the last frame as a `.bmp` |
 | `--save-snapshot FILE` | Save the machine as a `.vsf` snapshot after the last frame |
+| `--vice` | Add VICE's modules to `--save-snapshot`'s C64 snapshot, so x64sc opens it too |
 
 ```sh
 badline --unpaced --frames 12000 --true-drive disk1.d64 \
@@ -139,7 +140,8 @@ Without `--true-drive`, device 8 is no drive at all but traps on the
 KERNAL's disk routines. Loading is instant, but fast loaders and copy
 protection that run code on the drive need `--true-drive`, which puts
 an emulated 1541 there, running its own DOS at a real 1541's speed. Its
-red LED lights in the bottom right corner of the border. With
+red activity LED and green power LED light in the bottom right corner
+of the border. With
 `--true-drive`, a `.d81` goes in an emulated 1581 in place of the 1541.
 [doc/media.md](doc/media.md) has the details, and how to attach media
 from Ruby.
@@ -225,10 +227,11 @@ snapshots, and x128's `.vsf` files don't load.
 badline's data folder, replacing the oldest, and `F12` restores the
 newest, even after badline has quit and started again. badline also
 autosaves every two minutes of play, and the pause menu's Snapshots page
-saves under a name and loads any of them. Snapshots use
-VICE's `.vsf` format: badline opens those x64sc saves, and x64sc opens
-badline's. See [doc/snapshots.md](doc/snapshots.md) for where they're
-kept, what they hold and how far the two agree.
+saves under a name and loads any of them. Snapshots from badline 0.14.0
+on load in every later version. They use VICE's `.vsf` format: badline
+opens those x64sc saves, and x64sc opens badline's saved with `--vice`.
+See [doc/snapshots.md](doc/snapshots.md) for where they're kept, what
+they hold and how far the two agree.
 
 ## Playing and rendering SID tunes
 

data/doc/media.md

@@ -31,7 +31,8 @@ own DOS ROM on its own 6502 and talking to the machine over the serial
 bus. It reads `.d64` and `.g64` images, which it autostarts with the
 same `LOAD"*",8,1` and `RUN`, but not `.d71`, `.d81` or `.t64` images
 or directories. Loading runs at the speed of a real 1541, and the
-drive's red LED lights in the bottom right corner of the border.
+drive's red activity LED and green power LED light in the bottom right
+corner of the border. A 1581 flashes its power LED after an error.
 
 A `.g64` holds the disk's raw GCR, half tracks and all, so copy
 protection and fast loaders that read it work.

data/doc/pinned-behaviour.md

@@ -38,6 +38,7 @@ only catches the rows that happen to move.
 - [VIC-20 RAM power-on pattern](#vic-20-ram-power-on-pattern)
 - [VIC-I fetches and the V-bus](#vic-i-fetches-and-the-v-bus)
 - [VIC-I sound](#vic-i-sound)
+- [TED beam and the 7501 port](#ted-beam-and-the-7501-port)
 - [1541 serial port](#1541-serial-port)
 - [1541 disk mechanism](#1541-disk-mechanism)
 - [REU DMA](#reu-dma)
@@ -1490,6 +1491,34 @@ wasn't read.
   - Spec guard: *a step* in
     [`vic_i/sound/output_spec.rb`](../spec/badline/chips/vic_i/sound/output_spec.rb).
 
+## TED beam and the 7501 port
+
+Two places where badline knowingly differs from xplus4 r45942, which was
+run as a black box. No hardware capture settles either of them. Whoever
+finds one should start here.
+
+- The line count steps, and the raster interrupt fires, at horizontal
+  count 376, column 47 of `Chips::TED::Beam`: the datasheet's "Increment
+  Vertical Line" decode, which fits its "8 cycles before the character
+  window" for the raster interrupt. xplus4 steps the line about 3 single
+  clock cycles later, and its raster interrupt reaches the handler 2-3
+  cycles later, on display and border lines alike.
+  - Pinned by the TED datasheet in the *Plus/4 Hardware Manual*, the
+    scanned decode table on sheet 11 (page 62 of `hw.pdf`), not by a test.
+    The comparison with xplus4 used trace probes that sample `$FF1E` and
+    `$FF1D` through the lines, described with #644. The Lorenz plus4 rows
+    don't move either way.
+  - Spec guard: *the beam* in
+    [`chips/ted_spec.rb`](../spec/badline/chips/ted_spec.rb).
+- `trap10`, `trap12` and `trap14` of the Lorenz suite's plus4 build, and
+  their `ane` and `lxa` variants, pass on badline and fail (`$ff`) on
+  xplus4. They are the trap tests that put their data on the 7501's port
+  at `$00`-`$01` (`Plus4::CPUPort`: a full 8-bit direction register, P5
+  reading 1 as an input). `readme-plus4.txt` says the trap tests don't
+  work on a real 264, so its results don't decide this either.
+  - Pinned by `lorenz-plus4`'s rows for those tests. The xplus4 verdicts
+    are its exit codes with `-debugcart`, one program at a time.
+
 ## 1541 serial port
 
 - The drive sees the C64's side of the serial bus a host cycle late. The