Every repository a run lands in should have a README, even a quick fix #140
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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 hello world baseline (run 42, see #139) merged to
mainwith no README. The only run instructions were in the PR summary ("runnpm run dev") and the committedAGENTS.md, and an operator who openedindex.htmldirectly got a CORS error.Nothing in the pipeline writes a README: the prompts tell agents to read one (
prompts.py:1477,:2161,:2375,:2486), and the docs pipeline treatsREADMEas a docs file, but no step creates one.forgejo.py:849also deliberately creates repos with noauto_init, so a new repo has none.Proposal: a run that lands code in a repository with no README adds a short one: what the project is (from the brief), how to run it, how to run its tests. A scripted check (
paths-exist:README*after the last agent step, or adocs-style check) holds the pipeline to it. A repo that already has a README keeps it, with the run's instructions updated only where the run changed them. The run instructions in the README are what the independent judge proposed in #139 would follow.Shipped as
runs-leave-a-readme.agent.implementin the quick fixes, the first apply group in an OpenSpec run, or the apply step insolo. An existing README is kept, and only its run and test instructions are updated where the work changed them.docs/doesn't count. A round without one fails as a red lane does. That round is not judged, and the fix round writes the README. So nothing is merged without one.Verified. The fast and full lanes passed on the integrated batch (3,388 backend tests, 681 vitest, 249 browser specs with the slow and live ones, 29 of 29 simulated runs), and it is live on production as
57971c2(deploy run 138, self-checkbraid-selfcheck: ok). Archived ina6ae0dc. The new simulated runreadme-from-the-fix-roundstarts from a repository with no README.Not covered: the docs, plan and release pipelines, which land no code. Whether a real model writes a sensible README needs a real-model run on a repository with none, as in run 42.