Track pai-v5#1 port: record Option 3 wiring decision (LATEST→6.3.0+local) in design doc

[virtualian]

Context

Tracks the marrair-side coordination work for virtualian/pai-v5#1 (Port AskUserQuestion ENUMERATE→OFFER phase-exit gate to Algorithm v6.3.0+local).

The actual overlay files live on virtualian/pai-v5's 1-port-askuq-gate branch (cut 2026-05-11 from main). This issue covers the design-doc-side decisions and progress tracking that belong on virtualian/pai.

Decisions to capture in Plans/v5-0-0-plus-port.md

• Add wiring strategy = Option 3 (LATEST→6.3.0+local) to the "Decisions Locked" table. Rationale: closest fit to "minimise changes to v5.0.0"; v6.3.0.md stays untouched; load chain is CLAUDE.md → LATEST → v6.3.0+local.md → (Read v6.3.0.md + askuq-gate.md). Three files on the pai-v5#1 branch:

  • Releases/v5.0.0-overlay/PAI/ALGORITHM/askuq-gate.md (cherry-picked from bootstrap/v5-overlay-and-tooling)
  • Releases/v5.0.0-overlay/PAI/ALGORITHM/v6.3.0+local.md (new — load-order wrapper)
  • Releases/v5.0.0-overlay/PAI/ALGORITHM/LATEST (new — 6.3.0+local)

• Document the vX.Y.Z+local LATEST convention as a fork pattern: future fork-side Algorithm doctrine variants (e.g. when a Scope-gate addendum lands per HIGH#3 in revised list) reuse the same wrapper pattern.

• Considered alternatives (record as rejected with rationale):

  • Option 1 — Class A overlay of v6.3.0.md. Rejected: overwrites v5's main Algorithm doc; high upgrade-drift cost on every v5 release.
  • Option 2 — CLAUDE.md section-append. Rejected: requires extending Tools/deploy-overlay.sh to support CLAUDE.md merging (only does JSON merge currently); out of pai-v5#1's scope.

Progress / Status updates

• Update the design doc's "Progress / Status" section to mark pai-v5#1 overlay files as authored on branch 1-port-askuq-gate.
• After deploy + acceptance verify on marrmini, update Progress / Status to mark pai-v5#1 as ported.

Out of scope

• The overlay files themselves — those live on virtualian/pai-v5:1-port-askuq-gate.
• Deploy via bash Tools/deploy-overlay.sh on marrmini — operational, not coordination.
• Acceptance verification (AskUserQuestion fires when 2–4-option decisions exist on OPEN_CHOICES: before THINK) — happens on marrmini against the live install.

References

• Parent migration: Migration: marrair → marrmini, adopt v5.0.0 as baseline, freeze v4.0.3+ #166
• Design doc: Plans/v5-0-0-plus-port.md
• Overlay scaffold: PR Track #166 progress + audit pai-v5 overlay scaffold #171
• Port issue: virtualian/pai-v5#1
• pai-v5 branch: 1-port-askuq-gate