v0.7.2 Package Runners + CI Gate

Five package-level test runners validating extension API contracts:
- notes-runner: CRUD, folders, tags, search, backlinks (12 tests)
- chat-runner: conversations, messaging, search (9 tests)
- schedules-runner: CRUD + run (5 tests)
- workflow-runner: definitions, instances, stage progression (5 tests)
- renderer-runner: registry contract, block matching (4 tests)

Runner Result API (in-memory, 3 admin endpoints) stores results
from browser runs for CI consumption. Test-runners surface v0.2.0
posts results after each run and fixes suite prefix matching.

CI integration via Playwright: wait-for-healthy.sh, run-surface-tests.sh,
surface-test-driver.js. New test-runners stage in Gitea CI pipeline.

Verified: 169 passed, 0 failed, 9 warned, 8 skipped on fresh install.
Go handler tests: 4/4 passing.

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

ci/wait-for-healthy.sh

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# ═══════════════════════════════════════════════
+# Wait for Armature server to be healthy
+# ═══════════════════════════════════════════════
+# Usage: ./ci/wait-for-healthy.sh [URL] [MAX_RETRIES]
+set -euo pipefail
+
+HOST="${1:-http://localhost:3000}"
+MAX_RETRIES="${2:-60}"
+
+echo "Waiting for ${HOST} to be healthy..."
+for i in $(seq 1 "$MAX_RETRIES"); do
+  if curl -sf "${HOST}/api/v1/auth/login" -o /dev/null 2>/dev/null; then
+    echo "Server healthy after ${i}s"
+    exit 0
+  fi
+  sleep 1
+done
+
+echo "Server not healthy after ${MAX_RETRIES}s"
+exit 1