abi: complete Hipo Finance message schemas

[behrang]

What

Completes abi/schemas/hipo_finance.xml for Hipo, the liquid staking protocol on TON (treasury EQCLyZHP4Xe8fpchQz76O-_RmUhaVc_9BAoGyJrwJrcbz2eZ, jetton hGRAM, formerly hTON).

The schema currently declares only the deposit leg (deposit_coins, proxy_tokens_minted, tokens_minted, added in 3b80a51). This PR verifies those three field-by-field against the protocol's authoritative TL-B (contracts/schema.tlb — they are correct, only regrouped by contract) and adds the 16 missing ops for the remaining flows:

• unstake/withdraw: proxy_reserve_tokens, reserve_tokens, proxy_tokens_burned, tokens_burned, withdrawal_notification
• deferred (bill SBT) flows: proxy_save_coins, save_coins, mint_bill, assign_bill, bill_burned, mint_tokens, burn_tokens, burn_all, last_bill_burned
• rollback: proxy_rollback_unstake, rollback_unstake
• loans: request_loan, recover_stake_result, loan_result

Deliberately not redeclared (noted in an XML comment): ops already covered by generic TEP schemas — unstake_tokens is TEP-74 burn#595f07bc, transfer_notification, ownership_assigned, excesses, and Hipo's burn_bill, which is TEP-85 revoke#6f89f5e3 with an identical body (already decoded as SbtRevoke; a duplicate would make the opcode ambiguous).

Regenerated with go run cmd/codegen/abi/main.go. I'm from the Hipo team — happy to adjust conventions if anything doesn't match how you'd like the schemas structured.

Testing

go build ./... and go test ./abi/... pass (one pre-existing failure, Test_contractInspector_InspectContract/storm_vamm_coinm, reproduces on master). Round-trip marshal/decode was verified locally for the trickier layouts (reserve_tokens uint4 mode, Bool fields, request_loan's ^NewStakeMsg).

🤖 Generated with Claude Code

[behrang]

Gentle ping — this has been quiet for about ten days, so just making sure it didn't slip off the radar. It's a schema-plus-regenerated-code change with no behavior changes outside the Hipo ABI; happy to adjust naming or structure to your conventions, or split it up if that makes review easier.

[behrang]

Second ping, three weeks in — no urgency, just keeping it on the radar.

One thing that might help with prioritising: opentonapi#939 classifies Hipo actions on top of these schemas, and it picked up a reviewer this week, so landing this side first would unblock that one.

The branch is still conflict-free against master. Happy to rebase, split it up, or adjust anything that doesn't match your conventions.

[behrang]

Third ping, five weeks in.

Still conflict-free against master: schema additions plus regenerated code, no behavior change outside the Hipo ABI. opentonapi#939 builds on these schemas and has a reviewer on it, so this side landing first would unblock that one.

Happy to split it, rebase, or adjust naming to your conventions. If GitHub isn't the right place to chase this, tell me where is and I'll take it there.