docs: task 15d attempt 3, the block interfaces are ready

Task 10b landed the Localized props that attempt 2 stopped on. Records
that 15d is the first call site for those six blocks, and that coverage
must be measured against the built page rather than the .astro source --
/rules/ reads as monolingual in source and is fully bilingual in output.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

plans/astro-refactor/task-15d-page-full-guide.md

@@ -224,3 +224,26 @@ block — do not work around it by duplicating the block.
 - [ ] No `.pt` reads added to the nine selector detail panels
 - [ ] Gate green, 42 assertions, `verify.mjs` untouched
 - [ ] Report lists any `translations.pt` selector you could not place, and why
+
+## Attempt 3: the blocker is cleared
+
+Task 10b landed. `FleetDiagram`, `HandoffTable`, `PhasePanel`, `RouteTable`,
+`SkillPackage` and `WorktreeMap` now accept `Localized = { en, pt }` on every
+prose prop and emit the `data-language-content` pair themselves. Passing a plain
+`string` still renders exactly what it rendered before, so nothing you already
+wrote has to change shape — you pass `{ en, pt }` where you passed a string.
+
+You are the first call site for those six blocks. No merged page uses them, so
+if a prop is wrong you will be the one to find it. Report anything that does not
+fit rather than working around it.
+
+**The measurement.** 17 of the 102 `translations.pt` entries currently reach the
+built page. Verify against `dist/full-guide/index.html`, not against the
+`.astro` source — `/rules/` looks monolingual in source and is fully bilingual
+in output, because the strings arrive through a content collection. Checking the
+source is how you get a wrong answer here.
+
+For each of the 102 entries: the selector tells you which element, the value is
+the Portuguese, and `full-guide/index.html` has the English. Both verbatim.
+
+Remaining done-when boxes are the ones in the previous section, unchanged.