diff --git a/.serena/memories/CI-01-ACTIONS.md b/.serena/memories/CI-01-ACTIONS.md
index a5fdd77..a3918f0 100644
--- a/.serena/memories/CI-01-ACTIONS.md
+++ b/.serena/memories/CI-01-ACTIONS.md
@@ -1,6 +1,6 @@
 <!-- Memory Metadata
-Last updated: 2026-05-22
-Last verified: 2026-05-22
+Last updated: 2026-08-10
+Last verified: 2026-08-10
 Last commit: d93a558050d54a80e578035d0e1627385ec7c1e4 test(runtime): stabilize opencode debug resolve smoke
 Scope: GitHub Actions and local CI policy
 Area: CI
@@ -16,14 +16,17 @@ GitHub Actions and local CI policy
 - `path:README.md`
 
 ## Last verified
-- date: 2026-05-22
+- date: 2026-08-10
 - commit: `d93a558050d54a80e578035d0e1627385ec7c1e4`
 - checked by: Codex ry-start memory taxonomy sync
 
 ## Facts
+- Every caller of a `ci-workflows` reusable that exposes a `runner` input passes `runner: ubuntu-latest` explicitly. This repository is public, so `pull_request` executes untrusted fork code; the reusable's `runner` default is a property of the **pinned commit**, and on current ci-workflows main 39 of 46 reusables default it to the estate's self-hosted `amsterdam` label. At the pin in use the default is still `ubuntu-latest`, so the explicit value is currently a no-op and becomes load-bearing at the next pin bump. On any pin bump, diff `inputs.runner.default` between the old and new commit.
+- `ci-workflows` enforces the same rule for its own self-calls and its published examples, but nothing extends it to external consumers, so the constraint lives in this repository's `AGENTS.md` and `.claude/CLAUDE.md`.
 - CI memories record which checks prove repository integrity and which checks are intentionally lightweight.
 
 ## Evidence
+- `commit:11d5587` explicit hosted runner in ci-workflows callers
 - `commit:d93a558050d54a80e578035d0e1627385ec7c1e4`
 - `path:.github/workflows`
 - `path:README.md`