diff --git a/.agents/reports/planner-reviewer-claude-01/report-4d3c2c1c.md b/.agents/reports/planner-reviewer-claude-01/report-4d3c2c1c.md
new file mode 100644
index 0000000..dbe228c
--- /dev/null
+++ b/.agents/reports/planner-reviewer-claude-01/report-4d3c2c1c.md
@@ -0,0 +1,40 @@
+# 🔍 Post-Commit Cross-Review — v4.1.3 Release Packaging (Commit `85a46ef`, Job `4d3c2c1c`)
+
+- **Reviewer**: `planner-reviewer-claude-01`
+- **Target**: commit `85a46ef` — "chore(release): bump framework and 8 skills to v4.1.3" (already on `main`; no uncommitted diff to review, so this is a post-commit audit against the checklist).
+- **Method**: read the actual commit via `git show`, verified every touchpoint against live file content, ran the version-lockstep tests and the full suite myself.
+
+---
+
+## 1. 3-Way Version Lockstep
+
+- `lib.sh:32`: `MAM_VERSION="4.1.3"` — confirmed exact, single-line change, comment/export logic untouched.
+- `VERSIONS.md`: current-version header now `v4.1.3` / `2026-08-31 (KST)`; all 8 rows of the skill matrix updated to `4.1.3`; new `### 🛠️ v4.1.3` changelog section inserted correctly *above* the existing `v4.1.2` entry (chronological order preserved), with accurate C-1/C-2 bullets that match the actual code changes and cite the correct tests (`test_h26`, `test_t14`, `test_t16`, `test_t15`).
+- All 8 `SKILL.md` frontmatters (`create`, `stop`, `resume`, `status`, `monitor`, `delegate-job`, `loop`, `orc-onboard`): each diff is a clean, isolated `version: 4.1.2` → `4.1.3` line change — no other frontmatter fields touched, verified by reading every one of the 8 diff hunks directly.
+- `tests/test_version_consistency.py`: ran both `test_three_way_version_lockstep` and `test_mam_version_is_not_env_overridable` myself — **both PASS** at the new v4.1.3 state.
+
+Lockstep is fully correct and complete.
+
+## 2. Reviewer-feedback doc sync (`multi-agent-mux-resume/SKILL.md`) — one real inaccuracy found
+
+**Line 55** ("UUID resolution order" prose): correctly and accurately updated — *"If both are empty → for Class A agents (`agy`, `hermes`, `opencode`), `resume_session.sh` automatically falls back to `FRESH_SPAWN=1` (`spawn-spec`). For Class B agents (`claude`, `grok`), fall back to `multi-agent-mux-create`."* This precisely matches the real, already-verified `resume_session.sh` behavior.
+
+**Lines 71-75** (the "Workflow" section's illustrative bash snippet): here I found a genuine content inaccuracy. The added comment says *"For Class A, `resume_session.sh` handles fresh-spawn fallback automatically"* — correct — but the `echo` text right below it on the very next line was changed to:
+```
+echo "No saved session for $WORKSPACE ($AGENT). Class B agents must use multi-agent-mux-create first."
+```
+I checked the **actual, live** `resume_session.sh` error string (line 67): it is byte-for-byte unchanged from before this whole Issue #3 effort — `"ERROR: No saved session for $WORKSPACE ($AGENT). Use multi-agent-mux-create first."` — with no "Class B agents must" phrase anywhere in it (I deliberately preserved this exact string across `a9c8d6d3`/`398afb2e` specifically because Class B's contract was to stay byte-identical). The doc's illustrative snippet now shows a **fabricated error string that the real script never actually prints**.
+
+This is a pre-existing pattern of the "Workflow" section being a simplified, non-literal walkthrough (it has never had an `opencode` case arm in its `case "$AGENT" in ...` blocks, for instance, even though `opencode` is a supported agent — that gap predates this release and is out of scope here). But this specific edit *introduces* a new inaccuracy rather than just continuing the existing simplification: previously the illustrative echo text matched the real error message nearly verbatim (modulo the missing `ERROR:` prefix); now it doesn't match at all. A reader who greps for this exact string against real output, or who takes the snippet as literal, would be misled.
+
+**This is non-blocking**: it's confined to an illustrative code comment/example (not the authoritative prose above it, which is correct), doesn't affect any runtime behavior, and doesn't touch the 3-way lockstep contract. Recommend a follow-up one-line fix: either revert the echo text to the real script's exact string, or make the whole `if [ -z "$UUID" ]` block in the example actually branch on agent class (mirroring the real script) instead of adding a claim the flat example doesn't back up.
+
+## 3. Full regression sweep
+
+Ran myself at the current `HEAD` (post-`85a46ef`): **455 passed, 0 failed**, 12m31s. `git status` clean (no uncommitted drift).
+
+## 4. Verdict
+
+The 3-way version lockstep is fully correct and test-verified; the changelog is accurate; the primary documentation-sync requirement (line 55) is correct. One non-blocking documentation inaccuracy found and specifically located (lines 71-75's example error text doesn't match the real script's preserved error string) — recommend a small follow-up fix, but it does not affect release correctness, runtime behavior, or the lockstep contract this commit was packaging. No lint/functional defects in the actual shipped code or version files.
+
+[VERDICT: PASS]
diff --git a/.agents/reports/reviewer-creator-grok-01/report-1acf4fb0.md b/.agents/reports/reviewer-creator-grok-01/report-1acf4fb0.md
new file mode 100644
index 0000000..7179268
--- /dev/null
+++ b/.agents/reports/reviewer-creator-grok-01/report-1acf4fb0.md
@@ -0,0 +1,39 @@
+# Post-commit review: v4.1.3 3-way lockstep (`85a46ef`)
+
+- **Reviewer**: `reviewer-creator-grok-01`
+- **Job**: `1acf4fb0`
+- **Commit**: `85a46ef chore(release): bump framework and 8 skills to v4.1.3 (PATCH — herdr daemon isolation & Class A 0-turn resume reliability fixes)`
+- **Working tree vs that bump**: subsequent `4b2f703` is docs-only report archive; live lockstep files match `85a46ef`.
+
+---
+
+## 1. 3-way lockstep
+
+| Surface | Live |
+|---|---|
+| `lib.sh:32` | `MAM_VERSION="4.1.3"` |
+| `VERSIONS.md` header | `v4.1.3`, date **2026-08-31** |
+| Line 21 prose | `v4.1.3으로 동기화되어 배포됩니다.` |
+| 8-row matrix | all `` `4.1.3` `` |
+| Changelog | `### 🛠️ \`v4.1.3\` — Herdr Daemon Isolation & Class A 0-Turn Resume…` (C-1 setsid, C-2 FRESH_SPAWN + epoch; Class B hatch/`test_t8`/`test_t15` named). `v4.1.2` section preserved. |
+| 8× `SKILL.md` `version:` | all `4.1.3` |
+
+`pytest tests/test_version_consistency.py -v` → **2 passed** (`test_three_way_version_lockstep`, `test_mam_version_is_not_env_overridable`).
+
+No leftover `4.1.2` on current-facing lockstep surfaces (only the historical `### v4.1.2` changelog header).
+
+## 2. Resume `SKILL.md` body (ec2e02e2 nit)
+
+- **Line 55:** Class A empty UUID → `FRESH_SPAWN=1` / `spawn-spec`; Class B → `multi-agent-mux-create`. Matches `resume_session.sh`. **Met.**
+- **Lines 71–74:** comment states Class A is handled inside `resume_session.sh`; the **example still `exit 1` for every empty UUID**. Copy-pasting the Workflow block would not reproduce Class A fallback. Residual docs nit, not a lockstep failure.
+
+## Residual nits (do not block)
+
+- Workflow snippet 71–74 still unconditional `exit 1` (see above).
+- Pitfall “Don't resume if the session is brand new and empty” (line 123) is slightly stale vs Class A 0-turn resume.
+
+No `[ESCALATE: PLANNER]`.
+
+---
+
+[VERDICT: PASS]
diff --git a/.agents/reports/reviewer-opencode-01/report-cb91f486.md b/.agents/reports/reviewer-opencode-01/report-cb91f486.md
new file mode 100644
index 0000000..3bbc898
--- /dev/null
+++ b/.agents/reports/reviewer-opencode-01/report-cb91f486.md
@@ -0,0 +1,50 @@
+# 🔍 Post-Commit Cross-Review: v4.1.3 Release Packaging Commit 85a46ef (Job cb91f486)
+
+- **Reviewer**: `reviewer-opencode-01` (role: reviewer)
+- **Target**: Commit `85a46ef` — `chore(release): bump framework and 8 skills to v4.1.3 (PATCH — herdr daemon isolation & Class A 0-turn resume reliability fixes)` — plus the follow-up archive commit `4b2f703`. Brief correctly states "(no changes since base commit)": the work is landed; this is a post-commit audit.
+- **Method**: Every checklist item verified by me directly against the committed state — lockstep surfaces, version-consistency tests, reviewer-feedback integration (my own two nits from `71a1b000` were on the record), stray-literal sweep, and behavioral regression run.
+
+---
+
+## 1. Checklist item 1 — 3-Way Version Lockstep: ALL VERIFIED
+
+| Surface | Committed state | My check |
+|---|---|---|
+| `lib.sh` MAM_VERSION | `"4.1.3"` | **Line 32** — exactly where the assessment *should* have cited it (my prior nit); the packaging commit edited the correct line |
+| `VERSIONS.md` header | `v4.1.3`, date `2026-08-31 (KST)` | Verified |
+| `VERSIONS.md` prose (line 21) | `v4.1.3`으로 동기화되어 배포 | Verified |
+| `VERSIONS.md` matrix | all 8 rows `4.1.3` | Verified |
+| `VERSIONS.md` changelog | new `### 🛠️ v4.1.3 — Herdr Daemon Isolation & Class A 0-Turn Resume Reliability Fixes (2026-08-31)` with C-1/C-2 entries | Verified — content matches the pre-agreed draft (assessment §5) and the actual commits: `test_h26`/`test_t14`/`test_t16`/`test_t15` names, Class B preservation statement, 455-test milestone |
+| 8× `SKILL.md` frontmatter | all `version: 4.1.3` (create, stop, resume, status, monitor, delegate-job, loop, orc-onboard) | Verified |
+| `test_version_consistency.py` | **2 passed** (lockstep + env-override guard), my own run | Verified |
+| Stray `4.1.2` literals | none in skills/tests/VERSIONS.md outside historical changelog sections | Verified |
+| Regression | `test_version_consistency.py` + `test_uuid_target.py`: **17 passed** (my own run); full-suite 455/455 was verified by me in `8bffb70b` and no test files changed since | Verified |
+
+The v4.1.2 changelog section is preserved intact — no historical 유실.
+
+## 2. Checklist item 2 — Reviewer-feedback integration: BOTH NITS ADDRESSED
+
+My `71a1b000` review (convergent with Grok's `ec2e02e2`) flagged two items for the packaging job. Both were carried into `85a46ef`'s resume SKILL.md edit:
+
+1. **Line 55 body-text sync** — DONE: "If both are empty → for Class A agents (`agy`, `hermes`, `opencode`), `resume_session.sh` automatically falls back to `FRESH_SPAWN=1` (`spawn-spec`). For Class B agents (`claude`, `grok`), fall back to `multi-agent-mux-create`." — accurately describes the shipped behavior (matches the code I verified in `8bffb70b`, gated by the `agy|hermes|opencode` case arm).
+2. **Workflow example (lines 71–74)** — PARTIALLY DONE: the comment now says "For Class A, resume_session.sh handles fresh-spawn fallback automatically" and the error message is reworded for Class B, but the example's caller-side `exit 1` still aborts for *all* agents including Class A — for a Class A caller the correct guidance is to just proceed to `resume_session.sh`. Grok (`1acf4fb0`) flagged the same residual. **Non-blocking**: the normative text (line 55) is correct; the example is illustrative, its comment points the right way, and a caller following the actual skill command (`resume_session.sh` directly) never executes this snippet. Recommend a follow-up docs polish to make the example branch on agent class.
+
+## 3. Process integrity
+
+- The assessment → consensus → packaging sequence was honored: assessment (no mutations, `6c24ddd0`), three reviewer opinions (Claude `39439652` PASS, Grok `ec2e02e2` PASS, my `71a1b000` PASS/concur — all archived byte-identical in `4b2f703`, I verified my own archived copy matches my job artifact), then the atomic bump.
+- Commit scope is exactly the 10 version surfaces + the resume SKILL.md body sync — no code drift smuggled into the release commit.
+- Claude's `39439652` (assessment review) completed **PASS** — the consensus was genuinely 3/3 before packaging.
+- Peer verdicts on `85a46ef` itself: Grok `1acf4fb0` **PASS** (same L71-74 nit), agy `47539988` **PASS**; Claude `4d3c2c1c` running at my report time.
+
+## 4. Residual notes (non-blocking)
+
+- The L71-74 example nit (§2.2) — one-line docs polish for a future commit.
+- SemVer classification (v4.1.3 PATCH) was established by the 3/3 consensus round and the commit message correctly labels it PATCH.
+
+---
+
+## 5. Verdict
+
+The v4.1.3 release packaging commit is complete and correct: strict 3-way lockstep holds (verified surface-by-surface plus the version-consistency tests), the changelog accurately documents the two Issue #3 fixes with correct test citations and Class B preservation, both reviewer nits from the consensus round were addressed in the packaging (line 55 fully; example partially with a benign residual), no stray literals or unauthorized changes exist, and the regression suite is green in my own runs. The consensus trail (assessment → 3/3 reviewer PASS → atomic bump → archive) is honest end-to-end.
+
+[VERDICT: PASS]
\ No newline at end of file