The serial INP deliberately kept bits 7 and above ("they belong to the frame,
leave everything above alone"). That made a tape depend on whatever happened to
be in the cell before the read, and the two R8Forge machines do not do it: their
-i assignment replaces the whole cell. Measured consequence: examples/calc.r8asm
(a 62585 character tape, cell 11, well inside the limit) printed
> 0000 / > 0000 / > 0000
here instead of "> 0046", while r8forge_tape_run and r8forge_derive agreed on
62 32 48 48 52 54 10. The digit window and the display were not at fault:
drv/calc_disp.r8asm already printed correctly in both machines.
INP now writes `frame` (character + parity/stop if framing is on, zeros above)
and no longer ORs the old cell back in. With that:
rot8_test --cell 11 --input "12 34 + ." calc.rot8 -> > 0046
and the smoke checks are unchanged: serial R8F, -n 512 1536 512, 7E1 A. README
and docs/serial.md said bits above the character stay untouched; they now say INP
writes the whole cell, which is what every implementation does.
The README had grown to 305 lines while features kept getting appended to it: a
35-line frame dump, a full option table, and three paragraphs of essays about
parity hardware. Split by what a reader needs first:
README.md intro + instruction table + quick start + I/O modes + live
view (trimmed sample) + geometry + 7E1 in five lines +
build/test 305 -> 181 lines
docs/serial.md bit 7 not owned by I/O, why characters are not space
separated, the frame layout, why a stop bit is a bit in the
cell, and the "parity costs one latch" essay
Verified the commands the new quick start and test sections show against the
build: --input R8F on serial_echo (prints R8F), -n on and/or/full_adder (numbers),
--dump on wave (259 cells), --7e1 with input A.