# makePAD runtime observation — macMAKE v0.1.1

**Evidence origin:** official release  
**Observed:** 2026-10-18  
**macMAKE release archive SHA-256:** `d83c173d4184a67738df3bad7d0cadb2b6eab45fa2cc06df89f9f7eff4bd0656`  
**macMAKE CLI SHA-256:** `1699a6925a7f994651335e54ead45bc40da9ee1cdda48aae592042e5ed3491d8`  
**Guest:** Mac OS 9.2.2 in QEMU 8.2.2, `mac99` machine, PowerPC G4, 1 GiB RAM, 800×600 display  
**Application:** makePAD v0.1, MacBinary II SHA-256 `505a3b1deb62ffc396537b1010c8f23921f4ae4308ac6ee989ccf7cd285ca3d1`  
**Build evidence SHA-256:** `68829c98db369c0d6b6fdec5f11951ca2fe901e1d227c8aaf5734169149907b7`  

## Observed behavior

The exact macMAKE v0.1.1 executable built makePAD using the standard Classic PowerPC project build workflow. The resulting MacBinary II artifact was transferred to the Mac OS 9.2.2 guest using the MacFiles workflow.

1. The application launched from the guest volume without loader or CFM errors.
2. The operator entered `rc7 runtime ok`; the application window properly received and rendered the typed text.
3. The operator selected File > Quit. The application opened its standard unsaved-changes dialog.
4. The operator clicked "Don't Save". The dialog dismissed and the application terminated cleanly, returning control to Finder.
5. The run report recorded status `application_completed_and_runtime_confirmed`, all checkpoints satisfied, `timed_out: false`, and QEMU exit code 0.

## Verified screenshot evidence

Both original captures are unmodified P6 PPM files with exact dimensions (800×600) and RGB payload lengths (1,440,000 bytes):

| Checkpoint | Dimensions | File bytes | SHA-256 | Visual Result |
|---|---:|---:|---|---|
| `guest_boot.ppm` | 800×600 | 1,440,015 | `7dc1fce7441346067023e89d542dc95e9c2e91006e26703769a4326a7c8e6ab2` | Finder desktop and Applications window visible |
| `application_state.ppm` | 800×600 | 1,440,015 | `2fc378da228afdb12490e3079eb913d2e485f79c8e87966758e152cf61de8bf1` | makePAD foreground window with `rc7 runtime ok` visible |

The two captures are visually and cryptographically distinct, confirming independent checkpoint states.

## Base disk integrity

The guest base disk has SHA-256 `5998d787dea695734948a52285e7b57d6cae840f2681a174f98e33ec9e8045e8` before and after the run. All writes during execution occurred strictly within the ephemeral copy-on-write overlay.

## Known nonblocking issue

While awaiting each operator response, the runner printed the entire prompt on each 250 ms timeout. The interactive test completed and evidence was verified, but console and log output contain repeated prompt lines. This is a known nonblocking defect documented for a subsequent maintenance release.

## Inputs and privacy

The build used authorized Universal Interfaces and Metrowerks MSL files that are not redistributed with macMAKE. No SDK files, ROM images, or guest disk images are included in this public record.