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
@@ -278,6 +278,34 @@ advances. DEV MUST identify images from an older build/session as stale during
edits/rebuilds. The previous execution MUST stop before rebuilding artifacts
that it uses. Capture/build correlation MUST NOT introduce code snapshots.
### Lifecycle, cleanup and recovery observations
Shared observations MUST distinguish no session, unknown state, an explicitly
unbooted session after reset, confirmed boot, observed guest state, lost process
and confirmed process-tree termination. An acknowledgement alone does not prove
an unavailable native state. Guest termination and process termination remain
different facts. Reset requires an explicit boot before intentional advancement.
Control return MUST revoke task authority before cleanup. Results and the DEV
snapshot independently expose authority, task revocation, project closure, cleanup
`NOT_REQUIRED`, `PENDING`, `COMPLETED` or `FAILED`, and structured cleanup failure.
A cleanup failure MUST retain the manual guard and MUST NOT reactivate the task.
An explicit subsequent reclaim may acknowledge actual completed cleanup.
Advance observations preserve requested and known completed frames, session/build,
last confirmed canonical frame, capture staleness and native structured causes.
Unknown progress is null, not zero. Guest fault, native host watchdog, media
refusal/action requirement, invalid protocol, transport loss and consumer deadline
remain distinguishable without parsing messages. Zero completed frames does not
prove that an unsuccessful advance had no internal effects.
The DEV inspector MUST show current authority/cleanup, current-session known facts
and the last operation conclusion separately, including media/native details,
unavailable inspections and recovery preconditions. Recovery descriptions are
read-only; they MUST NOT add manual headless Play/input, implicit replay, boot,
media discard, a new authority owner or a larger execution budget.
## 8. Local MCP Admission and Functional Surface
Concrete tool names, input schemas, response envelopes and HTTP lifecycle are
@@ -425,3 +453,35 @@ DEV and the existing build surface render the canonical public view: summary, co
Language queries use a 10000 ms execution budget from admission (including queue/read/connect/initialize/analysis/query) plus a 2000 ms cleanup response window. Cancel pending requests and owned socket/listener/executors. shutdownNow is not evidence of termination. If a child remains alive, the caller may return the primary failure with workerTerminated=false, but the managed worker remains alive/busy until that child actually stops. Manual control and successor admission cannot be released early. Preserve the first failure and attach cleanup state rather than replacing it with a later failure.
Conformance distinguishes model/projection tests, source-navigation tests and real JavaFX desktop inspection. Model tests alone do not establish visual inspection. The integrated corpus uses production compiler/packer/LSP and authenticated MCP; controlled invalid IR and stubborn-child/protocol fixtures are explicitly identified test injections.
## Visual evidence and human baseline review
DEV MUST offer a project evidence inspector for retained publications and reports.
It MUST show expected/actual/diff, original pixel coordinates and RGBA samples,
ROI/masks, normalized tolerance/alpha parameters, hashes, metrics, provenance and
current staleness. Observation during an agent grant MUST NOT add input or Play.
A human MAY explicitly select and authorize an external PNG reference; the adapter
MUST canonicalize the selection and enforce its exact project-bound grant through
symlinks. Otherwise file import MUST remain inside the canonical project. Import
or a rejected comparison MUST NOT approve a baseline. Baseline promotion MUST be
an explicit human action under the existing manual mutation lease, recording the
previous revision, new revision and reference origin. Grant/revocation and failed
or cancelled comparison MUST leave reviewed baselines unchanged.
Revoked tasks MUST NOT read historical evidence. A fresh authorized task in the
same project MAY read it; another project MUST NOT. The local bound human inspector
MAY remain read-only during a grant. Project closure MUST deny further service
access while preserving published bytes for a later authorized reopen.
## Project guest tests and production Play
The project test surface MUST offer explicit target/media selection and shared
start/query/cancel/transcript services, showing case states passed, failed, not_run
and infrastructure_failure, assertions, checkpoints, native observations and run
completion/timeout/cancellation. Human mutation MUST use existing manual authority;
while an agent holds control the surface is observation-only. DEV retains its
grant/reclaim/observation role. Normal Play MUST always select production, never
the last test build. No automatic source/barrel patches, larger budgets, private
access or implicit personal-card use are permitted. This is the accepted contract
for PLN-0172; UI/execution delivery remains in progress.