Skip to content

feat: group Fusion usage by request#83

Merged
steipete merged 1 commit into
mainfrom
feat/fusion-usage-lineage
Jul 6, 2026
Merged

feat: group Fusion usage by request#83
steipete merged 1 commit into
mainfrom
feat/fusion-usage-lineage

Conversation

@steipete

@steipete steipete commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • give every Fusion invocation an internal compound request identity
  • group adviser and synthesizer usage into one expandable dashboard row
  • preserve per-call cost, failure, latency, and retained-content detail
  • audit pre-fan-out and provider-selection failures without merging caller retries

Verification

  • pnpm check
  • pnpm build
  • pnpm worker:e2e
  • pnpm --dir admin test
  • git diff --check
  • autoreview: clean, no accepted/actionable findings

Notes

  • incomplete groups caused by the 100-event retention window are marked partial and never overstate completeness or totals
  • Access adviser failures retain the synthesizer identity only for audit ownership; provider authorization remains unchanged

@clawsweeper

clawsweeper Bot commented Jul 6, 2026

Copy link
Copy Markdown

ClawSweeper status: review started.

I am starting a fresh review of this pull request: feat: group Fusion usage by request This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

@steipete steipete merged commit 86fc997 into main Jul 6, 2026
4 checks passed
@steipete steipete deleted the feat/fusion-usage-lineage branch July 6, 2026 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant