chore: record pre-existing uncommitted repository state

Snapshot of the in-flight state that already existed, identically, in both
this worktree and the main checkout before this session began: the initial
HTTP Client platform implementation (previously untracked), the redis-lab
removal, and the JPA / object-storage / notification integration work.

Kept separate from this session's HTTP Client review response, which lands
in the following commit, so the two bodies of work stay reviewable apart.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -22,7 +22,8 @@ If this summary drifts from `AGENTS.md`, `AGENTS.md` wins and this summary must
 ## Gradle policy authorities
 
 - `src/config/architecture/modules.json`: exactly 19 leaf identities, repository-relative source
-  paths, Gradle paths, and allowed production project dependency edges.
+  paths, Gradle paths, allowed production project dependency edges, and the exact runtime
+  memberships of both composition roots.
 - `src/settings.gradle`: fail-closed registry validation, project inclusion, and directory mapping.
 - `src/build.gradle`: `verifyCleanArchitectureDependencies` and the other architecture-wide
   verification tasks.
@@ -57,7 +58,7 @@ families; the nearest `src/**/CLAUDE.md` owns local rules.
 | `app-bootstrap` | Spring Boot entrypoint and composition root | registered runtime leaves |
 
 Never infer an individual leaf's Gradle path, allowed dependency, or test command from this table.
-Read its `gradle_path` and `allowed_dependencies` from
+Read its `gradle_path`, `allowed_dependencies`, and `runtime_memberships` from
 `src/config/architecture/modules.json`; derive the focused test from that Gradle path.
 
 ## Layer workflow