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
@@ -257,3 +257,22 @@ 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).
## Batch composition, ownership and dependency boundaries
Authorized PNG import, bank creation/registration, ordered composition,
build-inclusion and preload/contract changes MUST reuse existing declaration,
registry and canonical scene-request rules through the shared batch service.
No agent-specific manifest/index writer or second packer is introduced. External
source grants and expected hashes are validated before publication.
Generated-output ownership and dependency metadata MUST be declared and
queryable by asset/batch. It describes producer, output path, input asset edges
and stale dependent state without replacing registry identity. Only explicitly
requested internal batch operations execute. Metadata MUST NOT invoke shell,
external generators, ROM importers or automatic transitive regeneration.
Composition changes MUST preserve no-op/append identities and expose affected
animation/scene/metadata references for explicit incompatible rebind. Canonical
scene layers retain cold glyph AssetIds; a batch MUST NOT reinterpret them as
runtime slot numbers or synthesize hidden helper exports.