Skip to content

Releases: henyjone/apsal-open

v0.16.0-beta.1

v0.16.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 22 Jul 17:05
6d63c7a

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.

v0.14.0

Choose a tag to compare

@github-actions github-actions released this 17 Jul 11:02
823f1cb

What's Changed

  • APSAL Studio 0.14: visual anchors and stage previews by @henyjone in #1

New Contributors

Full Changelog: v0.13.0...v0.14.0

APSAL Studio 0.13.0 — Controlled Variation

Choose a tag to compare

@github-actions github-actions released this 17 Jul 04:15

APSAL Studio 0.13.0

APSAL Studio 0.13 adds a controlled-variation strategy for complete photography sets. New nine-image sessions no longer default to one unchanged scene, look and lens language. They begin with a creator-visible choice between Chaptered Variation and Continuous Narrative.

Install or upgrade

codex plugin marketplace add henyjone/apsal-open --ref v0.13.0
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task. codex plugin list should show apsal-studio@apsal-open at 0.13.0.

What creators see

The first Direction card contains two selectable options:

  • 章节式丰富变化 / Chaptered Variation — recommended and selected by default for a new nine-image theme;
  • 连续叙事 / Continuous Narrative — for one core scene, one confirmed look and one causally continuous event.

Card options are now real keyboard- and touch-accessible buttons. Selecting one asks APSAL to revise the card and explain downstream effects; it never skips the required layer confirmation.

Chaptered Variation default

The nine-image set is organized as three chapters of three Jobs:

  • three related sub-scenes inside one coherent photographic world;
  • three coordinated looks, one locked inside each chapter;
  • nine distinct action-led body states with declared hands, gaze and physical consequence;
  • functional environmental-wide, full-action, natural-medium, emotional-close and hand/prop-detail perspectives;
  • stable identity, live-action medium, world physics, photographic grammar and color system.

Each image Prompt receives its exact scene/look lock, action, body state, chapter, nominal focal length and observable perspective purpose. The QA target separately checks what should vary and what must stay continuous.

Continuous Narrative

Continuous Narrative keeps one scene and one look while the event, action, gaze, hand plan, framing and focal perspective progress across nine Jobs. Changing strategy in Direction rebuilds World, Look, Event, Sequence, Camera and Quality Control proposals and invalidates stale downstream confirmations.

Compatibility

Protocol and Semantic Contract remain 0.3.0. Session schema remains 0.7.0. The strategy fields are additive for new sessions. Older 0.7 sessions without them preserve their prior generation intent; frozen themes, DNA assets, Prompt packages and run history are not rewritten. Static tests validate structure and deterministic compilation, not generated-image quality.

Release assets

  • apsal-studio-codex-plugin-v0.13.0.zip
  • apsal-studio-codex-plugin-v0.13.0.zip.sha256

Verify after download:

shasum -a 256 -c apsal-studio-codex-plugin-v0.13.0.zip.sha256

Read the complete usage guide, the 中文完整使用手册, or RFC 0009.

APSAL Studio 0.12.0

Choose a tag to compare

@henyjone henyjone released this 16 Jul 17:28

APSAL Studio 0.12.0

APSAL Studio 0.12 makes the creative cards carry the design work themselves. Every element card now contains the recommendation, the reason behind it, adjustable directions, concrete values, expected visual result, invariants and acceptance criteria. The surrounding chat no longer has to hold suggestions that disappear when the card opens.

Install or upgrade

codex plugin marketplace add henyjone/apsal-open --ref v0.12.0
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task, then confirm that codex plugin list shows apsal-studio@apsal-open at 0.12.0.

Default protagonist

When the brief does not specify another subject, new sessions propose a poised, distinctive East Asian adult female protagonist with reliable camera presence and broad compatibility across classical, contemporary, editorial and ceremonial makeup, hair and wardrobe.

Styling versatility is not identity mutability. APSAL locks facial geometry, adult age, natural skin, hair color and hairline, and body proportions. A theme keeps one confirmed look unless an observable event explicitly motivates a change. An explicit male-subject brief overrides the female default.

