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
@@ -314,3 +314,42 @@ 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).
## Qualified global bank budgets and publication
Bank-content format limits and global residency limits are separate checks.
The final deterministic packer preload list is the authority for effective
slots per bank type; individual glyphs, logical scenes and stages do not add
bank slots. Report existing, build-included, effective-preload and potential
dynamic views separately. Cold scene dependencies follow the existing runtime
residency contract, preserving AssetId identity rather than converting it into
a slot. Potential dynamic excess is a warning about possible loads, not proof
of simultaneous residency.
Global limits MUST come from a distributed versioned profile qualified against
the exact selected installed executable. The profile includes contract/runtime
versions, executable digest, per-type limits and retained positive/boundary
evidence. Publish the initial 16-slot profile only after the selected executable
passes 16/17 qualification for glyph and scene. Sound is outside this wave;
profiles MUST contain only bank types with actual boundary evidence. An absent/incompatible
profile is unknown, never unlimited or a silent constant/family fallback.
With a known profile, validate effective preloads before final cartridge
publication. Excess MUST retain the previous valid output and report the type,
limit, responsible slots/AssetIds/paths and profile. A build without a selected
compatible profile may publish with explicit unknown qualification, but MUST
NOT claim qualified capacity. Managed execution requires a matching profile and
valid budget through the same shared preflight. Runtime selection or effective
input changes invalidate the previous check. Record the checked profile and
input revision in build provenance; ordinary builds MUST NOT inspect runtime
checkout sources to obtain limits.
The bundled macOS arm64 profile `macos-arm64-cli-0.1.0-18423f7-glyph-scene-v1`
is qualified for glyph=16 and scene=16 against exact dispatcher, headless and
desktop component hashes. Runtime version `0.1.0` alone does not select it.
The distributed catalog includes hashed boundary evidence. Managed start and each
headless BOOT MUST recheck the selected component fingerprints, the complete
profile/evidence identity, and hashes of actual cartridge files. Admission reads
the serialized `assets.pa` table/preload; auxiliary JSON never replaces it.
A changed executable, evidence or build requires a new qualified build.