Add architectural review for reply-thread-fix

Review the reply-thread work (specifier scenarios, coder wiring, refactorer
optimistic-reply extraction). No source fixes needed. Refresh mutation and
acceptance mutation manifests from the verification runs.

By architect.

docs/reviews/reply-thread-fix-summary.md

@@ -0,0 +1,69 @@
+# Architectural Review Summary — reply-thread-fix
+
+## Task and commits reviewed
+- Task: `reply-thread-fix`
+- Reviewed the refactorer branch ending at `de24180c4d` (fast-forward merged into
+  `swarmforge-architect`), which carried:
+  - `ab84389` — specifier: reworded `reply-memo.feature` so each scenario sets up its
+    own thread-open step and added scenario 6 (comment icon opens thread with zero
+    replies) and scenario 7 (thread modal shows a reply form)
+  - `6e8dcaf` — coder: wired `ReplyThreadForm` into `PostThreadModal`, made the
+    `PostReplyCount` comment icon always clickable (so zero-reply posts open the
+    thread), passed wallet/profiles through the component tree, and added acceptance
+    handlers for the new scenarios
+  - `de24180` — refactorer: extracted the optimistic reply object construction out of
+    `ReplyThreadForm` into a pure, testable service module
+    (`src/services/optimistic-reply.js`) with unit tests
+
+## Architectural findings and fixes applied
+Reviewed UI/Core separation, dependency rule, information hiding/encapsulation, and
+local code quality.
+
+1. **UI/Core separation (good, and the heart of the refactorer's change).** The
+   optimistic-reply object shaping previously lived inline inside the React
+   `ReplyThreadForm` component, where it was untestable. The refactorer extracted it
+   into `src/services/optimistic-reply.js` — a pure `buildOptimisticReply({...})`
+   data-shaping function — with a focused unit test (`test/unit/optimistic-reply.test.js`).
+   The component now stays a thin UI adapter that calls the tested builder.
+2. **Dependency rule (good).** `optimistic-reply` depends on nothing; the UI component
+   depends inward on the service. No low-level module reaches toward IO.
+3. **Information hiding (good).** The reply object shape is a single, documented
+   function; the React form exposes only the user-facing form surface and delegates
+   submission to the already-tested `MemoReply`/`ReplyThreadPage` controllers.
+4. **Coder wiring (good).** `PostReplyCount` is now clickable whenever an `onClick`
+   handler is provided, so zero-reply posts can open the thread (matching scenario 6).
+   `PostThreadModal` holds optimistic replies in local state, cleared on hide/txid
+   change, and renders them through `PostThreadNode`.
+5. **Local code quality (good).** Small, clear modules; the extracted builder has one
+   responsibility. No duplication introduced.
+
+## Verification results
+- **Unit (`node --test`):** 89/89 pass (optimistic-reply included).
+- **Property (`node --test test/property/*.test.js`):** 13/13 pass.
+- **Acceptance (normal):** `memo-new`, `post-memo`, `set-name`, and `reply-memo`
+  (7 scenarios) generated suites all pass.
+- **Mutation (`mutate4javascript`, `--max-workers 8`, `--mutate-all`):**
+  - optimistic-reply 1/0/0, memo-action 5/0/0, memo-post 2/0/0, memo-set-name 2/0/0,
+    memo-reply 8/0/0, page-controller 7/0/0, new-post 4/0/0, set-name-page 3/0/0,
+    reply-thread-page 5/0/0, account-page 7/0/0, profiles 1/0/0.
+  - All testable core modules fully kill; no survivors, no uncovered.
+- **DRY (`dry4javascript src` and `dry4javascript test`):** no duplicate candidates
+  in either tree.
+- **Gherkin acceptance mutation (soft):** `reply-memo.feature` — 13 executed,
+  **5 killed, 8 survived**, 0 errors.
+  - Killed: byte `count` dithers and the empty-value boundary — behaviorally connected.
+  - Survived (documented equivalents): message text dithers are opaque data — any
+    non-empty value broadcasts and reflects identically.
+  - Scenarios 6/7 (plain `Scenario`s) carry no example mutations.
+
+## Suite status
+- Unit + property + acceptance all pass; source-level mutation fully kills all
+  testable core modules. Gherkin acceptance mutation survivors are documented
+  equivalents.
+
+## Handoffs sent
+- `git_handoff` → coder, refactorer (priority `00`, task `reply-thread-fix`), to
+  review the architect commit (manifest refreshes only — no source changes).
+- No handoff to the specifier: the architect produced no functional feature commit.
+
+By architect.