feat(studio): deliver asset authoring and automation workflows
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/pr-master There was a failure building this commit

Add shared human/task asset batches with reviewed atomic publication, explicit
reference rebinds, ownership inspection and qualified glyph/scene budgets.
Expose the same authoring and capacity results through Assets and MCP.

Deliver isolated guest test targets, retained visual evidence and immutable
runtime lifecycle/control observations. Preserve provider qualification and
installed authoring examples alongside the completed discussion lessons.

Close AGD-106 coordination and the delivered discussion workflows through
housekeeping, updating lesson references and preserving qualification limits.
Sound remains outside the asset delivery wave.

Validation: 579 module tests and 31 additional desktop, process and installed
checks passed; native glyph/scene 16/17 boundaries qualified. Discussion
validation passed after housekeeping.
This commit is contained in:
2026-11-11 01:21:25 +00:00
parent b351f2e582
commit 1471b427f1
325 changed files with 61179 additions and 323 deletions
@@ -167,3 +167,26 @@ This specification is complete enough when:
Expose the effective selected glyph layout through Packer API: asset UUID and stable artifact ID to glyph ID/fingerprint mapping from the same composition used for pack. Exclude `animations.studio.json` from glyph candidates and binary payload. The sidecar references existing identities and does not create an asset type, header or animation binary format. Reorder/removal/content drift requires explicit revision-checked rebind by authoring services; never retarget by path/order.
See the [complete animation contract](../studio/12.%20Animation%20Authoring%20Specification.md).
## Revision-checked authoring batches
The packer project write lane MUST support previewed atomic batches spanning
declared asset bytes, manifests, registry and related Studio metadata. Preview
leaves published state unchanged. Revalidate the complete input revision and
relevant source hashes immediately before commit. Shared reads/builds/writes
MUST observe the old complete batch or the new complete batch, with durable
journal recovery before admission after interruption.
Registration continues to allocate identity through this registry. An
uncommitted staged allocation is not an issued published identity. Identical
reimport MUST preserve UUID/AssetId, stable artifact IDs, selected order, output
hashes and references; append MUST NOT renumber existing glyphs/artifacts.
Incompatible replacement, removal or size/order/layout change requires complete
affected-reference analysis and explicit rebind in the same batch.
Cancellation/failure before commit leaves the old published state. After the
commit point, retained result/recovery reports the applied state rather than
claiming rollback. Request/batch correlation supports response-loss recovery
without acting as authority. The write lane coordinates participating services;
external writers that ignore it are detected by revision revalidation rather
than claimed to be serialized.