gqa(adr): mark DDD-0060 as synced in ADR-0060 SB (EN+KO)

DDD-0060 was rewritten to the two-kernel composite-hybrid design, so SB
item 1 ('DDD not yet synced') is stale. Update EN + KO mirror to record the
DDD as synced (ADR authoritative, DDD = impl how-to). Docs only.

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

docs/adr-proposed/ADR-0060-algo-gqa-fused-attention-ahbm.md

@@ -1011,13 +1011,11 @@ design; each needs a verification pass during implementation. Recorded here
 (rather than asked) per the working agreement — the recommendation is my
 predicted default; revise on review.
 
-1. **DDD-0060 is not yet synced.** The Detailed Design Document still
-   describes the old `tl.load_async` double-buffer path and primitive
-   `tl.dot` inner loop (its §4.3/§5/§10). It must be updated to the hybrid
-   (composite GEMMs, lazy load, K pre-transposed). *Left for review*
-   because the DDD is a derived how-to and a large rewrite; the ADR is now
-   the authoritative record. **Recommend:** sync DDD as a follow-up before
-   implementation starts.
+1. **DDD-0060 synced (this revision).** The Detailed Design Document has
+   been rewritten to match the two-kernel composite-hybrid + CUBE-Group SP
+   design (file plan, placement, phase plan P1–P8, verification, risks). The
+   ADR remains the authoritative design record; the DDD is the
+   implementation how-to and points back here (and to §B) for rationale.
 
 2. **K operand orientation for the composite GEMM.** Q·Kᵀ needs `b =
    [d, TILE]`, but the KV cache stores K as `[S_rank, d]`. `tl.trans` is