v9.4.0 — Composition Mode (#128) #143
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/v10-composition"
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?
A motif becomes an authored artifact: manually order its entries and interleave prose/heading blocks so the published page and Markdown export read as an essay with evidence, not a reverse-chron dump.
Model
entry_motifs.position INTEGER(nullable) + amotif_blockstable (position,content,content_format). Entries and prose blocks share one ordered sequence.ORDER BY position NULLS LAST, created_at DESCand interleave blocks — an uncurated motif renders exactly as before (all-NULL positions → created_at DESC, no blocks).Backend
entries[].position+ ablocksarray.PUT /api/motifs/:id/composition(transactional reorder of the mixed list),POST/PATCH/DELETE /api/motifs/:id/blocks(sanitized on write). Writes gate onACCESSIBLE_PROJECTS_SQL.Frontend
Validation (dev server)
composition.test.ts— reorder persistence, uncurated-unchanged, block CRUD + sanitize, Markdown interleave).apitsc +appbuild green.Closes #128.
🤖 Generated with Claude Code