[yapishu]

Wallet clients need the shared core's lock, metadata, fee, and allocation rules to produce the same transactions across runtimes. This implements those rules natively against tx-types at 02d194605c475013745cc65b26f1413cd098932e and the official Hoon fixtures at 9bcc26c6c57019dfde7f83aad9a9dd4ed5cd7902, and sets the SDK version to 0.2.0.

• A pure planner handles deterministic automatic/manual selection, sweeps, exact or solved fees, per-input positive seeds, complete parent commitments, and refunds. Payment helpers use this planner.
• Lock conditions support PKH, inclusive timelocks, hashlocks, and burn primitives; tagged trees preserve full Merkle paths. Fund admission uses an explicit authoritative identity and candidate-height maturity policy.
• Typed note data covers lock and bridge payloads. Fee sizing follows phase-dependent metadata merging, witness discounts, and saturating arithmetic. Canonical JAM uses structural backreferences with bounded expansion.
• V0 notes migrate into V1 outputs using complete source, coinbase, and timelock records. Parsing requires those records; signing and merging preserve the reviewed plan and fee context.

The shared corpus checks all 31 tagged lock leaves, Hoon metadata and fee results, seven Rust planner scenarios, and four migration scenarios with exact unsigned and signed bytes. Documentation describes the APIs, height/fee context, and validation boundaries. This does not publish a package or tag.

The Python implementation uses immutable policies and exact integers, with no runtime dependencies.

Validation:

• python -m unittest discover -s tests: 27 tests pass, including exact Rust/Hoon fixtures and boundary cases.
• Ruff lint and format checks pass.
• Version 0.2.0 sdist and wheel build successfully and pass twine check; the installed wheel exposes the planner, migration, lock-tree, and fee APIs.
• Shared JSON copies and Hoon SHA-256 checksums match the reproducible Go-repository fixture exporter.

Related core work: SWPSCO/tx-types#25