Prepare public CoCo 3 documentation and portable VCC Plus workflow

This commit is contained in:
Brian Holman committed 2026-11-11 16:43:19 -07:00
1 parent e9574b6f0d
commit 4aa739780c
16 files changed
+572 -913

No files matched your search

+4 -6
View File
@@ -2,9 +2,7 @@
## November 10, 2026 — C graphics exception
Brian's explicit decision, relayed by the coordinating chat **Deploy VCC Plus
Gitea** (`01a1c3a8-8bde-77f0-b8af-d0d29b874c7c`): **“Approve the C graphics
exception.”** The approved wording was:
The project owner approved the following limited implementation scope:
> C code for screen-memory mapping and drawing changed regions, using CMOC/BGraph
> where practical, with no assembly or emulator changes and explicit 128 KB validation.
@@ -18,9 +16,9 @@ Retain the public-API fallback and compare measured drawing and visible input.
This approval does **not** authorize hand-written assembly, custom sound/input/
interrupt drivers, emulator source access or changes, custom app builds, or a
replacement MCP integration. Official VCC Plus 3.5.5 (48) and reference boundaries
remain required. Further exceptions need review. Actual 128 KB testing remains
separate from the 512 KB MCP worker; Brian offered to perform that manual check.
replacement MCP integration. Use stock VCC Plus and the public reference boundaries in AGENTS.md. New
exceptions require review by the owner of the working fork. The 128 KB baseline
has since been verified; changes affecting memory require fresh target checks.
### Evidence prompting review