History

Kinneyzhang aeb1b0f7c7 feat(reactive): isolate dispatcher contexts		2026-09-01 02:17:13 +08:00
..
benchmark-scheduler-context.el	feat(reactive): isolate dispatcher contexts	2026-09-01 02:17:13 +08:00
emacs-gui-verifier.el	test: add fail-closed Emacs GUI scenario engine	2026-08-28 13:43:50 +08:00
etaf-m0a-inventory.el	feat(runtime): add postcommit retirement journal	2026-09-01 01:25:34 +08:00
etaf-m0b-component-manifest.el	docs: close M0b public contract drift	2026-08-31 13:43:23 +08:00
README.md	test: add fail-closed Emacs GUI scenario engine	2026-08-28 13:43:50 +08:00
record-screen.exp	test: add fail-closed Emacs GUI scenario engine	2026-08-28 13:43:50 +08:00
run-emacs-gui-verification.sh	test: add fail-closed Emacs GUI scenario engine	2026-08-28 13:43:50 +08:00

README.md

Generic Emacs GUI verification

This directory owns the reusable verification mechanism, not application scenarios:

emacs-gui-verifier.el defines Scenario, ordered Action, run-local Context, checkpoint sequencing, assertions, completion, and fail-closed evidence finalization.
run-emacs-gui-verification.sh owns one named daemon, explicit load paths, external application activation, recorder lifecycle, driver loading, report generation, and exact cleanup.
record-screen.exp keeps macOS screencapture -v attached to a PTY and stops it through an explicit signal. It contains no Emacs or application logic.

Concrete repositories provide adapter files that construct a Scenario and an entry function. The generic command is:

scripts/run-emacs-gui-verification.sh run ADAPTER.el ENTRY \
  --load-path /path/to/provider \
  --run-dir /private/tmp/my-gui-run

Fresh captures intentionally remain INCOMPLETE until their selected images and contact sheet are reviewed. Finalize the same evidence directory with:

scripts/run-emacs-gui-verification.sh review /private/tmp/my-gui-run

Only VERDICT=PASS is completion evidence.