chore(main): release 7.183.0 - #2795
Merged
zaxbysauce merged 1 commit intoSep 15, 2026
Merged
Conversation
zaxbysauce
enabled auto-merge
September 15, 2026 11:26
Contributor
Author
Drift check reportFound 2 drift finding(s): 0 error, 0 warning, 2 notice. required-check-contract (2)
|
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Execution-attempt tracing and task-cost cohorts (issue #2676)
What changed
execution_attempt_recordedobservability event (65th cataloguedkind): ONE event per execution attempt, bound to the exact task, call,
invocation, and generation identity the producer holds, with a closed
attempt-class vocabulary (
denial/attempt/result/duplicate/late/cancelled/provider_failed), explicit capture coverage(
captured/unknownlists), and a per-attempt cost block whose unknownaxes are strictly
nullplus anunavailablelist entry — never0.callId+invocationIdadded toWorkflowIdsSchema(13 → 15 recognized IDs): exact-call and invocationjoins are now first-class correlation axes; Stage A callers' PascalCase
sessionID/callIDare normalized at the recorder.(classes
attempt,result,cancelled; latency from the dispatch start,tokens only when the cost-evidence chain held usage, estimated-vs-billed
from
cost_source) and the Stage A gate route hook (classesdenial,result,latewith the correlation's threaded generation cursor, andduplicate— productionduplicate_resultroutes stay fail-open dropsbecause the seam holds no original record identity; the class is recordable
when a caller supplies
duplicateOf).src/services/task-cohort.ts): a DEEP-copiedpopulation snapshot with
capturedAt(post-snapshot mutation cannot changea reported denominator), frozen provenance manifests for the trigger /
WAL / event / host-status sources (bounded 64 KiB digests; missing sources
are explicit
unavailable), configuration/version strata, a computeduncertaintychannel (present whenever the sample is below threshold, anycost axis is unavailable, or any outcome is missing), and an explicit
causal-rate
qualificationverdict. Snapshots persist one boundedFIFO-20 manifest under
.swarm/observability/cohorts/(retention-registryrow
observability-cohorts)./swarm reportgains a "Task attempts (cohort)" section (--jsonschema version 2): per-class counts, cost known/unavailable split,
uncertainty, and the qualification line. Existing pairing/savings sections
are unchanged and documented as descriptive operational counts.
docs/execution-attempt-tracing.mddefines the event vocabulary,manifest schema, cohort inclusion rules, and the operational-counts vs
causal-rate-claims boundary; the event contract doc gains the kind section
and the two new correlation axes.
Why
Execution traces and task-cost measurements could not support causal claims
about retries, quality, latency, or cost: records were joined only at
session/task level (the call identity died at the envelope boundary),
denial/attempt/result/duplicate/late had no shared representation, unknown
token counts collapsed to zero in the legacy fold, and no cohort machinery
existed to qualify aggregate claims. Issue #2676 (Workstream D16).
Disclosed residual
The legacy
delegation_endfold (src/telemetry.tstoken?? 0defaults;src/services/cost-accounting.tsreadNumber(...) ?? 0) still zero-defaultsabsent usage on ITS surface — a pre-existing conflation tracked by a filed
follow-up issue. The new
execution_attempt_recordedsurface is immune byconstruction and never routes unknowns through that path.
🤖 I have created a release beep boop
7.183.0 (2026-09-15)
Features
This PR was generated with Release Please. See documentation.