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
@@ -374,3 +374,34 @@ This document is healthy when:
3. the minimum result contracts are explicit,
4. `run` no longer acts as a normative public concept,
5. and caller-specific contexts are constrained without opening semantic drift.
## Isolated build target context
An omitted build target MUST select `production` and preserve existing source,
output, AppMode and appId behavior. A test target is a separate explicit selection,
not a machine profile. `prometeu.json` MAY declare `testTargets` schemaVersion 1
with a targets array. Each target MUST have a unique non-production id, a project-
relative entrypoint file, sourceRoots, supportRoots, exact exclusions, expected
case IDs and a uint16 logTag. Paths MUST be normalized project-relative paths and
canonical admission MUST prevent escapes through symlinks. Unknown IDs, duplicate
IDs/cases/paths and exclusions that are not exact selected source files MUST fail.
Selection MUST propagate through the API, resolved workspace, project descriptor,
source crawling, frontend/lifecycle context, compile/build pipeline, pack/shipper
and result. The same dependency/import resolver and asset graph MUST be used.
Only selected roots/support and exact exclusions determine the effective source
set; diagnostics MUST retain original paths and source revisions. Included invalid
files MUST NOT disappear through implicit exclusion. Each selected test program
MUST have one lifecycle belonging to its declared entrypoint.
Test output MUST be immutable per target/build in
`.studio/test-builds/<targetId>/<buildId>/`. Artifacts in use MUST NOT be overwritten.
The usable build identity MUST be published only after complete successful output;
failed/cancelled builds MUST NOT become bootable. Provenance MUST include selected
target/entrypoint, effective source/configuration/dependency/asset hashes and their
revision. Normal Play MUST always request production, irrespective of the last test
build. No production source/barrel is edited or patched to select a test target.
This is the accepted DEC-0094 contract. Target propagation and structured execution
remain in progress under PLN-0172; declaring this contract does not advertise an
implemented capability in installed tools.