v0.16.0-beta.1

APSAL Creative Library 0.16.0

APSAL 0.16 turns Studio into a local-first creative project library while
keeping the Engine as the only semantic kernel.

The first public build is prerelease v0.16.0-beta.1. Internal protocol and
plugin artifacts remain version 0.16.0; the beta suffix identifies the
GitHub distribution, not a different project schema.

Versions

• APSAL Open Protocol: 0.4.0
• Project Protocol, Engine, and Codex plugin: 0.16.0
• APSAL Studio Desktop: 0.3.0
• Creative Library, Reference Analysis, and Share schemas: 0.1.0
• Semantic Contract: 0.3.0 (unchanged)

Creative flow

1. Import 1–24 reference images and record copyright, portrait,
   redistribution, AI-modification, and identity permissions.
2. analysis.next gives Codex one image or set-synthesis Job and a strict JSON
   schema. The Engine never calls a vision or image provider directly.
3. design.build_from_analysis compiles the complete five-layer,
   thirteen-element theme, Prompts, negative constraints, QA, and Skill.
4. Every creative expansion forks a child project with its parent snapshot
   digest and source assets. The parent revision and bytes stay unchanged.
5. Successful generated outputs enter the content-addressed library; failed
   Jobs stay recoverable and are never presented as completed output.
6. Public and private project packages include checksums and a static project
   page. Public packages exclude private references, local paths, nested
   private Skills, and tokens.
7. Social drafts require a digest-bound final confirmation. X uses the official
   API when a Keychain token exists and otherwise opens the official composer.
   Xiaohongshu always hands off to its official composer and remains
   awaiting_external_confirmation until an external completion is known.

Public interfaces

• Project: project.create_from_references, project.fork, project.export,
  project.import, explicit migration preview and copy migration.
• Analysis: analysis.start, analysis.next, analysis.record,
  analysis.status, design.build_from_analysis.
• Library: library.status, library.reconcile, library.list, library.get,
  library.update, library.archive, library.lineage.
• Share: share.draft, share.preview, share.confirm, share.publish,
  share.status.

The Codex MCP exposes creator-facing equivalents for all of these capabilities
and still includes the complete headless theme, generation, Registry and Studio
link surface. The 0.16 server exposes 50 tools.

Project layout

New Studio reference projects default to:

~/APSAL Projects/<project-name>-<project-id>/

Each project owns .apsal/project.json, .apsal/analysis/, .apsal/themes/,
.apsal/runs/, and .apsal/share/. The global ~/.apsal/library/ database and
objects are a rebuildable search/display projection, never the semantic source.

Migration

Opening a 0.15.0 project is read-only. project.migration_preview describes
the target and project.migrate performs an explicitly confirmed copy. The
source project is never silently rewritten.

Install the beta plugin

codex plugin marketplace add henyjone/apsal-open --ref v0.16.0-beta.1
codex plugin add apsal-studio@apsal-open

Open a new Codex task and verify that the plugin is enabled at 0.16.0. The
GitHub prerelease contains only the deterministic plugin ZIP and its SHA-256.
APSAL Studio Desktop 0.3.0 is built locally for ARM64 from
apps/apsal-studio; this release does not publish, sign or notarize a macOS
application.

See the English upgrade guide or
中文升级指南 for backup, local build,
copy migration, verification and rollback steps.

Security and publication boundaries

• Automatic authoring may skip routine design confirmations, but cannot skip
  reference rights, real-person identity, public release or social publishing
  confirmation.
• APSAL does not identify people. A real face cannot be locked without explicit
  portrait and identity permission.
• Share confirmation is bound to selected media, copy, platform and permission
  digest; any edit requires a new preview and confirmation.
• X OAuth material stays in macOS Keychain. No token enters a project, log,
  export, test fixture or Git.
• Xiaohongshu is a draft/composer handoff and remains awaiting external
  confirmation. Opening the official flow is never reported as publication.

Verification

The release gate runs the Python contract suite, deterministic package checks,
documentation/version/link checks, Studio production build, frontend tests and
Electron tests. CI uses mocked social delivery and never creates a real post.
Public-export tests reject references without redistribution permission, Vault
URIs, credentials and absolute local paths, and verify that a child fork does
not change the parent digest.

Known beta limits

• No APSAL cloud community, account, comments or moderation service.
• No background import of all historical Codex generated images.
• X API publication depends on a separately configured official developer app;
  composer handoff is the supported fallback.
• No unattended Xiaohongshu background posting.
• No publicly distributed signed/notarized macOS application in this beta.

Third party

The gallery/archive projection adapts MIT-licensed MOSA designs from commit
38be7f4c951b75ea032392a27abea1d2170b6bac. See
MOSA adaptation boundary and
third-party notices.