chore: extract road-skate to its own repo (hyperpolymath/road-skate)

road-skate is a retro driving game written in AffineScript — Accolade
Test Drive III: The Passion-inspired, with perspective road rendering
and centripetal-force steering. It belongs as a top-level repo on its
own; it was only ever in this tree because of the 2026-04-22
"Consolidate ecosystem projects into affinescript repo" commit, which
folded several independently-owned subtrees into this compiler repo by
mistake.

This PR:

* Removes the `road-skate/` subtree (368 files). Pre-extraction history
  is preserved in `hyperpolymath/road-skate` via `git subtree split`
  (commit `6715b38` there strips template `verification/proofs/` and
  rewrites the stale "AffineScript-Vite" README).

* Updates the five files that referenced the local `road-skate/` path:

  - `RSR_COMPLIANCE.adoc` — sibling-repo convention now references
    `hyperpolymath/road-skate` instead of the local subtree.
  - `docs/ECOSYSTEM.adoc` — road-skate moved from the in-tree adjunct
    row to an out-of-tree adjunct entry.
  - `docs/standards/PANIC-ATTACK.adoc` — the panic-attack tool is
    installed from crates.io (`hyperpolymath/panic-attack`), not from
    `road-skate/features/panic-attacker/` (which was a 2-file
    integration manifest with no Cargo.toml — the install never
    actually built locally).
  - `docs/standards/TESTING.adoc` — same fix on the cross-link.
  - `.github/workflows/panic-attack.yml` — drop the
    `cargo install --path road-skate/features/panic-attacker` branch;
    crates.io is the only install path now.

* Stripped `road-skate/verification/proofs/` on extraction (RSR
  template scaffolding, no real proof obligations — same precedent as
  the 2026-03-29 PROOF-NEEDS template wipe).

## Follow-up

Five more subdirectories in this repo are similarly-misplaced consolidations
from the 2026-04-22 commit and should be extracted on the same pattern:
`affinescript-dom/`, `affinescript-pixijs/`, `affinescript-tea/`,
`affinescript-vite/`, and the embedded `affinescriptiser/` (which already
has its own repo). Tracking issue to be filed once this PR lands.

`affinescript-deno-test/` stays in this tree — it's an approved Deno-test-
harness exemption per CLAUDE.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.github/workflows/panic-attack.yml

@@ -9,8 +9,8 @@
 #     open a tracking issue.
 #   - Release cuts call `just panic` manually per RELEASE.md.
 #
-# Tool: `panic-attacker` Rust crate from
-#       road-skate/features/panic-attacker. Installed via cargo.
+# Tool: `panic-attacker` Rust crate from `hyperpolymath/panic-attack`.
+#       Installed from crates.io.
 
 name: Panic-Attack (compliance scan)
 
@@ -44,19 +44,17 @@ jobs:
           toolchain: stable
 
       - name: Install panic-attacker
-        # Source-install from the estate crate. Once published to
-        # crates.io this can switch to `cargo install panic-attacker`.
+        # Installed from crates.io (the estate crate is published at
+        # `hyperpolymath/panic-attack`). The previous `road-skate/features/
+        # panic-attacker/` local-path fallback was removed when road-skate
+        # was extracted to its own repo on 2026-05-26 — that path was a
+        # 2-file integration manifest with no Cargo.toml, so the fallback
+        # never actually built locally.
         run: |
-          if [ -d road-skate/features/panic-attacker ]; then
-            cargo install --path road-skate/features/panic-attacker --locked || \
-              cargo install --path road-skate/features/panic-attacker
-          else
-            echo "::warning::road-skate/features/panic-attacker not found; trying crates.io"
-            cargo install panic-attacker || {
-              echo "::error::panic-attacker unavailable from both estate path and crates.io"
-              exit 1
-            }
-          fi
+          cargo install panic-attacker || {
+            echo "::error::panic-attacker unavailable from crates.io"
+            exit 1
+          }
 
       - name: Run panic-attack
         id: scan

RSR_COMPLIANCE.adoc

@@ -33,8 +33,8 @@ toc::[]
 |`.well-known/ai.txt`       |✅ |Estate-wide AI agent affordance metadata.
 |`.well-known/humans.txt`   |✅ |Human-readable maintainer / contributor surface.
 |`guix.scm` or `flake.nix`  |⚠️ |Neither file currently committed; the `affinescript.opam` package descriptor + the global `justfile` recipes carry the build contract today. Adding a Guix channel definition is a planned follow-up (estate primary is Guix per RSR-OUTLINE §"Language Tiers"); a Nix fallback would be acceptable for early CI.
