Fresh-sweep player-felt residuals (3582dc2) — triaged: real vs already-fixed vs false-positive

[100yenadmin]

Triage of the 3582dc2 5-persona sweep's player-felt complaints, after delivering #900/#901/#902 and de-risking the audit long-tails. The raw complaint list contained many already-fixed / false-positive items — recording the triage so they aren't re-investigated.

Fixed this pass

• Chronicle a11y overflow ([a11y][major] Chronicle floods the accessibility tree by beat 2 — Do/Declare unreachable for AT users #752) — flagged by 2-3/5 (newbie, narrative, adversarial); the Epic 0: Scaffold + OSS-reuse spike + SRD ingest #1 felt issue (action controls sliced off the a11y tree). fix(viewer): bound chronicle a11y footprint + suppress inter-beat transition meta-text (#752) #890's row-count tail didn't bound the char footprint (8 long beats ≈ 12000 chars > 9000 ariaSnapshot budget). fix(viewer): bound chronicle a11y by cumulative char budget so long beats never slice off the action controls (#752) #902 merged — added a cumulative-char budget (CHRONICLE_A11Y_CHAR_BUDGET=2800), revert-checked.
• Resource-table drift (F02-11) — dead class_features.json rage hints reconciled to the SRD-correct live table. fix(engine): reconcile Barbarian rage-uses to the single SRD-5.2 source (audit F02-11, #794) #901 merged.
• CON-HP retro (F02-6) — already landed (fix(engine): character-progression integrity cluster — ASI/feat debt, CON-HP retro, recompute-refill, resource drift, seat census (Refs #794) #856); hardening guards added. test(engine): lock F02-6 additive invariant — non-CON ASI/patch leaves max HP unchanged (#794) #900 merged.

Already fixed upstream (audit sub-findings were stale)

• F3-7 / F14-7 casting (canonical learn/prepare + cast gate + castable-affordance) → fix(engine): Spellcasting correctness P2 cluster — AoE path, all concentration-end releases, learn/prepare canonicalization, prepared discipline, innate casting (#797) #858.
• F6-6 companion heal-case → fix(engine): companion depth cluster — betrayal telegraph, camp/banter pillar, heal case, recruit XP, combat omission, quest-arc loader (F06-4/5/6/7/8/10/11) #859.
• F3-6 concentration-release (now in 5+ end-paths), F02-15 expertise default-fill grant, F14-5 travel BFS route hints, F14-11 update_character in_party pop + readable errors, F6-4 betrayal-telegraph band — all verified present at HEAD.

False-positives (verified in code — do NOT re-chase)

• "Escape silently commits long rest" (adversarial) — the RestPrepareModal HAS the correct Escape→onClose dismiss handler (screen-character.jsx:661-666, WCAG 2.1.2). Not reproduced in code.
• "Abilities tab is a dead button" (adversarial) — "abilities" is the active default tab (screen-character.jsx:33); clicking the already-active tab is correctly a no-op (setTab + render are wired at 120/261).

Genuinely open (need deliberate work)

1. Duplicate opening beat (adversarial, major) — opening DM narration appears twice. The dedup (fix(openworlds): 'building your universe' overlay can wedge full-screen 12 min on a DM cold-open error (no escape; dismiss() unwired) #405/[reliability] Duplicate opening narration — port play_codex_dm.sh record_dm_reply (engine_logged) into play.sh #720/fix(viewer): bound chronicle a11y footprint + suppress inter-beat transition meta-text (#752) #890: seq + normalized-text key + engine_logged stamp) is heavily engineered; a remaining gap needs the actual transcript (the two copies' exact text + seq + engine_logged flags) to determine viewer-dedup-gap vs DM-craft reworded-reply (SKILL.md warns a reworded reply defeats the text-dedup). Evidence: qa/ui_playtest_runs/vm2-adversarial/ @3582dc2.
2. Battle Log renders raw Markdown + leaks internal "narration" event labels (adversarial, minor) — viewer render sanitization (strip md + suppress internal event-kind labels in the player-facing log).
3. F02-7 multiclass Pact Magic ([engine-audit][P2-cluster] Character progression integrity #794, CONFIRMED) — server.py:423 still gates pact slots to len(class_levels)==1; a multiclass Warlock loses Pact Magic. Niche (multiclass), real.

Bigger deferred features (need engine field / GUI / wrapper)

• Fighting Style not displayed (veteran, optimizer) — needs a new Character.fighting_style field + a default-vs-pending-choice design (see Canon-figure-as-PC build completeness + armor inspector metadata (optimizer build-inspection gaps) #896) + viewer render.
• Equipment paper-doll — only Body + Main Hand slots; 8+ slots missing (viewer feature).
• Item inspector depth — Weapon Mastery ("Sap") unexplained, item descriptions are stubs (viewer + content).
• Beat-3 streaming stall 7+ min (narrative) — the [reliability] DM beats silently drop / hang >10min with no recovery — sabotages story personas (crit) #623/[reliability][P0] Stalled-mid-stream DM beat locks the player out with no recovery (the v1.0.4-rc2 holdout) #745 beat-stall/recovery class (wrapper/beat-driver).

[100yenadmin]

Beat-3 stall = measurement artifact, not an engine/wrapper bug. Pulled the narrative persona's actual DM beat durations from the 3582dc2 run: all beats were healthy (62s, 45s, 100s, 58s, 155s/21-turns — longest 2.5 min, none >155s, 0 errors). There was NO 7-min DM stall. Per worldos-latency-forensics, the perceived "7+ min stall" is the QA player-agent's OWN between-turn deliberation (a real human never incurs it; duration_api_ms is surface-independent). So beat reliability is sound — this complaint should NOT drive a wrapper/recovery change. (The #623 recovery infra — adaptive stuck-timeout + beat-timeout + retry + empty-narration fallback — is in place; no gap was exercised here.)