The capture batch reads moved onto server-streaming RPCs (StreamCaptures /
StreamUndispatchedCaptures) to get past gRPC's 4 MiB unary cap, but the
client interceptor suite attached the bearer token to unary calls only:
Dial installed WithUnaryInterceptor and nothing for streams, while
TaskGrants.StreamInterceptor requires the administrative token. On every
token-protected (non-loopback) listener -- every container-mode deployment
-- the daemon's binding dispatch and the dashboard's capture inspector got
PermissionDenied from the stream interceptor, and the unary fallback those
reads replaced is no longer taken, so there was no working path.
- Add StreamClientTokenInterceptor, mirroring gatewayrpc's, and install it
alongside the unary one in Dial, the single client dial path the daemon,
the dashboard and the agent all use.
- Route agenttransport's State Store dial through staterpc.Dial, deleting
the duplicate dial/fail-closed logic that installed only the unary
interceptor -- a second place for this class of bug to hide.
- Regression tests: the grants harness now dials through the production
Dial so client-side wiring cannot drift again;
TestCaptureStreamsCarryTheAdminToken reads both list surfaces (5 MiB
batch) through a token-protected listener;
TestStateStoreRealProcessTokenProtectedCaptureStream does the same
against the real binary; TestUpdateRejectsNilTask covers the Update
guard left untested by the earlier finding fix.