fix: cover two-candidate dispute slashing

[huangminghuang]

Summary

• Adds flow-batch-operator-terminal-tie, which materializes a three-operator schedule, administratively terminates one operator through typed opreg::terminate orchestration, and proves the two remaining live operators can open and resolve a two-candidate terminal tie with one non-canonical slash.
• Preserves flow-batch-operator-slashing as the original three-operator, three-candidate regression that produces two slashes.
• Moves the shared dispute scenario, constants, steps, canonical-envelope codec, inbound-tip reader, single-flight cache, and unit coverage into cluster-tool; neither flow package depends on the other.
• Finishes the shared-helper rename as BatchOperatorDisputeScenario, BatchOperatorDisputeConstants, and BatchOperatorDisputeSteps, with the steps barrel exported through the parent flow barrel.
• Keeps the configured operators_per_epoch value at three and verifies it explicitly while the terminal dispute opens from the two-operator live eligible set.
• Constrains scenario operator options to the provisioned dispute roster and rejects unsupported labels, duplicate delivery operators, and duplicate slashing targets during planning.
• Keeps SOLANA consensus and ETHEREUM candidate deliveries in separate parallel phases, uses generated SDK row types without casts or public third-party aliases, and scopes OPEN-dispute selection to the contested outpost and epoch.
• Removes the obsolete slashing-flow Jest project/configuration after relocating its tests to cluster-tool, and corrects the documented Jest project count.

Validation

• Exact current wire-tools-ts head: b42ee96bd352becde9dbba0ac76e66f953df6753.
• Current-head workspace build passed.
• Current-head focused scenario Jest passed: 1 suite / 10 tests.
• Current-head targeted ESLint and TypeScript Prettier checks passed.
• git diff --check passed.
• Current-head CI is green: Build and test #33433627755.
• Exact-head remote e2e is green: E2E Flow Tests #33434294378 built with wire-tools-ts at b42ee96bd352becde9dbba0ac76e66f953df6753, wire-sysio at 234abff294a5ddeca2832bc0617bef7d007b90fa, and ran only flow-batch-operator-terminal-tie. The run concluded with “All E2E flows passed.”
• The full PR diff and commit list were re-read after the final review follow-up; the correctness, architecture, and compliance findings are addressed with no remaining actionable issue.
• The installed Wire validation profile still lacks mappings for the new terminal-tie entry-point paths, so it cannot publish reusable exact-content evidence for those paths.

Reviewer notes

• The optional incomplete two-way scenario from the review is intentionally not included; this PR covers the terminal tie, while the companion Boost flow covers the other case.
• Review follow-ups and master syncs were added as normal commits; no history was rewritten.