diff --git a/docs/backlog/README.md b/docs/backlog/README.md
index ef1f206..dfe4c3c 100644
--- a/docs/backlog/README.md
+++ b/docs/backlog/README.md
@@ -50,8 +50,8 @@ for its existing violations, so every WP ends green.
 | [WP-08](WP-08-store-idiom.md) | One store idiom + machine naming + TEA MDX | 1 · FP/DDD | todo |
 | [WP-09](WP-09-pure-logic.md) | Pure-logic closure: dates + missing command specs | 1 · FP/DDD | todo |
 | [WP-10](WP-10-button-fidelity.md) | CIBG button fidelity | 2 · CIBG | todo |
-| [WP-11](WP-11-markup-fidelity.md) | CIBG markup fidelity: application-link + absent-class triage | 2 · CIBG | todo |
-| [WP-12](WP-12-datablock.md) | CIBG Datablock for application data | 2 · CIBG | todo |
+| [WP-11](WP-11-markup-fidelity.md) | CIBG markup fidelity: application-link + absent-class triage | 2 · CIBG | done |
+| [WP-12](WP-12-datablock.md) | CIBG Datablock for application data | 2 · CIBG | done |
 | [WP-13](WP-13-cibg-gap-register.md) | CIBG-gap register + hygiene + MDX | 2 · CIBG | todo |
 | [WP-14](WP-14-storybook-taxonomy.md) | Storybook taxonomy reorg + Layers MDX | 3 · Storybook | todo |
 | [WP-15](WP-15-missing-stories.md) | Missing stories: shell + brief components | 3 · Storybook | todo |
diff --git a/docs/backlog/WP-11-markup-fidelity.md b/docs/backlog/WP-11-markup-fidelity.md
index 36c7e2d..3a0fdc0 100644
--- a/docs/backlog/WP-11-markup-fidelity.md
+++ b/docs/backlog/WP-11-markup-fidelity.md
@@ -1,8 +1,15 @@
 # WP-11 — CIBG markup fidelity: application-link + absent-class triage
 
-Status: todo
+Status: done (98fd7e4)
 Phase: 2 — CIBG fidelity
 
+> Done as part of the "CIBG UI fidelity pass" (user-requested, out of order).
+> application-link now uses the real `.dashboard-block.applications li a` chain via a
+> `li[app-application-link]` attribute selector (native `<li>` child, axe-clean); the
+> invented `.application`/`.application-title` classes are gone (grep gate clean). The
+> dashboard "Mijn aanvragen" renders as the CIBG Aanvragen component. Remaining
+> absent-class triage for non-aanvragen components stays with WP-13's gap register.
+
 ## Why
 
 `application-link.component.ts` invents `.application` / `.application-title` — absent
diff --git a/docs/backlog/WP-12-datablock.md b/docs/backlog/WP-12-datablock.md
index b389a57..780ffde 100644
--- a/docs/backlog/WP-12-datablock.md
+++ b/docs/backlog/WP-12-datablock.md
@@ -1,8 +1,14 @@
 # WP-12 — CIBG Datablock for application data
 
-Status: todo
+Status: done (82fc3c4)
 Phase: 2 — CIBG fidelity
 
+> Done as part of the "CIBG UI fidelity pass" (user-requested, out of order). New
+> `app-data-block` molecule wraps `.data-block`/`.block-wrapper`; `data-row` moved to a
+> `div[app-data-row]` attribute selector so the `<dl>`'s child is a native `<div>`
+> (axe-clean — fixed a live definition-list defect). review-section folded on;
+> registration-summary + dashboard BRP block dropped `app-card` for the datablock.
+
 ## Why
 
 CIBG documents **Datablock** (designsystem.cibg.nl/componenten/datablock/) as THE way to
diff --git a/docs/backlog/WP-13-cibg-gap-register.md b/docs/backlog/WP-13-cibg-gap-register.md
index a532924..baf3d03 100644
--- a/docs/backlog/WP-13-cibg-gap-register.md
+++ b/docs/backlog/WP-13-cibg-gap-register.md
@@ -3,6 +3,17 @@
 Status: todo
 Phase: 2 — CIBG fidelity
 
+> **Correction (CIBG UI fidelity pass, b5c5d30):** this WP assumed the `upload/` suite
+> had no vendored CIBG classes and would be marked as a CIBG-gap ("Bestand-upload").
+> The vendored build actually ships a full upload vocabulary (`.file-picker-drop-area`,
+> `ul.file-list`, `.file-container`, `.file-name`/`.file-meta`, `.btn-upload`,
+> `.upload-validation`), so the suite was **reworked to wrap those classes** instead —
+> it is no longer a gap to mark. WP-13's remaining register still covers skeleton/
+> spinner, rich-text-editor, wizard-shell, confirmation, card (`.app-card`),
+> status-badge, placeholder-chip, etc. (Note: `application-link`'s non-navigating
+> `.static-row` mirrors the aanvragen card surface from tokens — a small marked-gap
+> candidate.)
+
 ## Why
 
 User decision: hand-rolled token-bridge components are allowed **only if explicitly