amadan
Rate limit: refusals at the sending edge's backhaul queue are not in owners' counts open
On branch design-edge-rate-limit-358
Parked from the #358 final review (finding 6), not fixed on design-edge-rate-limit-358.
When a request lands on a box that is not the instance's home, the sending edge's backhaul fair share (Task 7) can answer 429 before the request reaches the home box. Those refusals, and observe-mode "would refuse" decisions there, are only logged (backhaul-share <box>). They never reach usage.EdgeRow.RateShed/RateCeiling, so carlos ratelimit show and the console GET can read zero while some of an owner's visitors are being turned away on another box.
Why it was parked: the sending edge has no route row, so no account/app to attribute a usage row to, and spec §5.1 deliberately made its numbers box-level. Options for a follow-up:
- Carry the refusal to the home box out of band (a counter delta keyed by host, attributed there).
- Give the sending edge the owner identity the home map already publishes for door routing, and meter there.
- Keep it box-level and expose it in the operator's box metrics instead of the owner's counts.
During the observe rollout, read the backhaul-share log lines alongside the owner counts.