Fix Buzz live inbound on production relay

[olegbrok]

Summary

• remove since from the native Buzz main subscription REQ so the production relay live-pushes new channel events
• retain the exact computed subscription floor in client-side validation before the recent-ID cache, authorization gates, or durable writes
• keep heartbeat REQs unchanged with since and limit: 1
• model the production relay's since-blind live-fanout behavior in the WebSocket rig
• cover a 288-frame pre-EOSE stale history burst, proving zero broker turns, zero inbound-event rows, unchanged principal-seen state, and no recent-ID cache consumption before the live event

Root cause

The production Buzz relay returns stored events for subscriptions with or without since, but it does not live-push newly published events to any subscription whose filter contains since. The inc2 main subscription therefore authenticated and reached EOSE, then remained silent forever.

The main REQ is now open-ended on the wire. The existing client-side floor remains the freshness authority, so historical events streamed before EOSE are rejected before cache, policy gates, ledger writes, or persona dispatch. Active liveness probes keep their stored-query since + limit semantics.

Validation

• 61 passed: all Buzz tests
• 220 passed: agent registry, DB security, and auth under PINKY_AUTH_DENY_DEFAULT=shadow
• 123 passed: broker and messaging overlap
• 91 passed: daemon and poller overlap
• full Ruff check passed
• git diff --check passed
• uv lock --check passed
• uv pip check passed
• compileall passed
• sdist and wheel builds passed

Exact local tuple before publication:

• base: cd3ca1c7dbdf180ccc801abcc76b34056a92e06f
• head: 60958b32df7762108ed0c7f65f9f04e171d54a78
• tree: e97a18302222093833754791be9add0c0f1a4511

Draft only. Merge, release 26.08.011, and deployment remain operator-controlled.