- repository baseline
- MIT licence
- Hatari container
- runtime/config/artifact mounts
- Hatari version reporting
- ST/STE profiles
- EmuTOS integration
- automated CI smoke test
- consume canonical
MINIMAL.PRGfrom atari-dev - validate the atari-dev → atari-runtime hand-off
- execute the same canonical artifact under ST and STE profiles
- Hatari + EmuTOS automated runtime qualification
- require guest-side
C:\\MINPASS.TXTGEMDOS evidence - verify the exact PASS marker
- GitHub Actions run #56 qualified both ST and STE
Physical Atari hardware is not required. Emulator qualification is authoritative for this project.
- reusable GitHub Actions workflow for consumer projects
- canonical atari-dev artifact hand-off
- ST and STE guest execution qualification
- machine-readable evidence and guest marker verification
- evidence artifact upload
- self-test run #1 PASS on both profiles
- keep Hatari + EmuTOS as the authoritative baseline
- retain ST and STE profiles
- persistent machine-readable qualification evidence
- retain useful emulator logs/traces
- add Steem SSE as an independent ST/STE cross-emulator
- execute the same canonical atari-dev artifact across supported emulators
- Steem SSE + EmuTOS guest execution qualified in GitHub Actions run #120
- exact GEMDOS marker verified from the AUTO floppy after CRLF normalization
- ARAnyM + EmuTOS headless boot with framebuffer evidence qualified in GitHub Actions run #5
- ARAnyM extended FreeMiNT/TT/Falcon-oriented profiles
- provisioned the current redistributable upstream FreeMiNT ARAnyM snapshot
- FreeMiNT boots under ARAnyM + EmuTOS in CI
- guest-side execution is required: pid 1
xaloaderexecutesxaaes.km - upstream Bash startup hook creates the exact Ploos-AS PASS marker inside the FreeMiNT guest
- case-insensitive guest marker content is verified and retained as machine-readable evidence
- GitHub Actions ARAnyM integration probe run #55 PASS
- TT/Falcon profiles where supported
falcon-040profile qualified with standard ARAnyM build in GitHub Actions run #61falcon-040requires the same FreeMiNT guest marker and XaAES execution gates as M4.2- profile-specific machine-readable evidence records the ARAnyM virtual-machine fidelity boundary
falcon-040-mmuqualified from a dedicated upstream ARAnyM full-MMU build: full MMU, FreeMiNT bootstrap, XaAES and guest marker PASS- standard Ubuntu ARAnyM package remains the non-MMU
falcon-040baseline - do not label ARAnyM as a TT emulator; TT qualification requires an emulator with an actual TT machine model
- Hatari
ttmachine qualified with EmuTOS boot, canonicalMINIMAL.PRGguest execution, and a CI-built FreeMiNT 68030 kernel - TT FreeMiNT boots natively from a FAT16 ACSI disk and executes a guest-side probe
- exact
PLOOSPAS.TXTFAT 8.3 marker is persisted to the ACSI image and verified host-side - TT FreeMiNT qualification PASS in GitHub Actions run #36924355353
- additional emulator coverage when it adds independent value
- physical-hardware reports are optional supplemental evidence, never a release gate
- maintain a single explicit matrix of qualified emulator, machine, CPU and OS combinations
- distinguish actual Atari TT emulation from ARAnyM Falcon-oriented virtual-machine profiles
- record the required guest-side evidence gate for every supported runtime profile
- keep physical hardware supplemental rather than a release gate
- machine-readable
profiles/runtime-matrix.ymlis CI-validated - GitHub Actions qualification run #37116922793 PASS
- expose qualified runtime profiles through a stable command-line contract
- allow consumer repositories to require a profile and fail closed when it is unknown or not PASS
- keep the contract backed by the M4.4 machine-readable matrix
- validate all currently qualified profiles in CI
- reusable qualification workflow fails closed unless the requested profile is present and PASS
- GitHub Actions qualification run #37119923731 PASS
- version the consumer-facing runtime profile contract independently of individual emulator profiles
- expose contract identity in machine-readable CLI output
- fail closed when a consumer encounters an unsupported contract version
- preserve the v1 field semantics for compatible additions
- qualify contract-version behavior in CI before declaring M5 PASS
- Hatari is the explicit reference emulator for ST, STE and TT baseline qualification
- Steem SSE and ARAnyM remain supplemental independent/extended qualification paths
- reusable workflow requires
atari-runtime-profile/v1andstatus=PASSbefore consuming caller artifacts - GitHub Actions qualification, Steem SSE and ARAnyM runs for commit
9669d68PASS
- define
v1.0.0as the first stable runtime release - retain
v1as the moving compatible major tag - freeze
atari-runtime-profile/v1compatibility semantics - keep Hatari as the reference emulator for the v1 baseline
- validate release identity and runtime contract together in CI before tagging
atari-devconsumes the reusable qualification workflow through moving major tag@v1- canonical
MINIMAL.PRGis qualified on both ST and STE profiles - end-to-end GitHub Actions run
37121828700PASS - stable checkpoint:
v1.0.0/atari-runtime-profile/v1; further M6 work is intentionally paused