feat(framework): upload out of band, never at the session's expense

No files, tests, or entry points are identified in the issue. Start by locating the session data sink, the local retention queue, and the redaction path referenced by #655; then determine how upload can remain out of band. Done requires the listed delivery, retry, retention, redaction, disabling, and duplicate-batch behaviors to be asserted.

Outcome

Measured data reaches a hosted dashboard reliably, and never at the cost of the session that produced it.

Scope

#652 claims the upload in its boundaries and no issue builds it. #656 reports across repositories and people, which is impossible while data expires locally on N laptops.

• Includes: what is sent — the run journal and the aggregates, never raw telemetry payloads.
• Includes: authentication, and where the credential lives. Not in a committed file.
• Includes: batching, retry with backoff, and idempotency, so a retried batch does not double a figure.
• Includes: backpressure and a bounded local queue, so an unreachable endpoint degrades rather than grows without limit.
• Includes: upload before local expiry. The sink's retention floor becomes a function of the upload cadence, or data is lost between the two.
• Includes: the redaction of #655 applied on this path, before anything leaves.
• Excludes: the hosted side — storage schema, tenancy, query model, server retention. That is the dashboard's product, not this repository's.
• Excludes: any behaviour that blocks, delays or alters a session. Upload is out of band, always.

Done When

• A session is unaffected in duration and outcome whether the endpoint is reachable, slow or absent.
• A batch delivered twice produces one figure, asserted against a duplicate delivery.
• An endpoint down for a day loses nothing, and an endpoint down past the retention bound says what it lost rather than silently truncating.
• Nothing the redaction list forbids appears in a captured request body.
• Disabling upload stops it immediately and leaves local reading intact.

Completion Evidence

A capture of what actually left the machine over a working week, checked against the redaction list, with the delivered totals matching the local ones.

Relations