docs(qa): prepare post-August-2 human acceptance sheet (#204)

[AnnieScigliano]

docs(qa): prepare post-August-2 human acceptance sheet (#204)

Part of #204 — this PR does not close #204. The human acceptance battery remains honestly NOT EXECUTED.

What ships

One dated, additive document: docs/ops/rehearsals/2026-08-06-post-aug2-human-qa.md.

It consumes docs/ops/WEEKEND_REHEARSAL.md as the canonical protocol (entry gate, role discipline, synthetic identities, device minimums, rehearsal sequence — all unchanged) and adds only what landed after the August 2 event:

• Contributions NAMED/ANONYMOUS (PR feat(chat): CHAT-01 contract and backend — session contributions (#137, PR A) #161, feat(chat): CHAT-01 UI — session contributions panel and staff drawer (#141, PR B) #187; hardening 671cde8; E2E fixes PR fix(e2e): correct chat fixture and Firefox media probe #192): named vs anonymous audience truth, staff attribution with badge, Enter-does-not-publish, draft preservation, new-messages indicator, media-probe remount guards.
• SessionGuidance (PR feat(ux): UX-COPY-01 — listening guidance: question, volume, balance, camera/mic (#142) #206): ES/EN comprehension rows for the listening guide, pre-room availability, remount guard.
• Second-session A→B leakage check and end-of-session token denial rows.

Candidate vs deployed (refreshed 2026-08-07, after the LOGOS release)

origin/main	aec2632
origin/release = deployed (/api/health gitSha)	64634e94f21a0a0d60d0f5745c159fe224f2895b
Database schema (deployed)	20260806233000_add_logos_private_session
Branch comparison	rev-list --left-right --count origin/release...origin/main → 2 21 — divergent branches: LOGOS was integrated separately on each (release via PR #209, main via PR #208), so this is not "main 21 ahead"

The new release 64634e9 adds the private LOGOS session. Ancestry probes against it (git merge-base --is-ancestor <sha> 64634e94f…, exit 1 = "not contained"):

• 89f77991 (PR feat(chat): CHAT-01 contract and backend — session contributions (#137, PR A) #161 contributions backend) → exit 0, contained.
• 388fe8f (PR feat(chat): CHAT-01 UI — session contributions panel and staff drawer (#141, PR B) #187 attendee/staff UI) → exit 1.
• 671cde8 (final hardening) → exit 1.
• d547e96 (PR fix(e2e): correct chat fixture and Firefox media probe #192 E2E fixes) → exit 1.
• 341c15c (PR feat(ux): UX-COPY-01 — listening guidance: question, volume, balance, camera/mic (#142) #206 SessionGuidance) → exit 1.

Production still contains only the contributions contract/backend; the chat UI, its hardening/fixes and SessionGuidance are not deployed. The fail-closed rule therefore keeps every row BLOCKED until /api/health shows a candidate explicitly containing #187 + #192 + #206. The battery remains NOT EXECUTED.

Sheet properties

• Status: PREPARED — NOT EXECUTED; Decision: PENDING DEPLOYED SHA + HUMAN EXECUTION.
• 34 journey rows with ID, precondition, action, expected/observed, PASS/FAIL/BLOCKED/NOT RUN, severity, evidence and issue columns — all NOT RUN, nothing simulated.
• Synthetic role codes only; no names, emails, tickets, tokens or real data anywhere.
• Severity P0–P3 and abort conditions; scope separation (PERF-01 — Generador reproducible de carga dual-LiveKit y seis publishers #99, WS6-01 — Prove Ticket Tailor + PayPal through the Argentine bank #25/WS6-02 — Configure the two capped events, ticket tiers, and attendee terms #26/INT-00 — Permanent registration → payment → Beacon access integration #81, CHAT-02 — Moderación, retención y retiro #134, RTC-02 — Mezcla compartida dirigida por facilitación con handoff suave #98 — exists, OPEN, unimplemented, audio-touching with explicit acoustic approval required, RTC-04 — Preflight de micrófono y selección de dispositivos #126, RTC-03 — Retorno de audio receive-only para staff #131, EarlyBirds, sales/deploy) made explicit.
• Closure requires human evidence, go/no-go signature, and linking from WS5-03 — Run capacity test, full dress rehearsal, and production freeze #24, UX-00 — Build Harmonic Beacon as a room entered, not an app used #64, UX-02 — Define capabilities and add FACILITATOR_OP safely #66, UX-06 — Build typed, persistent ES/EN localization #68, UX-09 — Establish browser, accessibility, visual, and media-continuity quality gates #69, [MVP-07][Nico+Codex] Validación mínima de audio multidispositivo #94.

Dependencies before execution

1. Deploy of a candidate containing PRs feat(chat): CHAT-01 UI — session contributions panel and staff drawer (#141, PR B) #187, fix(e2e): correct chat fixture and Firefox media probe #192 and feat(ux): UX-COPY-01 — listening guidance: question, volume, balance, camera/mic (#142) #206 visible in /api/health, with rollback SHA recorded.
2. Hidden isTest=true session derived from the canonical catalog/cockpit + synthetic COMP tickets via Admission.
3. Real humans filling every role (facilitator, independent operator, 4 attendee devices, evidence recorder).

Risks

None to production: docs-only. The only risk is process — someone treating the prepared sheet as executed; the sheet guards against this with the status banner, the fail-closed rule and the "silence is not approval" declaration.

Rollback

Revert this single document.

Verification

• Diff: exactly one new file under docs/ops/rehearsals/; branch rebased onto origin/main (aec2632) to avoid stale evidence.
• Links checked against the repo: ../WEEKEND_REHEARSAL.md, ../../verification/HUMAN_ROLE_LANGUAGE_REVIEW.md, ../../verification/2026-08-04-quality-rubric.md all resolve.
• No secrets, no personal data, no productive code, no workflow/snapshot/E2E changes. EarlyBirds (PR draft: build isolated Founding Listener candidate #203) untouched and confirmed non-colliding.

Also in this delivery (administrative, outside the diff)

• CHAT-01 — Feed público y envío con anonimato por mensaje #137 reconciled and closed as Completed with criterion-by-criterion evidence (PRs feat(chat): CHAT-01 contract and backend — session contributions (#137, PR A) #161/feat(chat): CHAT-01 UI — session contributions panel and staff drawer (#141, PR B) #187/fix(e2e): correct chat fixture and Firefox media probe #192, 671cde8, CHAT-UI-01 — Superficie frontend de preguntas y emociones #141 Done). Moderation/withdrawal explicitly deferred to CHAT-02 — Moderación, retención y retiro #134; epic CHAT-00 — Preguntas y emociones durante la sesión #127 stays open. Board already shows CHAT-01 — Feed público y envío con anonimato por mensaje #137 Done / HUMAN-QA-02 — Regresión humana integral posterior al evento del 2 de agosto #204 In Progress.

Review requested from @nicoechaniz — factual corrections from the previous review round are applied (#98 exists and is OPEN; deploy evidence refreshed after PRs #208/#209).

[nicoechaniz]

Un único bloqueo factual antes de mergear: en docs/ops/rehearsals/2026-08-06-post-aug2-human-qa.md:187 dice que #98 does not exist. #98 sí existe y está OPEN: RTC-02 — Mezcla compartida dirigida por facilitación con handoff suave. La separación de alcance es correcta, pero debería decir que esta batería no ejecuta ni certifica #98 (y que continúa bajo audio-touching/aprobación acústica), no que la tarjeta no existe. Verifiqué el resto de la evidencia candidata/deploy: 0 19 y las cinco pruebas de ancestry coinciden; la PR es docs-only, main es ancestro limpio y no colisiona con EarlyBirds. Con esa línea corregida, no veo otro bloqueo.

[AnnieScigliano]

@nicoechaniz corregido en 1450bbb — línea de scope separation (antes línea 187 del documento, ahora §8 bullet 3):

It does not execute or certify the facilitation-driven shared mix override: #98 (RTC-02) exists and remains OPEN and unimplemented; that work stays under audio-touching governance and requires explicit acoustic approval. No interface copy claims the override exists.

La separación de alcance quedó intacta: la batería no ejecuta ni certifica #98. Ninguna otra parte del documento cambió (filas NOT RUN, fail-closed, roles y estados sin tocar). Solicito re-review. 🙏

[nicoechaniz]

Re-review sobre 1450bbb: la corrección describe correctamente #98 como OPEN/unimplemented y conserva la separación audio-touching. Verifiqué el documento final, la evidencia de ancestry/deploy corregida, los links relativos, el estado PREPARED — NOT EXECUTED y el alcance docs-only. Los tres checks están verdes y no hay colisión con la línea Listener. No veo bloqueos restantes para merge.

[AnnieScigliano]

@nicoechaniz evidencia factual refrescada después de las PRs #208/#209 (release LOGOS) — commit 0ef8a8a:

• Deployed ahora 64634e94f… (= origin/release), schema 20260806233000_add_logos_private_session.
• Probes re-ejecutados contra el nuevo SHA: feat(chat): CHAT-01 contract and backend — session contributions (#137, PR A) #161 backend exit 0; feat(chat): CHAT-01 UI — session contributions panel and staff drawer (#141, PR B) #187, 671cde8, fix(e2e): correct chat fixture and Firefox media probe #192 y feat(ux): UX-COPY-01 — listening guidance: question, volume, balance, camera/mic (#142) #206 todos exit 1 — la conclusión operativa no cambia (batería BLOCKED, filas NOT RUN).
• La comparación 2 21 quedó explicada como divergencia con commits propios de LOGOS en cada rama, no como "main 21 adelante".
• Rama rebaseada sobre origin/main (aec2632); el diff sigue siendo un solo archivo nuevo.
• La corrección de RTC-02 — Mezcla compartida dirigida por facilitación con handoff suave #98 de la ronda anterior queda intacta.

Solicito re-review. 🙏

[AnnieScigliano]

Gracias por la aprobación, @nicoechaniz. Nota de trazabilidad: la review quedó asociada a 1450bbb; el head actual es 0ef8a8a después del refresh factual por #208/#209 y el rebase sobre main@aec2632. El diff continúa siendo docs-only y los checks del head están verdes. ¿Confirmás aprobación del head actual para merge?