Add safe piece creation and validated LLM generation #95
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: eleith/luzzle#95
Reference in new issue
Block a user
Summary
Core groundwork for interactive LLM generation, plus CLI preflight validation. Web UI integration follows separately; the CLI remains quiet.
Add
Piece.write(markdown, { createOnly: true })using exclusive filesystem creation, so final creation cannot overwrite an existing piece. Ordinary Save still overwrites; asset preparation is not transactional.Add separate Google metadata, field-value, and Markdown-body generation functions under
llm/google/, preserving the existing final-metadata wrapper and package exports.Use Gemini 3.8 Flash and SDK 2.24.0. Build small reference-free field response schemas with
json-schema-traverse, already used by Ajv.Report best-effort progress, return only completed validated results, bound file/output sizes and processing polling, and attempt cleanup of known provider files.
Use ordinary SDK requests and per-request timeouts. No token previews, caller cancellation, overall generation deadline, SQLite generation results, or archive writes during generation. Accepted work finishes despite observer failure.
Reject incompatible CLI assistant options before loading a piece or calling the provider. Keep the CLI quiet and preserve its existing output/create/update behavior.
Verification
Node v26.4.0, pnpm 11.2.2; rerun immediately before commit:
pnpm lint— passpnpm check— passpnpm test— passpnpm build— pre-existing failure: web prebuild cannot findapps/web/config.yaml. This was recorded before the feature work; it is not a passing build gate. Core builds successfully.Deferred manual verification
The owner explicitly approved committing the core work and deferring real-provider checks until the UI is connected. Provider completion, abandoned-observer behavior, temporary-file cleanup, and production proxy/ingress behavior remain unverified manually; no passing result is claimed here.
Follow-up / issue #94
Proposed issue direction: interactive generation with live progress, one completed validated result, browser-only review, explicit Create or cursor insertion, and no durable generation jobs or SQLite outputs. Accepted work finishes after disconnect; abandoned results are discarded and cleanup still runs.
This PR does not implement the new web UI/endpoint. CLI progress display was removed from scope; issue #94 itself is unchanged.
Add write(markdown, { createOnly: true }) backed by exclusive filesystem creation. Preserve ordinary overwrite behavior and validate and serialize before writing. Update storage mocks, unit tests, and API documentation. Verified with Node v26.4.0 and pnpm 11.2.2: pnpm lint, pnpm check, and pnpm test pass. Core has 330 passing tests; coverage remains 100% statements/lines/functions and 99.84% branches. Known baseline failure, also reproduced before changes atb57b93bc: pnpm build fails in @luzzle/web prebuild because apps/web/config.yaml is missing. Core builds successfully; the repository build gate is not passing. Per owner review, use an optional write argument rather than writeNew and retain mocked unit coverage instead of the proposed real-filesystem integration suite.