Skip to content

Keep one draft per source, not per directory - #69

Merged
peterbjohnson merged 3 commits into
devfrom
wb/t42
Sep 20, 2026
Merged

peterbjohnson merged 3 commits into
devfrom
wb/t42

Conversation

@peterbjohnson

Copy link
Copy Markdown
Member

source add writes draft.json beside the source, and every draft command reads the draft in a directory. So a folder holding several sheets - which is what every document set in the corpus is (PHYS40002 has 18 tex files in one folder) - can hold one draft at a time: the agent's sweep over that folder overwrote draft.json eighteen times, and nothing can inspect any but the last. It also means two people, or two runs, cannot work on two sheets in one folder.

Name the draft after its source: freezing sheet.tex writes sheet.draft.json (or a sheet.in2lambda/ folder holding source.md, draft.json and the spec run's record), and every command takes the draft path, or the source path, rather than a directory: in2lambda draft question add --draft sheet.draft.json ... with the current directory's single draft still found when there is exactly one. The log, replay, validate, build and render all follow. Done when two sources in one folder each freeze, validate and build without touching the other, and the fixtures and the docs use the new naming.


Workbench ticket t42.

@peterbjohnson
peterbjohnson merged commit 5331f4e into dev Sep 20, 2026
2 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant