Relock in2lambda and offer field set and part solution to the fix loop - #21
Merged
Merged
Conversation
…the fix loop (t26)
…the fix loop (t26)
…the fix loop (t26)
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.
in2lambda's dev has moved since the lock (pinned at 6699c53; dev is now a76603d): t44 freezes converted documents unwrapped with display maths on its own lines, t48 takes a list of selectors per role and reports a doubled block instead of refusing, t50 adds
draft field set FIELD --text RANGE(quote a range into a field already written) and t53 addsdraft part solution PART --text RANGE.Relock in2lambda at dev head in pyproject.toml/poetry.lock. Then give the fix loop the two new commands as tools in in2lambda_agent/fix.py:
field_set(field, text) for a finding that a field is empty or quotes the wrong lines, andpart_solution(part, text or literal) for a part whose solution is on the sheet under it; describe each in the system prompt beside the six commands there.field sethas no literal. package.py's command wrapper needs no change if it is generic; check. Update the corpus-specs and any fixture spec that t48's list form or t44's freeze changes, and tests/test_fix.py for the two tools. Then run the replay sweep (in2lambda-agent corpus <corpus> PHYS40002 --replay) and the UCL_MechEng PDF sweep and put both CSVs in the PR description, with the before/after built counts. Done when the lock names dev head, the two tools are offered and tested, and the replay sweep builds at least as many documents as before the relock.Workbench ticket t26.