Track pai-v5#2 merged: refresh design doc with verification evidence

[virtualian]

Context

pai-v5#2 (AISTEERINGRULES @imports wiring) merged 2026-05-11 as d564990 on virtualian/pai-v5 main. Post-merge deploy + structural verification on marrmini succeeded:

• File present: ~/.claude/PAI/AISTEERINGRULES.md, 13334 bytes
• MD5 match: 567f17ccdc71a4f691aecd02ceff113a (== marrair canonical)
• @PAI/AISTEERINGRULES.md inserted at line 11 of ~/.claude/CLAUDE.md, positioned after the 5 vanilla v5 imports (lines 6-10)
• check-overlay.sh reports ok CLAUDE.md.imports
• Idempotent on re-run

Resolution

Refresh Plans/v5-0-0-plus-port.md:

• Flip pai-v5#2 row in the follow-up-issues table to MERGED with d564990 reference and verification summary.
• Mark pai-v5#7 / PR fix: bump hardcoded version in INSTALL.ts from 2.4 to 2.5 #8 (Class B-imports tooling) MERGED in the same table.
• Add issue Track pai-v5#2 merged: refresh design doc with verification evidence #177 (this issue) and PR #N to the Related issues row.
• Refresh Phase posture to reflect the post-pai-v5#2-merge state (pai-v5#1, feat(voice-server): Add config flag to disable desktop notifications #7, Diataxis skill: Role-first vs content-type-first structure mismatch #2 all live).

Out of scope

• Preamble cosmetic drift in AISTEERINGRULES.md ("settings.json -> loadAtStartup" vs @imports) — deferred until marrair migrates off loadAtStartup.
• settings.json.overlay co-mingling cleanup — design doc Decision C; separate work.

References

• Precedent: Track pai-v5#2 port: AISTEERINGRULES wiring decision (loadAtStartup vs @imports) #175 / PR Capture pai-v5#2 wiring decision: @imports for AISTEERINGRULES (#175) #176 (pai-v5#1 status flip + Decision A)
• Tooling: pai-v5#7 / PR Add Class B-imports mode for CLAUDE.md @-import merge (#7) pai-v5#8
• Implementation: pai-v5#2 / PR Port AISTEERINGRULES.md base via @imports wiring (#2) pai-v5#9
• Parent tracking: Migration: marrair → marrmini, adopt v5.0.0 as baseline, freeze v4.0.3+ #166