Version 0.2.2 — the model can answer, and one file per platform

[timbogdanov]

What this changes

Describe-it had never worked, for anyone. output_config.format compiles the schema into a grammar, and the service caps a schema at 24 optional parameters. aiSchema() hung all 29 DSL_RANGES keys plus nine others off a single shape object — 38 properties with only type required. Thirty-seven optional. Every request came back:

400 — schemas contains too many options parameters 37 ... limit is 24

A shape now carries its parameters as a list of name/value pairs:

{"type":"diagonal","params":[{"name":"dx","value":"1"},{"name":"period","value":"8"}]}

Nothing is optional — 0 optional parameters, and it stays 0 however many primitives the DSL grows. The name enum still refuses a parameter the DSL doesn't have. Types and ranges leave the grammar, which costs nothing: every value already went through dslValidateShape's clamping. aiCoerce converts back and names the offender (period is not a number: "eight"); aiToProgram collapses pairs into flat shapes, so the Program box still shows a program you can read and edit.

Then a second bug nobody could reach. With the 400 gone, "city skyline" returned too many layers. The prompt states every parameter range, every primitive, the canvas limits and the scale — and never DSL_MAX_LAYERS. dslValidate discards the whole program over it. Now stated, derived from the constant so the two can't drift.

One file per platform. Two DMGs, two zips and three Windows builds meant downloading twice left PatternFront, PatternFront 2 and PatternFront 3 in Finder — macOS numbering duplicates, exactly as README.md:42 already warns. Releases now ship the Apple silicon .dmg and the x64 Setup.exe, and the notes say to drag to Applications before opening, which is what stops the duplicate existing.

	before	after
schema optional params	37 (400 on every request)	0
release artifacts	8	2

Verification

Confirmed against the real API with a live key: the request is accepted and returns a program. New checks in tools/verify-behaviour.js fail on the code as it stood — the schema's optional count against the limit of 24, and the prompt naming whatever DSL_MAX_LAYERS currently is — plus coverage of the pair→flat conversion, numeric coercion and enum rejection.

Full suite: 421 checks, 0 failures.

Checklist

• npm run verify passes
• Generated files re-run through their generator — none touched
• If it touches the desktop app, the browser build still works — changes are the AI path and CSS-free
• If it adds a stamp, the contact sheet was looked at — no stamps

🤖 Generated with Claude Code

https://claude.ai/code/session_01GRMJpT8yxY2Q33td1QeP7z