feat(telemetry): a failed task says why #90

Merged
peersky merged 3 commits from feat/generic-job-variables into dev 2026-08-29 07:03:54 +00:00
Owner
No description provided.
- Added Interface carrying the head of the failure's rendered chain on the task-failed event, with the provider detail where one exists, since a class alone says a task failed and diagnosis needs the words.
- Fixed Bug where every non-payment failure was classed as a timeout, so parse failures and empty completions wore a label pointing investigation at the clock; the class now comes from the chain.
- Added Interface for per-job variables on the agent context, the request and the policy configuration, carried verbatim from a team's yml through the manifest to every seat, so deployment-specific behaviour lives in that team's agent code.
refactor(agents): the deliberation type is a job variable, not a protocol field
All checks were successful
CI / Dependency Age Check (pull_request) Successful in 4s
CI / Lint & Audit (pull_request) Successful in 1m6s
CI / Spell Check (pull_request) Successful in 5s
Commit Lint / Validate PR Title (pull_request) Successful in 3s
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Publish Release / Publish to crates.io (pull_request) Has been skipped
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Publish Release / Create GitHub Release (pull_request) Has been skipped
CI / Test (pull_request) Successful in 5m1s
0986e6119c
- Removed Interface naming a specific deliberation style on the agent context, since the protocol should carry a team's variables without knowing any of their meanings, and the generic variables map already carries this one.
forgejo-actions changed title from feat/generic-job-variables to feat(telemetry): a failed task says why 2026-08-29 07:02:15 +00:00
peersky deleted branch feat/generic-job-variables 2026-08-29 07:03:54 +00:00
Sign in to join this conversation.
No reviewers
No labels
release
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
peeramid-labs/quorum-rs!90
No description provided.