What appears in every card

  • My design proposal
  • Why this is recommended
  • Adjustable directions
  • Design purpose
  • Proposed values
  • Expected visual results
  • Must-preserve constraints
  • Acceptance criteria

Chinese sessions show these fields in creator-facing Chinese. CLI and IDE text fallback contains the same information.

Compatibility

Protocol and Semantic Contract remain at 0.3.0. Session schema remains at 0.7.0. Existing frozen themes, official DNA versions, Prompt packages and run history are not rewritten. The new protagonist contract applies to newly created Studio 0.12 sessions unless the creator overrides it.

Release files

  • apsal-studio-codex-plugin-v0.12.0.zip
  • apsal-studio-codex-plugin-v0.12.0.zip.sha256

Verify after downloading:

shasum -a 256 -c apsal-studio-codex-plugin-v0.12.0.zip.sha256

Full Changelog: v0.11.0...v0.12.0

APSAL Studio 0.11.0 — Chinese Card Localization

Choose a tag to compare

@henyjone henyjone released this 16 Jul 16:59

APSAL Studio 0.11.0

APSAL Studio now gives Chinese creators a fully localized card experience and uses a clearer, accessible celadon highlight hierarchy for important decisions.

Install

codex plugin marketplace add henyjone/apsal-open --ref v0.11.0
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task, then verify that codex plugin list shows apsal-studio@apsal-open at 0.11.0.

中文卡片变化

  • 五个创作层和十三个协议元素全部使用面向创作者的中文。
  • 中文卡片不再显示英文内部角色名、层编号、字段名、状态、来源、资源类型、资源层级、质量状态、语义标签或资源编号。
  • 七类官方资源拥有独立中文标题、摘要与核心约束。
  • 项目资源、个人资源和社区扩展资源使用安全中文回退,不会把英文机器字段直接暴露给创作者。
  • 内部稳定编号、版本、摘要和依赖仍保留,用于解析、校验和复现,但不进入中文卡片可见区域。

Highlight hierarchy

  • Current layer and card titles use the strongest celadon text.
  • Creative intent and recommendation reasons use a celadon side rule and tinted surface.
  • Important values use stronger color plus font weight.
  • Selected cards receive a visible inset state and filled action.
  • The primary layer confirmation action is filled; secondary revision actions remain outlined.
  • Focus rings, 44-pixel controls and reduced-motion behavior remain intact.

Compatibility

Protocol and Semantic Contract remain 0.3.0. Session schema remains 0.7.0. The localized fields are a presentation projection only: canonical themes, DNA content digests, Prompt compilation and photographic generation intent do not change.

Release files

  • apsal-studio-codex-plugin-v0.11.0.zip
  • apsal-studio-codex-plugin-v0.11.0.zip.sha256

Verify after download:

shasum -a 256 -c apsal-studio-codex-plugin-v0.11.0.zip.sha256

Full Changelog: v0.10.0...v0.11.0

APSAL Studio 0.10.0 — Bilingual Creator Interaction

Choose a tag to compare

@henyjone henyjone released this 16 Jul 13:49

APSAL Studio 0.10.0

APSAL Studio now offers complete Chinese and English creator interaction while preserving one shared APSAL Protocol, DNA Registry and photographic generation chain.

Install

codex plugin marketplace add henyjone/apsal-open --ref v0.10.0
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task, then verify that codex plugin list shows apsal-studio@apsal-open at 0.10.0.

Language behavior

  • Write in English and Studio uses English cards, questions, controls and explanations.
  • 使用中文输入,Studio 会使用中文卡片、问题、按钮和说明。
  • There is no mandatory first-run language screen.
  • If the first message is genuinely ambiguous, Studio asks once: English or 中文?
  • Say use English or 切换到中文 at any time to switch the current local session.
  • Switching language does not change DNA, confirmed creative decisions, theme or Prompt digests.

Prompt/Skill delivery

