jschoubben 719956b745 R1-F-parts: the receiving side keeps a transfer's idle key and reads its cap from the binding ...

distribution and gitea each carried the same idle bound (one expiring key per open transfer, its end
dropping a transfer idle for 24 hours or arming it again for the rest) and the same read of incoming's
cap from its binding: the second instance of the kind, so it moves to the Receiver every holder shares.
Arm is called on each open that leaves a transfer open, a key not written failing it loudly; Expired
handles a key's end; Bound reads the binding's cap over Cap. BusArm, BusCap and FollowIdle bind them to
the holder's own state and objects.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

2026-11-04 17:24:55 +01:00

..

bus.go

R1-F-parts: the receiving side keeps a transfer's idle key and reads its cap from the binding

2026-11-04 17:24:55 +01:00

parts_test.go

J4 (J3 item 7): merge A3's wip/registry-a3-sdk (c974a11): a holder's receiving side of a file in parts joins its sender

2026-11-04 15:12:03 +01:00

parts.go

ADR 0627 §2: the sending of a file in parts is seat-neutral runtime; publish leaves mesh-sdk

2026-11-04 13:09:19 +01:00

receive_test.go

R1-F-parts: the receiving side keeps a transfer's idle key and reads its cap from the binding

2026-11-04 17:24:55 +01:00

receive.go

R1-F-parts: the receiving side keeps a transfer's idle key and reads its cap from the binding

2026-11-04 17:24:55 +01:00