Enrich trace v0 with blocker_codes#3
Merged
Merged
Conversation
Adds blocker_codes (sorted, unique string[]) to every trace artifact — the distinct blocker codes (E_*) seen across the run. This is the field the upcoming bean-lessons analyzer needs to rank which gate conditions fire most (weak load-bearing, open risks, conflicts, verifier failures); trace v0 previously stored only blocker COUNTS. - bean-run: derive blocker_codes from the open-front keys; emit alongside the counts. - schemas/trace.schema.json: new required key, array of unique strings; top level stays additionalProperties:false. - conformance: asserts the field exists, is a sorted unique string[], and contains the expected E_OPEN_RISK for the driver fixture. - trace.md updated. trace v0 is unreleased, so no migration. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
…osed), not final-state Per review of #3: make the docs/schema explicit that blocker_codes is the set of distinct codes seen across all rounds — including blockers later closed — not a count and not final-state-only. Code already behaves this way (derived from blockers_seen, not final). Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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
1 participant
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.
Summary
blocker_codes: string[](sorted, unique, deterministic) to every trace artifact — the distinct blocker codes (E_*) seen across a run.additionalProperties: false;blocker_codesis a new required key.string[], and contains the expectedE_*codes for a driver run.trace.mdupdated.Why
blocker_codesis what lets the upcomingbean-lessonsanalyzer rank which gate conditions fire most (evidence bars, open risks, conflicts, verifier failures) — the most actionable signal for improving bean itself. Trace v0 stored blocker counts only. This is a trace-format correction, kept separate from the analyzer so the contract change is reviewable on its own.trace v0 is unreleased, so no migration.
Validation
npm testnode test/conformance.mjscargo fmt --check --manifest-path rs/Cargo.toml🤖 Generated with Claude Code