Every new theme package and migrated legacy package now contains:

PROMPT_GUIDE.md
PROMPT_GUIDE.en.md
PROMPT_GUIDE.zh-CN.md

The two complete guides operate the same frozen provider-neutral Prompts. APSAL still uses Codex built-in image generation one independent Job per turn, never asks for an image API key, and does not claim guaranteed returned pixel dimensions.

Compatibility

Protocol and Semantic Contract remain 0.3.0. The local five-layer session artifact remains schema 0.7.0 with an optional language object, so previous sessions remain readable. Legacy run takeover, Registry assets, DNA Extension Packs and existing Prompt/Skill packages continue to work.

Release files

  • apsal-studio-codex-plugin-v0.10.0.zip
  • apsal-studio-codex-plugin-v0.10.0.zip.sha256

Verify after download:

shasum -a 256 -c apsal-studio-codex-plugin-v0.10.0.zip.sha256

Full Changelog: v0.9.0...v0.10.0

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 16 Jul 13:14

APSAL Studio 0.9.0

APSAL Studio now completes both new-theme creation and legacy APSAL package takeover inside Codex. It does not call an image API or require an image API key.

Install in three steps

codex plugin marketplace add henyjone/apsal-open --ref v0.9.0
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task. Then choose one path:

  • New theme: 使用 APSAL Studio 创建一套九张东方极简窗边真人摄影主题。
  • Existing package: attach the ZIP and say 打开这个 APSAL 包并生成第一张图。

What happens next

  1. New themes confirm five creator layers and all thirteen protocol elements; old ZIPs recover Prompts and references by SHA-256.
  2. APSAL automatically creates a documented Prompt/Skill ZIP with positive, negative and full Prompts, references, rights, QA and checksums.
  3. Codex generates one independent photograph per turn. Inspect it and say 继续 for the next unfinished Job.

Requested 9:16, high quality and 2160×3840 remain creative delivery targets, not guaranteed returned pixel dimensions. Model visual QA and human visual QA remain separate.

Detailed instructions

Release assets

  • apsal-studio-codex-plugin-v0.9.0.zip
  • apsal-studio-codex-plugin-v0.9.0.zip.sha256
  • Plugin SHA-256: 99520d351fb26ace371accac9819fefc2e1b8aeff4d229a466b8aae55b517860

Protocol and Semantic Contract remain 0.3.0. Studio 0.4–0.8 assets and Skills remain readable.

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 16 Jul 12:51

Full Changelog: v0.7.0...v0.8.0

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 16 Jul 12:26

Full Changelog: v0.6.1...v0.7.0

APSAL Studio 0.6.1

Choose a tag to compare

@henyjone henyjone released this 16 Jul 11:45

APSAL Studio 0.6.1

APSAL Studio 0.6.1 is a presentation-only compatibility patch. DNA selection now uses compact text cards instead of image-led cards, so the creator can compare meaning, constraints and recommendation evidence without a decorative thumbnail dominating the decision.

Install

codex plugin marketplace add henyjone/apsal-open --ref v0.6.1
codex plugin add apsal-studio@apsal-open

Restart Codex or open a new task after installation.

Release assets

  • apsal-studio-codex-plugin-v0.6.1.zip
  • apsal-studio-codex-plugin-v0.6.1.zip.sha256
shasum -a 256 -c apsal-studio-codex-plugin-v0.6.1.zip.sha256

What changed

  • Interactive Character, World, Scene and Photo choices are text-only cards.
  • Cards prioritize stable ID/version, scope, core constraints, recommendation reasons, matched tags, rights, attribution and QA.
  • MCP no longer sends Base64 preview images in card payloads.
  • Registry previews remain background sidecars for rights review, Extension Pack validation and exchange.

No DNA, Prompt, theme, Protocol, Semantic Contract, generation setting or visual QA claim changed. The reference engine remains 0.6.0; the Studio presentation layer is 0.6.1.

Full Changelog: v0.6.0...v0.6.1