Repository navigation
The page chooses EM's fields and says what limits the run - #145
Merged
Merged
Conversation
… page's "Which fields should EM learn from?" runs choose em (each session kept or dropped and why, then Find matches); Find matches lists report.txt's DIAGNOSIS items, kept in steps.json and given by describe workspace as diagnosis Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012o8JNBKSY1aREPbMQDG8g2
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.
What and why
Two things only the CLI and report.txt had are now on the page.
nayose choose em(declared in the page's layout, busy label "Choosing EM's fields"). It then shows each session (pairs, share agreeing on the given name, kept or dropped, why), a banner with the sessions kept now and a Find matches link, and the comparisons that took every session's m. The Try sample labels understand emchoose("EM chosen by the given name"), and a list of fields reads as "EM per …". The button is not on the Your data step: choose em needs a run, and there is none yet at that step.report.diagnosisnow returns items (what, pairs, fix).report.diagnosis_linesprints report.txt's lines from them, unchanged.Run.reportmakes the items once, prints them and keeps them in the report step's facts in steps.json.describe workspacegives them asdiagnosis, from the last run that wrote a report; it is null for an older run that has none. On Find matches, a card "What limits what the run finds?" lists them, the most pairs first. A choose em or try sample fix is a button that opens the Method page and presses its button,--recordsincluded. Any other fix shows its command line, with the real workspace, and a copy button. No items: one line, "Nothing found.". Null: no card.Tests: describe workspace returns the items, and report.txt prints the same ones; an older steps.json gives null. A browser walkthrough covers the diagnosis card (light and dark), choose em writing fit em "choose" from a double click that sends one request, a rerun, a diagnosis fix button carrying
--records, an older run with no card, a workspace with no run, and a lost server freeing the button. Full suite on 3.14 (301 passed) and the non-browser tier on 3.12 (277 passed); ruff clean.Checklist (CONTRIBUTING.md)
shortcut: …), and every store that grows says what bounds it (rules 3 and 4)🤖 Generated with Claude Code