After the comparison: lint, briefs, spine, review findings, inference per backend (#279) #297
Loading…
Reference in a new issue
No description provided.
Delete branch "claude/batch-294"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The batch after the backend comparison (#279): three OpenSpec changes, one merge.
Fixes after the comparison (
fixes-after-the-comparison)ban-checkprints only the rules that block (--allfor every rule), and the briefs list only those. The test-only refusal and the scenario-test brief say a helper goes under a test directory..gitignoreright after it; the file's header names Braid.--logsprints the end of its osfd log, and the image self-check passes it.script.scenariosand git-flow's release steps have a phase. A drift test checks every built-in node.Review findings panel (
review-findings-panel)6 to fix · 5 notes) in the tone of the worst finding: red, amber, grey or green. The code review's major findings count as things to fix.outcomes.json.GET /api/runs/{id}/review/{round}serves a round, and a panel under the review and revision steps lists it by weight; a click on a review chip opens it.Inference per backend (
inference-per-backend)/metricsand/slotsgive its requests, each slot's context, prompt reuse and draft acceptance; tabbyAPI shows Braid's own rows; a hosted API shows Braid's tokens and their cost at the profile's prices. Every chart has a value axis.Checked
./tools/test.sh: 198 backend tests, 56 unit tests, 18 browser specs../tools/sim.sh: 67 of 68.e2e-lane-inferredfails on main as well, filed as #296.slot 0 · 1.3k of 262k, reuse 99%, drafts 91%) and on a priced Claude profile (no slots, tokens and cost).🤖 Generated with Claude Code
A review's chip counts its findings as the digest merges them, in words a reader knows (2 blocking · 6 to fix · 5 notes, nothing found), and takes the tone of the worst: red, amber, grey or green. The code review counts major as to fix and minor as notes. The verdict carries the tone; the step stores it. Lenses give each finding an optional title; the revision records what it did with each finding by its id in .osf/review/r<n>/outcomes.json. GET /api/runs/{id}/review/{round} serves a round, and ReviewFindings shows it under the transcript of the round's review and revision steps, grouped by weight; a click on a review chip opens it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>cmoriarty referenced this pull request2026-10-28 22:42:04 -04:00