-|`0-AI-MANIFEST.a2ml`       |✅ |Adopted 2026-05-25 (PR #359) replacing the older `AI.a2ml` per Hypatia `root_hygiene` rule. Matches sibling-repo convention (`road-skate/`, `affinescript-vite/`, `affinescriptiser/` all carry the same).
-|`STATE.scm`                |❌ |*Documented exemption.* This repo's `.scm` extension is reserved for Guix (`guix.scm`, `.guix-channel`) per the language policy in `0-AI-MANIFEST.a2ml`. Project state lives at `.machine_readable/6a2/STATE.a2ml` in the canonical 6a2 schema (matches sibling repos in the same estate). Substituting `.a2ml` for `.scm` is the cross-repo standard, not an AffineScript outlier — see also `road-skate/.machine_readable/STATE.a2ml`.
+|`0-AI-MANIFEST.a2ml`       |✅ |Adopted 2026-05-25 (PR #359) replacing the older `AI.a2ml` per Hypatia `root_hygiene` rule. Matches sibling-repo convention (`hyperpolymath/road-skate`, `affinescript-vite/`, `affinescriptiser/` all carry the same).
+|`STATE.scm`                |❌ |*Documented exemption.* This repo's `.scm` extension is reserved for Guix (`guix.scm`, `.guix-channel`) per the language policy in `0-AI-MANIFEST.a2ml`. Project state lives at `.machine_readable/6a2/STATE.a2ml` in the canonical 6a2 schema (matches sibling repos in the same estate). Substituting `.a2ml` for `.scm` is the cross-repo standard, not an AffineScript outlier — see also `hyperpolymath/road-skate`'s `.machine_readable/STATE.a2ml`.
 |`RSR_COMPLIANCE.adoc`      |✅ |This file. Added 2026-05-25.
 |===
 

docs/ECOSYSTEM.adoc

@@ -170,9 +170,15 @@ canonical `affinescript tea-bridge` + a re-entrancy fixture.
 |`affinescript-cadre` |scaffold |Was imaginary until #175. Router/navigation
 satellite (internal `lib/tea_router.ml` contract exists).
 
-|`affinescriptiser`, `road-skate` |adjunct |In-tree tooling/experiments;
+|`affinescriptiser` |adjunct |In-tree tooling/experiments;
 not part of the integration critical path.
 
+|`hyperpolymath/road-skate` (out-of-tree, 2026-05-26) |adjunct |Retro driving
+game written in AffineScript (Test Drive III-inspired). Extracted from this
+repo's `road-skate/` subtree on 2026-05-26 — see commit history of
+`hyperpolymath/road-skate` for pre-extraction lineage. Not part of the
+integration critical path.
+
 |`packages/affine-js` / `-ts` / `-res` / `-vscode` |works |
 `affine-js` SAT-02 fixed by INT-02 (#179): host-agnostic loader
 (`loader.js`) — Deno/Node/browser parity, multi-namespace import

docs/standards/PANIC-ATTACK.adoc

@@ -13,7 +13,7 @@ when the scanner runs, how findings are dispositioned, and what the
 finding-disposition vocabulary is.
 
 The estate-wide rule that mandates panic-attack lives in
-`road-skate/docs/governance/MAINTENANCE-CHECKLIST.adoc`
+`hyperpolymath/road-skate`'s `docs/governance/MAINTENANCE-CHECKLIST.adoc`
 (Axis 3 — *audit: systems > compliance > effects*).  This file is
 the AffineScript-specific instantiation of that rule.
 ====
@@ -147,23 +147,21 @@ mechanism.
 == Tool installation
 
 `panic-attack` is the `panic-attacker` Rust crate from the estate
-(`road-skate/features/panic-attacker/`).  Install:
+(`hyperpolymath/panic-attack`).  Install:
 
 [source,bash]
 ----
-cargo install --path road-skate/features/panic-attacker
-# or, from the published crate (when available):
 cargo install panic-attacker
 ----
 
-CI installs it during the weekly workflow via the same crate path.
+CI installs it during the weekly workflow via the same published crate.
 
 == Cross-references
 
 * link:TESTING.adoc[TESTING.adoc] — testing standards (this doc
   is referenced from there as the security-scan policy).
 * link:RELEASE.md[RELEASE.md] — release-cut checklist
   (pre-release panic-attack invocation).
-* `road-skate/docs/governance/MAINTENANCE-CHECKLIST.adoc` —
+* `hyperpolymath/road-skate`'s `docs/governance/MAINTENANCE-CHECKLIST.adoc` —
   estate-wide maintenance axes that mandate the scanner.
 * `panic-attack.toml` — the rule configuration this SOP enacts.

docs/standards/TESTING.adoc

@@ -199,7 +199,7 @@ and a ratchet policy.
 == Panic-attack (security scan)
 
 `panic-attack` is the estate's compliance scanner.  Per estate
-practice (`road-skate/docs/governance/MAINTENANCE-CHECKLIST.adoc`
+practice (`hyperpolymath/road-skate`'s `docs/governance/MAINTENANCE-CHECKLIST.adoc`,
 Axis 3 — *audit: systems > compliance > effects*) it runs:
 
 * On a weekly schedule