Connect early Juice of Sapho battle aggressor

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

docs/CURRENT_STATUS.md

@@ -6,12 +6,11 @@ gated.** Prototypes do not open completion or publication gates.
 
 ## Current checkpoint and work
 
-Latest delivered rules checkpoint: `62e87d2`, [Harass allocation](HARASS_ALLOCATION.md).
-Types, lint, **4,850 offline tests**, production build and 43 HTTP checks passed.
-Eight genuine card-variant games completed in 9,956 accepted actions with 266
-periodic save/restore checks and no rejected candidates. Focused and browser
-cases exercised ambiguous allocation. All 1,038 opening games and original
-seat/recovery records were unchanged; 1,072 rooms remained after isolated QA.
+Latest delivered checkpoint: `bfa24b0`, [optional table sounds](TABLE_SOUNDS.md).
+Types, lint, **4,856 offline tests** and production build passed. Browser controls
+verified mute, keyboard volume, refresh and cross-tab preferences; physical audio
+and screenshot acceptance remain open. All 1,072 games and original seat/recovery
+records were preserved, and the server remained healthy after the outage.
 Earlier evidence remains in the [implementation history](IMPLEMENTATION_STATUS.md).
 
 The connected [Harass & Withdraw prototype](HARASS_WITHDRAW_RUNTIME.md) supports either
@@ -24,22 +23,20 @@ card-specific discard precedence are explicitly labeled inferences. The Stone
 Burner timing question is pending; no user answer is assumed. Reinforcements
 remains unfinished. This does not open variant, mode or publication gates.
 
-Current checkpoint: [optional table sounds](TABLE_SOUNDS.md) connects local mute,
-volume, a test sample and short public phase/automatic-action cues. Initial and
-background updates stay silent; preferences survive refresh and synchronize
-between tabs. This adds no gameplay actions, private eligibility checks or game
-storage. Final source-bound checks and delivery are recorded in the private
-report and Git message; physical audio and screenshot acceptance remain open.
+Current checkpoint: [early Sapho aggressor](SAPHO_AGGRESSOR.md) connects the
+printed battle-priority effect during the existing shared pre-plan opportunity.
+Physical attacker/defender/chooser stay stable; Habbanya takes precedence in either
+slot. Shared priority feeds Stone admission, ordinary/Stone resolution, public
+controls and all four AI profiles. Battle-bound history survives private saved
+continuation. Later intervention remains unfinished; no new ruling is assumed.
+Final checks, samples, browser evidence and delivery belong to the source-bound
+private report and Git message.
 
-On 20 September, the stopped server was started after backing up all 1,072 rooms.
-Following another reported outage, the server responded normally and every saved
-game still matched that baseline. The isolated browser seat restored successfully.
-No database reset or recurring automation was needed.
-
-Next: prototype ordinary Mirror Weapon copies using the existing shared resolver,
-while retaining explicit gates for unresolved copied Tooth/Artillery disposal and
-Stone Burner choices. Sapho battle aggressor is the next independent candidate.
-The remaining Leader Skill bands retain their existing pending rulings.
+The [Mirror admission review](MIRROR_WEAPON_ENGINE_AUDIT.md) found that every genuine
+Richese setup contains the unresolved copied weapons. Ordinary-only activation
+cannot safely depend on hidden custody or alter the printed deck. Mirror remains
+gated pending the existing disposal ruling and copied-choice work. Continue with
+independent missing faction/card functions, then integrated play and refinement.
 
 ## Authoritative navigation