Repository navigation
Epic: Usage, telemetry and operator diagnostics #1063
Description
Current cycle runbook
The table is the executable next-action index for this epic. Read the roadmap cycle contracts and the canonical issue together. Each issue retains its own acceptance, current Project Status, milestone and scope. Grouping does not close issues or make one large implementation batch.
Ready for discovery means read-only qualification/design only. It does not authorize implementation, tests, live calls, quota use, merge or release. Ready for AI is reserved for a prepared implementation/review slice with prerequisites met. In-flight work must coordinate with the existing branch owner.
| Issue | Delivery cycle / packet | Primary step | Readiness | Bounded next action |
|---|---|---|---|---|
| #1129 | C10 Operational visibility; C10.01 | 11 | Needs refinement | Refine one bounded slice: Define counters/histograms/gauges and their label limits. Compare pinned source/current local paths and define the focused regression before coding. |
| #1128 | C10 Operational visibility; C10.01 | 12 | Needs refinement | Refine one bounded slice: Trace admission, routing attempts, provider TTFT and terminal outcome with stable IDs. Compare pinned source/current local paths and define the focused regression before coding. |
| #1131 | C10 Operational visibility; C10.02 | 21 | Needs refinement | Refine one bounded slice: Define trusted session/project attribution and limits on header cardinality. Compare pinned source/current local paths and define the focused regression before coding. |
| #1130 | C10 Operational visibility; C10.02 | 22 | Needs refinement | Refine one bounded slice: Use deterministic suite versions and explicit model/account selection. Compare pinned source/current local paths and define the focused regression before coding. |
One writer per shared path; independently review and serialize composed exact-head proof. Handoff includes source/head/base, original acceptance IDs, paths, tests/receipts, reviewer and remaining scope. Stop for missing source, ownership, credentials/runtime authorization, drift or ambiguous acceptance.
Outcome
Give operators accurate spend, routing, quota and latency evidence with redaction and bounded storage.
Roadmap: #1056.
Tasks and child epics
- Consolidated feat(usage): distinguish unknown prices, estimates and provider receipts #1133 into fix(usage): complete paid usage, price provenance and dollar-budget accounting #1085; preserve all original acceptance criteria in the canonical implementation ticket.
- feat(observability): expose authenticated operational metrics and runtime pressure #1129 | P2 | stage 3 | feat(observability): expose authenticated operational metrics and runtime pressure
- Consolidated feat(observability): report event-loop stalls and runtime pressure #1132 into feat(observability): expose authenticated operational metrics and runtime pressure #1129; preserve all original acceptance criteria in the canonical implementation ticket.
- port(omniroute): add opt-in OpenTelemetry routing traces #1128 | P2 | stage 3 | port(omniroute): add opt-in OpenTelemetry routing traces
- port(omniroute): add provider and routing evaluation runs #1130 | P2 | stage 3 | port(omniroute): add provider and routing evaluation runs
- port(omniroute): attribute usage to agent sessions and projects #1131 | P2 | stage 3 | port(omniroute): attribute usage to agent sessions and projects
Completion criteria
Every accepted child meets its behavior, test, documentation and evidence requirements. Candidate-only items receive an explicit adopt/defer/reject disposition. An open upstream proposal cannot be considered a completed port.
No implementation or live/provider/deployment verification was performed during this planning audit.
Cross-epic dependency: #1085 contains the preserved scope originally tracked in #1133. Its original parent remains unchanged.
Activity