Qualify cloud lifecycle telemetry alongside existing SDK events

Overview

SDK telemetry manager and hidden emit/blast are implemented; the earlier cloud-telemetry requirement has no demonstrated install/login/harness lifecycle coverage.

Priority: P2 / post-mvp. Impact: roadmap improvement. Initial planning estimate: Medium; refine after inventory. This issue does not add a release blocker.

Current evidence

SDK telemetry manager and hidden emit/blast are implemented; the earlier cloud-telemetry requirement has no demonstrated install/login/harness lifecycle coverage.

• Source: src/bootstrap.cpp#L273
• Source: src/bootstrap.cpp#L405
• Source: src/app.cpp#L94

Design and implementation plan

Inventory existing events and gaps before adding a minimal cloud lifecycle schema; reuse SDK telemetry and correlate nonsecret request IDs, avoiding synchronous analytics on token delivery.

1. Reconcile the current implementation and any already completed work with the evidence above.
2. Record the owner, selected scope, dependencies and unresolved decisions before implementation.
3. Implement or execute the selected scope using existing components and artifacts.
4. Attach reproducible validation or outcome evidence and record any deferred work.

Acceptance criteria

• Inventory configured/emitted/delivered cloud lifecycle events and prove test-account delivery.
• Exclude prompts, credentials and access tokens; define opt-out/retention.
• Bound queues/flush failures and prove telemetry outage does not block normal inference.

Related work and deduplication

No existing issue has this acceptance scope; existing release defects remain separate.

• https://github.com/RunanywhereAI/InferenceInfra/issues/501
• https://github.com/RunanywhereAI/Runanywhere-monorepo/issues/158

Requirement provenance

Reconciled September 13, 2026 against WALLY_CLOUD_PRODUCT_SOURCES.md (SHA-256 e601b7b154b750965fa8d25d4533d3542621bd00b3bb30038c1fae553a549e7b) and the consolidated requirements report. Historical proposals are not evidence of current delivery, customer agreement or approved pricing.

Start with src/bootstrap.cpp at lines 273 and 405 and src/app.cpp at line 94, then inventory the existing SDK telemetry manager and hidden emit/blast events. Reconcile configured, emitted, and delivered cloud lifecycle coverage before selecting scope. Done requires reproducible test-account delivery evidence, privacy and opt-out/retention decisions, bounded failure behavior, and proof that telemetry outages do not block inference.