Repository navigation
feat(ui): trustworthy analytics with coverage — structured usage summary and /api/analytics (#200) - #229
Merged
Conversation
…ary and /api/analytics (#200) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #200.
Trustworthy analytics in
forgecell ui:molecule.UsageSummary(Record)is the structured data behindUsageSummaryLines, which stays the renderer. It records per-attempt cost, basis, tokens, effective models and coverage (n of m reported).GET /api/analytics: outcome counts by lane; wall-clock, active Atom time and waiting time; a harness/model breakdown that keeps the Unknown and Not-recorded groups; cost with coverage.app.jsrenders it with text-only DOM nodes, and demo mode serves labelled sample data.Built by Forgecell Molecule
mol-200-e4aa0dd6b2fa9dcc1d698058(planb3b2941f). Hand-delivered: the candidate failed one of its own new tests, but only under the Lab's longTMPDIR. Labels were truncated before redaction, so the lab path was cut mid-way and fell back to[local path]instead of<lab>. It didn't leak, but the order was wrong. Fixed here: redact first, then bound. I reproduced the failure with a longTMPDIRbefore the fix and confirmed it passes after.Review: one independent adversarial pass. Fixed here: small reported costs rendered as
$0.0000. They now use six decimals, like the engine'sformatUSD. Rebased onto #201 (#227); the conflicts inserver.go(theunavailablelist) andapp.js(thestateobject) were resolved as unions, andnode --checkpasses. A clean-shellgo test -timeout 25m ./..., vet and gofmt pass on the rebased commit.LOWs (not fixed):
toFixed(4)(app.jsper-run usage line and total). Same display issue, outside this slice.🤖 Generated with Claude Code