[Jacob-Met]

Jacob's standing order (2026-10-08, hamon issue #143 comment 6067592767): no GitHub Actions - no dispatches, reruns, scheduled execution, or implicit push/PR/merge triggers.

This PR removes this repository's GitHub Actions workflow files so no workflow can trigger. File-level only: no repo or org settings changed, nothing merged by this PR. Reverting restores the files.

Reason: Jacob, 2026-10-08 19:32 UTC: "i guess no more github actions since they are charging for those i guess relay that but they can keep working just no more github actions".

[Jacob-Met]

Root review HOLD: the required license-check evidence for PR133's current composition has not been received. Leave the proposal unmerged; no license command, product/test/native execution or Actions run is authorized by this review.

Current main is bcf185fb6502f016869a6fb1507c76b06cab317d, tree 10d524f14e6010838dab08b432b272421d6f6f17; head remains 1046a7505e2a085cd6be08eaa2335f3de22ed79f. Root read all six governing originals, including the complete autonomous playbook, and bound their exact Git identities to the current complete tree. CONTRIBUTING.md (07ce652a85c16bfed220192076f22ce6d602d211) explicitly lists under Pull requests item4: run python tools/check_licenses.py. No deletion-only/workflow-only exception was found. The instruction does not require GitHub Actions specifically; CI's separate --enforce-spdx invocation is a stricter command, not interchangeable wording.

Positive history is preserved. Root read three complete current PROGRESS entries: the comparator reports the license command passing on the full1,334-leaf original plus3 additions; the offline viewer reports1,337 inherited blobs plus4 additions; navigation reports --enforce-spdx on an explicit21-file subset and expressly excludes a whole-repository scan. Those are historical source-recorded claims, not underlying process receipts received here. Their applicability to this PR's prospective current-parent tree has not been established. This is not a claim that no license checks have ever passed, nor an inference that removing YAML changes a license; static non-impact alone is not the required execution receipt or a waiver.

A separate automation question remains: root read all three current workflow bodies (10,042 bytes) and directly read historical dynamic graph run37563447087. Source received184/184 historical run records, including11 dynamic Dependabot runs, none on currentbcf185, and no dynamic Pages. Metadata has_pagesfalse. Historical dynamic execution does not prove this merge would trigger it, and YAML removal does not alone establish every mechanism disabled. The reported preview also used older firstparent2f552351, so no current-parent preservation acceptance is claimed.

The existing frozen-release/#10, native/#94, and saved-output/#97/#115/#148/#150 owners remain intact. No release/tag/DOI, bench/device/patient-data operation, hand bake-off, native rerun, PROGRESS edit, settings change, alternate access or full merge-gate acceptance occurred. Preserve the proposal for disposition when exact applicable required-check evidence and a nontriggering current composition are established.