Move hosted unitypackage export jobs to the self-hosted fleet

[wallstop]

Filed from central issue Ambiguous-Interactive/ambiguous-organization-build-lock#226. The maintainer decision is recorded there: move the export jobs to the self-hosted fleet.

What the central audit found

The organization enrollment audit records unsafe-hosted-unity-runner for two paid jobs that run licensed Unity work on GitHub-hosted runners:

Workflow	Job	Runner today
.github/workflows/release.yml	unitypackage	ubuntu-latest
.github/workflows/unity-tests.yml	unitypackage-smoke	ubuntu-latest

Both jobs acquire the organization build lock, activate Unity inside a container, and return the license. A Unity portal seat row from 2026-09-06 (central issue #223) shows the matching signature: container-style machine id, root user, client address inside GitHub Actions range 135.232.128.0/17. Hosted runners consume a Named User License seat from outside the known fleet.

What to change

• Run both jobs on a self-hosted runner from the organization fleet. Keep the existing container shape if it works on that runner; the requirement is the physical runner identity, not the container.
• Keep the full lock lifecycle (acquire, activate, export, return, classify, release, gate) on one runner identity.
• Add the required label set to the existing check-unity-runner-availability preflight so an impossible label set fails before queueing.
• Repin nothing else; the lock action pins stay at the authorized release.

Acceptance

• Both jobs declare a literal self-hosted label in runs-on.
• The central audit no longer records unsafe-hosted-unity-runner for this repository.
• One release export and one smoke run complete green on the fleet.

[wallstop]

Implementation is in #737 (fc376aab). Release and smoke exports now use the existing self-hosted Windows/RAM-64GB fleet, with matching preflight labels and the same central editor/acquire/return/classify/release/cleanup lifecycle as native tests. Cross-platform staging preserves all 21 required package roots, sample compilation and the generated exporter. No Unity matrix leg was removed.

Local evidence: actual Windows Node/npm/tar staging exited 0; native export controls 27/27; shell portability 21/21; workflow mutation controls and release publication guards passed. A release export_only dispatch mode validates metadata and produces artifacts while independently skipping tag creation and publication.

Acceptance remains pending: PR fleet smoke, a separate release export-only run pinned to the candidate SHA, artifact/hash and cleanup evidence, then the authoritative central enrollment audit against merged main. The audit reads default branches; a successful audit job alone is insufficient without complete=true and absence of this repository's unsafe-hosted-unity-runner findings.

Main Unity baseline is 52m38s; hosted smoke is 160s (136s export step). Candidate timing and all 14 result sets will be compared. No speedup is claimed yet.

[wallstop]

Native smoke acceptance passed at 249dc218 in job 101666350031: the entire acquire/export/return/classify/release/final-gate sequence ran on ELI-MACHINE, runner 338, and reported confirmed/healthy cleanup with released=true and no incident. Export SHA256 was 08d6be668457eaf8fecd88633af3b1ee3ee4ca368d497129e7af619b8843c765. Smoke job time fell 160s → 80s; the export step fell 136s → 44s. Successful smoke intentionally retains no package-byte artifact, so this is positive execution/hash-log evidence, not an independent download verification.

All 14 test result sets preserved all 139,830 prior passes. Whole-workflow elapsed still increased 52m38s → 82m36s, dominated by a 41m30s late SINGLE_THREADED queue. The subsequent 56b153c1 scheduling sweep queues all six licensed jobs after preflight and keeps the final aggregate dependent on every result. Its run 34099719707 has already passed SINGLE_THREADED and native smoke; the four editor jobs are continuing.

Remaining acceptance is explicit:

• Release export-only dispatch was rejected HTTP 422 because Release Publish is disabled_manually. Permission is pending to temporarily enable it, run guarded export-only validation, and restore the disabled state. No release, tag change or dispatch run was created.
• The authoritative enrollment audit reads default branches, so its complete=true / absence-of-unsafe-hosted-findings check must follow merge.
• The competing automated PR Repin organization lock actions to v1.14.0 #738 was incompatible with the historical wrapper and created a new quarantine, reducing usable licensed capacity to one. It is closed; recovery and prevention are tracked in central #233. No recovery has been performed without the required external license evidence.

#737 now references this issue without an automatic closure keyword, so these remaining acceptance steps cannot be silently closed by merge.

[wallstop]

Additional acceptance at PR #737 head 56b153c: Unity run 34099719707 passed all modes and native smoke. The DAD smoke exported in 59s after 390s license acquisition; all ordered return/classify/release/final gates succeeded with confirmed cleanup and no incident. All 14 test artifact digests and passing-test identity comparisons passed.

Follow-up 3089701 fixes the independent ST/smoke job cancellation guards; release export implementation is unchanged. Its final CI is running. The real devcontainer Docker build and non-root Git/Fetch MCP protocol smoke also passed locally.

This issue remains open: Release Publish is still manually disabled (the attempted export-only dispatch returned HTTP422 and created no run); temporary enablement permission is pending. Release artifact bytes/sidecar verification and the post-merge default-branch enrollment audit remain outstanding. Overall Unity elapsed was 58m32s versus 52m38s baseline with one license slot quarantined; no no-increase claim is made.

[wallstop]

Post-merge enrollment evidence is now available from audit 34130206554, artifact 10021797978. Its ZIP SHA-256 matches the GitHub digest; complete=true, and the consumer snapshot is merged main 9c3689b. All 27 inventoried jobs were inspected. There are no unsafe-hosted-unity-runner findings for this repository, satisfying that specific migration acceptance item.

The audit still reports 31 other findings across release, benchmarks and tests; #322 remains open while these are classified against the exact central analyzer. A successful audit workflow is not a clean enrollment result.

Final PR #737 Unity run 34105182458 passed all nine jobs. All 14 artifact digests and all 139,830 baseline passing test occurrences were verified; final total is 140,085 passes with zero failures. Elapsed 104m53s exceeds the 52m38s baseline. Current lock state has no reservations and two live holders; merged-main run 34129823692 is already underway for another measurement. Release Publish remains manually disabled, and export-only enablement approval/package-byte acceptance are still pending.

[wallstop]

Merged-main validation is now complete: Unity run 34129823692 passed all nine jobs at 9c3689baa8ede0aa8c7780f2c54e4c10738c8584. All 14 ZIP digests and NUnit leaf full-name/status multiplicities were checked. Every one of the 139,830 baseline passing occurrences and 140,085 final-PR passing occurrences is preserved, with zero failures. Elapsed time was 39m 16s versus the 52m 38s baseline (13m 22s lower). This is an observed exact-run result, not a controlled causal speedup claim.

Follow-up #739 makes both export cleanup verdicts unconditional and terminal, retains a central cleanup verifier before release package upload, and removes the unused legacy license-return wrapper. Its separate CI is running. The hosted external-link repair already passed at its exact head.

The prior default-branch enrollment audit remains complete with zero unsafe-hosted-unity-runner findings; broader policy findings remain tracked in #322. Release Publish remains manually disabled. No temporary enablement, release dispatch, publication, license-state mutation or cancellation has occurred; export-only package-byte acceptance is still pending.

[wallstop]

Follow-up #739 is now fully green at 98efaff9127e90777b8e8fa989cc30b1e04fa6de, with no review findings. Unity run 34133512123 passed all nine jobs. Independent audits checked all 14 ZIP digests, run/commit provenance, XML counts and test identity/status multiplicities: all 139,830 baseline passes and all 140,085 merged-main passes are preserved. Results exactly match merged main: 147,489 cases, 140,085 Passed, zero Failed, 7,165 Skipped, 239 Inconclusive.

Observed elapsed was 48m 29s, 4m 09s below the original 52m 38s baseline and 9m 13s above the intervening merged-main run. Fleet occupancy differed; this supports exact-run baseline nonincrease, not a controlled causal speedup.

The native smoke job verified the changed terminal cleanup gate after redaction, with confirmed/healthy cleanup, successful lock release and no incident. The hosted link repair also passed. PR #739 remains open; this is not a default-branch landing claim. Release Publish remains manually disabled, and independent release package-byte/hash acceptance remains unverified follow-up. The broader enrollment findings remain under #322; the predicted four-finding reduction still needs a fresh default-branch audit after landing.

[wallstop]

Post-#740 default-branch enrollment evidence is now available from audit 34168370804, artifact 10034918093 (ZIP SHA-256 of the downloaded file verified against the GitHub digest; complete=true). The consumer snapshot is merged main 540c49847d0e74dff22688345f22ecadf2c527f3 — this repository's current default branch, i.e. it includes the #737/#739/#740 export-fleet migration follow-ups rather than stopping at 9c3689ba as the previous audit did.

All 27 inventoried jobs for this repository were inspected. There are zero unsafe-hosted-unity-runner findings for this repository at the current default branch, so the audit acceptance item specific to this migration ("the central audit no longer records unsafe-hosted-unity-runner for this repository") now holds against the merged post-#740 head, not just the earlier snapshot.

The audit still reports the known 27 policy findings for this repository — classifier-inputs-not-typed (2), missing-unity-aggregate (5), missing-unity-editor-check (3), missing-unity-return (2), unsafe-central-return-suffix (2), unsafe-unity-editor-provisioning (5), ineligible-unity-trigger (4), missing-runner-preflight (4) — spread across release.yml unitypackage, unity-tests.yml (unity-tests / unity-tests-single-threaded / unitypackage-smoke) and unity-benchmarks.yml. Those belong to #322's remediation scope and keep this issue's remaining acceptance unchanged:

• Release Publish is still disabled_manually; the guarded export-only validation run and its package-byte/hash acceptance remain blocked on the temporary enablement approval, and the disabled state must be restored afterward.
• One release export completing green on the fleet with artifact/hash evidence remains pending that permission.