Register corrected supplemental control contracts and retained claims

[DavidBakerEffendi]

The prior control series stopped before Python analyzer dispatch because three supplemental commands retained the original contract path. This prospective registration binds those commands to the new packet and runs the corrected Python wrapper first.

Key Changes:

• Register 33 controls and 84 serial groups against merged harness fdb83ab, with exact runner provenance, input hashes, designated roots and fresh per-dispatch resource checks.
• Preserve the prior 30 successful controls and failed wrapper attempt; carry all 34 known predecessor claims explicitly, retaining unknown historical counts and a separately disclosed one-claim qualification allowance. No execution, freeze or publication is claimed by registration.

Touch Points:

• reports/releases/v0.9.0/execution-v1/resume-20261007-04/

Validation: exact merged release runner build passed; all 157 bound inputs and supplemental contract arguments verified. Ledger initialization preserves predecessor anchor and claim bytes. Dispatch follows green registration CI and merged-main verification, with no automatic retry.