docs(adr): update 002/003/005 with vertical-refactor notes; supersede 004

docs/decisions/adr-002-di-framework.md

@@ -24,3 +24,7 @@ InversifyJS with symbol-based resolution + targeted agent documentation.
 - Requires reflect-metadata + decorator config in tsconfig
 - Symbol indirection harder to trace than plain functions
 - Extra dependency (inversify + reflect-metadata)
+
+## Update (2026-05-04)
+
+The vertical-feature refactor preserved InversifyJS but moved from a single shared container in `packages/core/src/di/` to **per-feature containers** in each feature package (`packages/<feature>/src/di/container.ts`). See ADR-008.

docs/decisions/adr-003-cms-separation.md

@@ -25,3 +25,11 @@ apps/cms → @repo/cms-core → @repo/core/application (hooks)
 ```
 
 No cycles because cms-client never imports from cms-core or core.
+
+## Status: Partially superseded by v2 (2026-05-04)
+
+v1 advocated `@repo/cms-core` as a single CMS package. v2 splits this into:
+- `@repo/core-cms` — composition only (assembles feature CMS schemas)
+- Each feature owns its own collections/globals under `packages/<feature>/src/integrations/cms/`
+
+Rationale: vertical-feature ownership scales better; CMS schema lives with the business code that needs it. See ADR-006.

docs/decisions/adr-004-dual-mode-client.md

@@ -16,3 +16,7 @@ Apps need to access Payload CMS data. Payload 3.x offers both Local API (direct)
 - **HTTP mode (fallback):** REST API for external consumers without access to a Payload process.
 - Payload instance is injected at app startup, not imported — keeps cms-client standalone.
 - Both modes share the same `PayloadClient` interface — consumers don't know which mode is active.
+
+## Status: Superseded by ADR-007 (2026-05-04)
+
+The dual-mode client wrapper was deleted. Feature payload-backed repositories now call `getPayload({ config })` directly with the assembled config injected via constructor. See ADR-007 for rationale.

docs/decisions/adr-005-atomic-design.md

@@ -18,3 +18,7 @@ Atomic Design (atoms/molecules/organisms/templates) + shadcn/ui + Storybook.
 - shadcn/ui provides excellent base atoms that map naturally to atomic levels
 - Storybook sidebar mirrors the hierarchy via story titles
 - Pages live in apps (not UI package) — they connect to real data
+
+## Update (2026-05-04)
+
+Atomic Design now applies to `@repo/core-ui/` only — generic primitives (atoms, molecules, generic organisms, templates). Feature-specific components (e.g., `ArticleCard`, `HeaderNavMenu`) live in the owning feature's `ui/` folder per the vertical-feature architecture. See ADR-006.