During the existing public pre-plan opportunity, the holder can discard canonical unreserved Sapho to become aggressor before their readiness or any binding plan/Voice/inspection/Truthtrance commitment. Unchosen preparation prompts remain available. No new confirmation-only or holder-dependent response window is introduced. Later intervention and its allocation/privacy protocol remain unfinished. A battle/turn/revision-bound history and independent event list preserve accepted priority while keeping attacker, defender and chooser stable. Legitimately recovered cards can change priority again at a fresh event. Reads, actions and normalization reject corrupt histories/custody. Shared tie priority respects Habbanya in either physical slot and reaches pre-commit Stone/Voice checks, public views, bot calculations and actual ordinary/Stone resolution. The final quote previously assumed original attacker priority and now consumes the validated aggressor. Harkonnen capture still follows actual winner/loser. Owner controls, public aggressor/tie text, automatic notices and internal guidance are connected. Focused tests exercise actual tied results in Basic/Advanced, both Habbanya sides, mixed-force Stone finishability before opposing commitments, a real allied Prescience boundary, stale/late/cross-owner rejection, private rival noninterference, receipt corruption, saved recovered-card revision, actual policies at all four AI levels and authenticated SQLite races/seat restoration. Independent review found no material defect. A prior scheduling test now explicitly readies its human holder to save the card instead of allowing the new legal AI play. Types, lint and 4866 offline tests, production build and 43 HTTP/session tests pass on the unchanged source fingerprint below. Two genuine CHOAM/Richese samples completed with 1279 accepted actions, 34 periodic JSON restores and no rejected candidates. One movement Sapho play occurred; neither sample used aggressor. Targeted tests and browser evidence, not those samples, establish the new effect. Full expansion and module acceptance remain incomplete. In a new isolated browser room, genuine Advanced faction setup was followed by conserved battle staging. The human Guild used the actual aggressor button, restored the spent card and priority after refresh, readied, selected Master Bewt with zero dial/support, and declined a Traitor call. The staged Emperor opponent used real engine ready/plan/vote actions with Caid and zero dial/support. Guild won the 3-3 tie, retained four forces and 30 spice, and Emperor lost four forces. Final refresh and private JSON views restored the same outcome; the original seat row is unchanged. Screenshot capture timed out, so visual screenshot acceptance is not claimed. All 1072 original games and original seat/recovery/entry/handover records are unchanged; 1106 rooms remain including isolated QA and HTTP fixtures. SQLite quick-check and foreign keys pass. The healthy server was reused without reset/restart or automation. The Mirror audit now records why every genuine CHOAM/Richese setup includes unresolved copy candidates: an ordinary-copy-only gate would need hidden eligibility or altered inventory. Mirror stays gated pending the existing disposal ruling and copied-choice work. No mode/publication gate is opened. Verified source tree: 2fb3160efd713a3f7068aedb474868ba6863bccc420848a56e69e1df1d84441b
3.7 KiB
Juice of Sapho: early battle aggressor
20 September 2026. Connected partial prototype. The physical face and source precedence remain in the Sapho audit; the battle review separates scheduling, physical participants and tie priority. This checkpoint implements the printed aggressor effect during an existing opportunity. It does not adjudicate late timing.
Connected behavior
The holder can play the canonical, unreserved card while their shared preLeader
opportunity is open, before their readiness declaration and before either plan.
The other combatant may already be ready. Actual Voice, Prescience, Nexus/full-plan
inspection and Truthtrance commitments prevent this early use, as do suspended
interactions and mandatory disposal. Unchosen preparation prompts bind no plan
content and may remain. No hidden opposing hand or selected plan determines
eligibility. No holder-only pause or new confirmation window is introduced.
scope:'battleAggressor', mode:'aggressor' binds the battle, turn and use revision.
It discards the physical card once and records public priority, without swapping
attacker/defender slots, chooser, forces, leaders or later battle scheduling.
An already held position is unavailable. A recovered card can change priority
again at a fresh opportunity; no extra once-per-battle limit is invented.
The validated use history and independent event list survive JSON continuation. Reads, actions and automatic normalization reject mismatched history, event, combatants, turn or physical card custody. Legacy battles retain their original attacker priority and do not reopen closed preparation.
The shared tie helper checks both combatants for the effective Habbanya advantage before falling back to aggressor. Engine plan/Voice/prescience checks, public projections, AI calculations and the final battle quote use that priority. Ordinary strength ties and Stone Burner's physical-token ties therefore agree. Early use precedes all commitments, so Stone's existing public finishability guard can evaluate the changed priority before accepting a plan. The unresolved late mixed-allocation hazard from the battle review is not bypassed.
The hand panel exposes the real action, the table names aggressor and tie winner, and automatic notices mark a successful use. All four AI profiles can use the same private options and finish through the existing preparation and battle path. Timing strategy and complete Richese-game acceptance remain later work.
Evidence and limits
Focused tests cover actual ordinary/Stone outcomes in Basic and Advanced, Habbanya on either physical side, rejected stale/late/cross-owner submissions, unchanged rejected input, public eligibility with changed private rival holdings, receipt corruption, conserved recovered-card reuse and all four AI continuations. The mixed Emperor/Guild regression changes Stone's pre-commit finishability before any hidden opposing plan exists. Authenticated in-memory SQLite races consume one card; fresh stores restore each private seat through the same battle. Fixtures use genuine CHOAM/Richese setup followed by explicit conserved board/hand staging; they are not full genuine-game evidence or proof of every module combination.
The owner-only control and public table text have rendering regressions. Browser, required checks, complete-game samples, preservation and verified Git evidence belong to the source-bound checkpoint report and commit message.
Later pre-reveal, post-reveal and final-intervention opportunities remain unfinished, including their privacy-neutral response protocol and Stone allocation work. These are development boundaries, not extra printed prohibitions. Other Sapho timing questions and all mode/publication gates remain unchanged.