Mark phase-2 localization storage implemented; list chunks.py in AGENTS.md

docs/localization.md

@@ -6,7 +6,7 @@ parameter or the `Accept-Language` header.
 - **Phase 1 (implemented):** negotiation, URL scheme, caching, rendering
   plumbing. Translations are consumed through a stub interface; the database
   still holds only the original language.
-- **Phase 2 (final plan):** gettext-style fragment storage in the
+- **Phase 2 (implemented):** gettext-style fragment storage in the
   database — machine-translated chunks plus user override patches, assembled
   at render time. Storage details in `docs/migrate.md`.
 
@@ -66,7 +66,7 @@ Region tags normalize to their base subtag (`fi-FI` → `fi`).
 - The markdown typographer (SmartyPants) is English-centric; per-language
   typographer options are a possible follow-up, not blocking.
 
-## Phase 2: fragment-based translation storage (draft)
+## Phase 2: fragment-based translation storage (implemented)
 
 Phase 1 assumed whole-page translated Markdown delivered from outside. The
 refined model is gettext-style: an article has **one primary version** (its
@@ -170,7 +170,7 @@ Full storage design and the `migrate_v3` restructuring live in
 - Article paths are stored and keyed **without leading slashes**
   (`"docs/setup"`, front page `""`); slashes are added only in hrefs.
 
-### Render pipeline (replaces the phase-1 `get_translation` stub)
+### Render pipeline (the phase-1 `get_translation` stub, now real)
 
 ```python
 def get_translation(path, lang, data) -> Translation | None: