Implement Gitea Actions runner substrate

docs/ci-runner-actions-gitops-ownership.md

@@ -1,6 +1,6 @@
 # CI Runner, Actions, And GitOps Ownership
 
-Last reviewed: 2026-06-05
+Last reviewed: 2026-06-07
 
 Status: contract v1. This document defines ownership and handoffs only; it
 does not authorize a live runner deployment, credential change, GitOps controller
@@ -161,10 +161,25 @@ should provide:
 - representative cluster dry-run evidence for cluster-access labels;
 - a rollback or disable path for a bad runner registration.
 
+## Current Implementation Surface
+
+`docs/gitea-actions-runner-substrate.md` defines the first supported Gitea
+Actions runner model, the initial haskelseed compatibility labels, the attended
+registration path, and recovery steps. `make runner-status` provides the
+read-only probe entry point, and `.gitea/workflows/forge-runner-smoke.yaml`
+provides the first non-production proof workflow.
+
+The first compatibility labels are `self-hosted` and `haskelseed`, matching the
+inter-hub blocker. New workflow consumers should prefer semantic labels such as
+`linux`, `container-build`, and `registry-publish` once smoke evidence is
+recorded.
+
 ## Open Follow-Ups
 
 - `docs/observability-operating-evidence.md` defines the runner health and
   artifact evidence signals that consumers may cite.
+- `docs/gitea-actions-runner-evidence.md` records the current runner inventory,
+  smoke evidence, and inter-hub unblock evidence.
 - WP-0006-T09 should declare runner substrate, label contracts, and evidence
   edges in Railiance Fabric.
 - `RAILIANCE-WP-0005-T05` should document app-side dry-run behavior once forge