test(lyracore): remove realm-wide party cleanup

[Mathih13]

The LyraCore wire suite dissolved every party before each scenario. That hid Character-deletion residue and removed unrelated parties from the test Realm.

Scope party setup, assertions, and teardown to each scenario's known Character and party IDs. Add a Headless Client scenario that deletes one member from a three-member party twice, checks both Realm-core and the Shard mirror, and proves a separate party keeps its row, leader, loot settings, and members. Character create and delete probes now wait up to three seconds for the matching Character-list update while retaining the protocol success checks and exact deleted-GUID assertion. Party cleanup also fails closed if it cannot identify or query the authority.

The core behavior test passed on a private two-Shard fixture with LyraCore artifacts from 1d6ec20d797ab1af78e399a2087983e346fc0a61. Both deletion lifecycles passed and preserved the unrelated party. No existing Realm was accessed.

The full eight-scenario Playerbots Package run remains pending. A bounded schema audit of 20 local Module artifacts found none with playerbots_spawn_role or pkg_playerbots_bot, including the frozen fixture Module. LyraCoreProject/LyraCore#46 should stay open until a compatible Package-enabled Module and Gateway pair is available for that run.

Validation:

• cargo test --locked
• cargo clippy --all-targets --locked -- -D warnings
• cargo fmt --check
• all five offline LyraCore adapter tests
• syntax check for every adapter script
• private two-Shard party_delete scenario, two lifecycles

Refs LyraCoreProject/LyraCore#46.

Model: GPT-5.6 Sol, high effort. Harness: Codex T3.