ci: add Heart's own pytest workflow; reframe the test-footprint rule

Heart had no PR-triggered CI: lib-tests.yml is reusable and tests the five
libraries, not Heart itself, so a logic bug in the release gate (readiness.compute,
ci_status.rollup, …) could land unnoticed. Add a minimal `Heart Tests` workflow
that runs ONLY `pytest tests/` on push/PR (3.12 + 3.13) — the gate's self-test.
It deliberately does not run any health check; those need live checkouts/network
and remain the scheduled health agent's job.

Also reframe hard-rule #4: the real invariant is a lightweight test footprint
(stdlib + PyYAML, no scientific/ML stack), a property of Heart's own suite — not
a "No JAX" claim, which wrongly implied something about the projects Heart
watches. Heart may monitor JAX or non-JAX repos; that's their concern.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BVXPU6hFTr6Ww6xhLyXcUY

Author: claude

.github/workflows/heart-tests.yml

@@ -0,0 +1,32 @@
+name: Heart Tests
+
+# Heart's own unit suite — the gate's self-test. This answers "is Heart's
+# measuring logic (readiness.compute, ci_status.rollup, the classifiers …)
+# correct?", which nothing else runs automatically: the health agent runs
+# Heart's checks *against other repos*, never Heart's own tests.
+#
+# Deliberately ONLY pytest. It must not run `pyauto-heart tick`/`readiness` or
+# any health check — those need live repo checkouts + network and are the
+# scheduled health agent's job, not a PR gate. The suite is stdlib + PyYAML
+# only, so it stays fast and flake-free.
+
+on: [push, pull_request]
+
+jobs:
+  pytest:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+      - name: Install (PyYAML core + pytest dev extra)
+        run: pip install -e ".[dev]"
+      - name: Run tests
+        run: pytest tests/ -q

CLAUDE.md

@@ -34,8 +34,13 @@ the `Brain → Heart → Hands` call chain, and `README.md` for user-facing docs
 3. **Polling must be cheap**. A full `tick` should complete in <30s
    total. If a check would take longer, run it less often (move to a
    v2 daily cron, not the watch loop).
-4. **No JAX in tests** — library convention. Heart tests run with
-   stdlib + PyYAML only.
+4. **Lightweight test footprint**. Heart's own test suite runs on the
+   standard library plus PyYAML only — no scientific/ML stack (numba,
+   matplotlib, JAX, the PyAuto libraries). This keeps the suite fast and
+   flake-free so it runs anywhere (CI, mobile, sandbox). It is a property of
+   *Heart's* tests, not a claim about the projects Heart watches — Heart may
+   perfectly well monitor non-JAX (or JAX-heavy) repos; that's their concern,
+   not the suite's.
 5. **State writes are atomic**. Use `heart.state.atomic_write_json` or
    the bash equivalent (`heart_write_json` in `_common.sh`). Concurrent
    ticks must not corrupt `state.json`.