Files
AStar/docs/VALIDATION.md
Brian Holman 0c3f8c0324 Integrate AStar with VCC Plus disk builds and verified run
Add the vccplus-disk packaging target, project settings, playable AStar.DSK, actual MCP framebuffer screenshot and build-43 validation. Preserve upstream C sources and Makefile unchanged.
2026-11-09 23:33:13 -07:00

58 lines
2.7 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# AStar installed-app validation
Verified **November 9, 2026** through the installed VCC Plus public MCP build
and disposable-playtest interface. This records the selected demonstration;
it is not a full library regression suite.
## Configuration
- VCC Plus **3.5.0 build 43** and its bundled CMOC/Make/disk tools.
- An isolated native copy of the installed application was used to preserve the
active CoCoMan workspace. Its emulator code was unchanged; the bundle identity
was changed and the copy was ad-hoc signed for isolation.
- **Release** configuration; **512 KB RAM, MC6809, Disk BASIC**.
- Approved Make recipe: `VCCPlus.mk`, including upstream `Makefile`.
- Public build action: `disk`; declared target: `vccplus-disk`.
- Declared launch command: `LOADM"ASTAR":EXEC`.
## Build evidence
- Project ID: `963A54EE-D02A-4701-B53A-92FC0BB62D02`; source revision: `0`.
- Recipe ID: `ae0576ed455aa0f6ef31e0372662312b63aa633b175928b7115e9df71267cb88`.
- Build ID: `7237D773-A262-4AE3-9F67-674F2300FC8B`; result: **succeeded**.
- Artifact ID: `1158FAAB-2636-487E-9FB7-68DD272F8CCF`.
- `astar.bin`: **4,540 bytes**; SHA-256
`a967c02ebdb8f5dff0e94d9768fdb0fd37071c22542a9feedc0444c6903e6722`.
- Delivered `AStar.DSK`: **161,280 bytes**; SHA-256
`48c532dee5a302f7b0841f9353c218ae61bee23af0d1bac576e41d11cde3e502`.
CMOC emitted two existing warnings in `astar-demo.c`, at lines **183** and
**242**, about assignment used as a condition. The original source was not
changed to suppress them. Compilation, linking and disk packaging completed.
## Execution and screenshot
The MCP-owned run `321CD4AD-E480-4BB8-95A6-271182F20B74` reached the actual
running demonstration. Its framebuffer showed the grid, a drawn path and the
text **FOUND PATH: A B C G F J K L**. The capture was taken after **1,072 emulated
video fields**, with **5,120 bytes read from disk**, zero disk writes and the
same disk SHA-256 as the verified artifact. The run was then stopped and its
test disk retained by VCC Plus.
[The screenshot](screenshots/running.png) is the actual **640 × 480** framebuffer
returned by MCP. SHA-256:
`689f47c217418b2b0702aa37bf4055bf16ad81e3eb805c2f5544be4a049302b0`.
It is not an illustration, an old distribution disk capture or a build log.
The source waits for a key and returns to BASIC after the displayed result;
this capture session stopped the owned run rather than separately testing that
key-to-BASIC transition.
## Scope
This establishes a fresh Release disk build and a successful displayed result
for the specified MC6809 configuration. It does not claim HD6309 execution,
Intel/Rosetta qualification, physical CoCo hardware, audio listening,
comprehensive library tests or all possible pathfinding inputs. No private
connection grant or raw host log is included in this repository.