@@ -127,7 +127,7 @@
   missing`); a bare model id prefixed `anthropic.`, an id already spelled for Bedrock kept; no server-side fallbacks (Bedrock offers
   none); an empty credential chain `503 AWS credential missing` by name; `llm.health` reporting `region`. `backend_for(name, client)`
   holds a route's shape, and the vector harness installs its fake under the backend a case names (66 cases). The `bedrock` extra adds
-  boto3. **Driven live 2026-10-14 (PR #44, the Node twin mercury-nodejs #112):** negative controls first, then chat, a structured
+  boto3. **Driven live 2026-10-14 (PR #44 merge `03c5f57`, the Node twin mercury-nodejs #112 merge `0ece23f`, both MERGED 2026-10-14):** negative controls first, then chat, a structured
   verdict and a progressive stream on Haiku 4.5, and the Java engine's shipped triage graph and streaming relay in front of the
   helper - all through IAM, no vendor key. What the drive taught: Bedrock has TWO SURFACES an account may be enabled for separately,
   so `llm.aws.api` selects `mantle` (the default, the Anthropic-shaped endpoint, the `anthropic.` prefix) or `runtime` (the classic
 
@@ -1,8 +1,8 @@
 - [x] **AWS Bedrock through IAM as the LLM helper's second backend. CLOSED 2026-10-14.** Built in PR #43 (merged `c25ba35`) and
   driven live the same day with Eric's temporary IAM credentials and no vendor key: negative controls first (401 and 503 by
   name), then chat, a structured verdict and a progressive stream on Haiku 4.5 through the classic runtime surface, and the Java
-  engine's shipped triage graph and streaming relay in front of the helper; PR #44 carries the surface switch `llm.aws.api`, the
-  SDK's credential wording mapped, and the report. Lesson: an account may be enabled for one Bedrock surface and one model
+  engine's shipped triage graph and streaming relay in front of the helper; PR #44 (merged `03c5f57`) carries the surface switch `llm.aws.api`,
+  the SDK's credential wording mapped, and the report. Lesson: an account may be enabled for one Bedrock surface and one model
   generation only - the gates are the per-model agreement, the one-time use case and the account's own enablement, told apart by
   `GetFoundationModelAvailability` - and the negative control is what found the mapping gap. origin: 2026-10-02-001146.
   → serves: vision-mercury-python
 
@@ -84,11 +84,12 @@ pack's `PostOffice` client (`llm.chat`, a schema call, `llm.stream`), then the J
 
 ## Context for Next Session
 
-- PR #44 (the runtime surface, the credential-error mapping and this pack's report) is OPEN awaiting Eric's merge; the Node twin
-  mercury-nodejs #112 likewise. The thread `llm-helper-bedrock-iam` is CLOSED - the live drive ran. PR #43 merged (`c25ba35`);
-  mercury-nodejs #111 merged (`def1e3a`). The pack's next release adopts the Java number it catches up to - 4.12.25 today - when Eric
-  cuts it. The thread `llm-helper-bedrock-iam` stays open for the live drive; after it, the certification report in the four
-  repositories gains a Bedrock section and the thread closes.
+- PR #44 (the runtime surface, the credential-error mapping and this pack's report) MERGED 2026-10-14 (merge `03c5f57`; the tree
+  identical to the branch head outside `memory/`; the branch deleted locally and already gone from the remote; at the one CI read
+  `ci` and `agent-memory` were green); the Node twin mercury-nodejs #112 merged the same day (`0ece23f`), as did the engines' report
+  PRs (mercury-composable #563 squash `cd708eba`, mercury #384 merge `9141cc32`). The thread `llm-helper-bedrock-iam` is CLOSED -
+  the live drive ran. PR #43 merged (`c25ba35`); mercury-nodejs #111 merged (`def1e3a`). Sprint 1 of the AI SDLC epic is on main in
+  all four repositories. The pack's next release adopts the Java number it catches up to - 4.12.25 today - when Eric cuts it.
 
 ## Memory References