Release notes

Library surfaces and collaboration foundations landed for gallery filtering, vault stats, rendered version diffs, visual pins, and Claude HTML import.

• The gallery read model now composes weighted FTS with category filtering and lineage counts for adapted-artifact signals.
• Visual comments can store coordinate-anchored pins per artifact version, list them by version, resolve or reopen them, and audit every pin mutation without touching the sandboxed iframe.
• The vault read model reports member artifact, fork, version, and comment counts from existing tables, with version-pill data for each artifact.
• Import from Claude accepts pasted/exported HTML through the existing bundle ingest path and records artifact.imported audit events on successful imports.
• Library thumbnails and detail previews now stay version-specific, avoid double-prefixed URLs, and open local live views with dev-safe signed links.

Spec 008 completed design system centralization with tokenized surfaces, shared layout rhythm, and a calmer form-control pass.

• The design system now owns the shared app shell, page shell spacing, footer rhythm, and route surface widths from one tokenized pattern.
• The component library carries the form-control pass, including a compact checkbox overhaul that replaces the shadowed accent-tile treatment.
• Profile, audit, new-artifact, release-note, and state surfaces are aligned around the same page shell and neobrutalist component primitives.
• The release history now includes the completed bundle-format and fork/fill specs so past product changes are visible in-app.

Fork, lineage, fill, MCP write flows, and state commits made artifacts reusable without mutating their sources.

• Artifacts can be forked into new artifacts with immutable lineage back to the source version.
• Fill payloads and MCP write scopes let external agents create data-backed versions while preserving audit and rate-limit boundaries.
• The viewer can capture postMessage state changes and save them as a new version with the template unchanged.
• Lineage APIs, migration coverage, and browser checks protect the source artifact from mutation during fork and fill workflows.

Artifact bundle support introduced html, data, and manifest parts with safer ingestion and render contracts.

• Uploads now support the three-file artifact bundle shape: artifact HTML plus optional data.json and manifest.json.
• Bundle parts are stored, carried forward, and served with scoped raw routes so data-only changes can preserve the HTML part.
• Manifest metadata powers category and dependency surfaces while enforcing pinned dependency and CDN allowlist rules.
• Backfill, migration, CORS, CSP, and isolation tests cover legacy artifacts and the new bundle render path.

Completed v0.4 compliance fixes for share management, detail and folder polish, validation coverage, and local reliability.

• Share management now covers one-time copy, visibility changes, 7-day and 30-day expiry updates, never-expire cleanup, tracking, and revoke from the artifact.
• Detail and folder polish closes the equal-action row, copy embed, and Top level wording gaps.
• The v0.4 validation suite now directly checks share lifecycle, detail layout, folder quality, static metadata, and clean viewer runtime output.
• Local reliability fixes keep app.lvh.me dev sign-in, isolated previews, and worker shutdown behavior dependable during review.

Neobrutalist redesign with a gallery-first home, working prefix search, folder completion, and tag discovery.

• Gallery cards now open isolated view-origin previews with a separate details affordance.
• Search supports as-you-type prefix matching, deterministic sorting, collapsed filters, and active filter chips.
• Folders can be renamed, moved, browsed by child folder, and audited alongside artifact moves.
• Tags are keyboard-accessible discovery links from the gallery and artifact detail pages.

People, admin, bulk operations, search-first organization, and security hardening for member workflows.

• Admin user and people management gained invitation, role, disable, and audit surfaces.
• Bulk artifact actions cover move, archive, and tag operations with safer limits.
• Search and organization APIs gained folders, tags, metadata edits, and audit coverage.
• Authentication, API tokens, throttling, and cleanup operations were tightened for production use.

Initial MVP for uploading, viewing, versioning, and cataloging artifact HTML safely.

• Member authentication and the first artifact inventory shell shipped.
• Artifact upload, immutable versions, thumbnails, and detail pages established the core catalog.
• View-origin rendering separated live artifact bytes from the application origin.
• Basic comments, discovery, and operational documentation created the baseline workflow.