WIRE-353: align emissions E2E and bootstrap docs with no-expiry DClaim

[huangminghuang]

Summary

• Let the emissions flow validate DClaim bootstrap configuration without requiring the removed expiry window; document indefinite claimability and retained import controls.
• Reject malformed packed collateral codes before planning configuration actions, preserving exact chain/token identity and the zero sentinel.

Why

The approved WIRE-353 resolution extends WIRE-339 no-expiry policy to DClaim. The old positive-window assertion rejects the new configuration; the flow still requires the configuration row, open bootstrap import window, and its accounting/payout invariants.

The target branch supplies canonical string writers. The remaining collateral guard checks safe nonnegative integers and exact packed round trips so conversion cannot silently drop high bits or select a different asset.

Validation

• TypeScript build, lint and debugging bundle build passed with the actual consumer resolving the candidate SDK.
• Focused collateral configuration, registry/external outpost, chain/reserve/token writer, reserve-tool, slug and swap-context tests: 114 tests across nine suites passed. Shared configuration tests: 141 passed.
• Collateral tests cover all operator roles, preserved amounts, high-bit loss and malformed packed values.
• Independent correctness, architecture, and compliance reviews found no actionable issues.
• Local operator-termination and full 30-minute emissions flows passed against Sysio 20591bfd, SDK fdbddd26, and Tools 78f39784: exact collateral/reward payouts, all four transfer directions, and zero capital shortfall. The subsequent host-only reverse-range fix passed 28 query tests; these flow results precede that fix.

Companion PRs

• wire-sysio #639: removes claim expiry configuration/cleanup and preserves indefinite claimability.
• wire-libraries-ts #87: aligns the generated interfaces. Merge contracts, then SDK source, then publish a compatible SDK. The currently published SDK 1.0.92 lacks the required interfaces/serializer; this PR remains draft pending release, a compatible dependency minimum and registry-only consumer validation. Sibling-candidate tests do not establish registry compatibility.