monad-developers / monad-developers/ultrafuzz
events rejects the authenticated AgentTraceSummary lifecycle projection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 18
- Avg merge
- 11h 10m
- Merged PRs (30d)
- 194
Description
Summary
Ultrafuzz's authenticated Smithers compatibility layer deliberately adds AgentTraceSummary to the runner's default lifecycle projection. The public ultrafuzz events reader still rejects that exact event because its own pinned lifecycle allowlist omits it.
As a result, an ordinary lifecycle-only events query fails as soon as a matching page contains an agent trace summary:
WORKFLOW_EVENTS_INVALID: workflow event type is not in the pinned lifecycle contract
No --raw or agent-category query is required to trigger the mismatch.
Generic reproduction
- Launch a synthetic workflow using the authenticated compatibility snapshot.
- Let one agent-backed node finish so the runner records an
AgentTraceSummary. - Run
ultrafuzz events <run-id> --since 5m --limit 20 --json. - The runner emits the summary as part of its patched default lifecycle stream, then Ultrafuzz rejects its type.
The same mismatch is reproducible hermetically by returning a well-formed Smithers event record whose type and payload type are both AgentTraceSummary.
Root cause
SMITHERS_CLI_LIFECYCLE_TRACE_SUMMARY_PATCH extends Smithers' DEFAULT_LIFECYCLE_EVENT_TYPES with exactly AgentTraceSummary, but CURRENT_LIFECYCLE_EVENT_TYPES in the lifecycle inspection adapter was not extended with the same type.
Expected behavior
- Accept a well-formed
AgentTraceSummaryfrom the authenticated default lifecycle projection. - Keep raw agent chunks, tool calls, and every other non-lifecycle category excluded.
- Preserve the existing strict envelope, provenance, ordering, and bounded-output checks.
- Cover both one-shot and watch parsing through the shared event-line parser.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the lifecycle inspection adapter where CURRENT_LIFECYCLE_EVENT_TYPES is defined, and compare it with the Smithers compatibility patch that adds AgentTraceSummary. Trace the shared event-line parser and its one-shot and watch callers. Done means well-formed AgentTraceSummary records are accepted while raw agent categories and existing envelope, provenance, ordering, and bounded-output checks remain rejected or enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100