A throwaway repository for on-box smokes of neosource's direct-VM CI runner: direct-vm-ex44-10 on ex44-10, label direct-vm, registered actor-bound in the neosource workspace (plan plans/ci-direct-vm-executor-2026-10.md in neosource/neosource). Nothing depends on this repo; its runs, branches and history can be thrown away at any time.

Workflow	Trigger	What it checks
vm-smoke-hardening.yml	dispatch	M3.2: the jail, network isolation, cgroup limits
vm-smoke-services.yml	dispatch	M3.1: services:, docker build, the Docker Hub mirror
vm-smoke-toolcache.yml	dispatch	M3.4: preinstalled toolcache and node20, offline
vm-smoke-uses.yml	dispatch	M3.5: action SHA pinning across matrix legs
fork-pr.yml	pull_request + dispatch	M3.1: a fork PR runs untrusted and never commits the cache disk

Run a smoke with neo actions run .neosource/workflows/<file> --ref main from a clone of this repo. The vm-smoke-* workflows are dispatch-only and must stay that way: the runner is self-hosted, so they must never run code a non-writer controls.

fork-pr.yml is the one exception, on purpose: it only prints and writes a marker line into $HOME/.cache/fork-pr-marker (on the cache disk), uses no secrets, and a fork PR from a non-writer is held pending_approval until a maintainer approves it. A dispatch on main (protected, so its cache disk commits) is the trusted probe: it prints the marker as committed, and a pull_request line there would mean an untrusted run committed the disk.