fix(boot-test): exactly what a new server gets, and pinpoint settings it can't start without #20

Merged

greg merged 2 commits from feat/builder-pinpoint-empty-settings into main 2026-10-26 02:08:51 +00:00

Conversation 2 Commits 2 Files Changed 7

+146 -57

2 Commits

Author	SHA1	Message	Date
gregandClaude Opus 5.5	fe790ad223	fix(boot-test): run every boot test with exactly what a new server gets ... CI's boot test gave every blank password-like setting a throwaway value. A real deploy only fills x-generate fields, so a template whose server won't start without one passed CI and failed for the first owner who deployed it. boottest-payload now fills only x-generate fields, for CI and the builder alike. The old behaviour is kept as -fill-blank-passwords, used only by the builder's second boot to tell whether an empty setting is why a draft fails. Messages and AUTHORING.md no longer say boot tests fill passwords; a server that needs a join password gets x-generate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 22:01:16 -04:00
gregandClaude Opus 5.5	98ba043bec	feat(builder): pinpoint settings a server can't start without ... Booting drafts as deployed catches a server that stops when a setting is empty, but the server's own output rarely says why, so the model guessed (more memory) for three rounds and the draft ended as WIP. When a draft fails with its defaults and has blank password-like settings without x-generate, the builder boots it once more with those filled. If that boot passes, the cause is certain, and the model is told exactly that: these settings stop the server when empty; give them x-generate (a password per server) or a working default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 21:57:16 -04:00