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
@@ -231,3 +231,73 @@ Retries MUST use capped exponential backoff (2–30 seconds), reset after connec
and stop at extension shutdown. Connection state MUST be visible without recurring
error popups. Explicit manual mode MAY use configured host/port for other hosts.
The server's project binding validation remains authoritative.
## Persistent visual evidence
Visual evidence MUST be retained separately from session restoration in
`.studio/evidence/`. Immutable publication directories contain PNG objects and a
publication record, including comparison reports and reviewed baseline revisions.
The application filesystem adapter MUST stage and integrity-check complete objects
and publish the directory atomically. Incomplete staging MUST NOT be listed and
MAY be cleaned under the store lock on reopen. Rebuild, release, shutdown and
project/application closure MUST preserve completed publications.
The byte quota MUST be configurable and default to 512 MiB per project. Admission
MUST serialize concurrent publishers, include object and publication metadata
bytes, and refuse before publication with used/required/limit. It MUST NOT evict
evidence or replace a baseline to admit new data. Deletion MUST be explicit,
authorized and refuse while another report or baseline references the publication.
Each artifact MUST retain an opaque ID, SHA-256 of original bytes, size, MIME,
dimensions and available project/task/operation/client-request/build/session/frame
provenance. Current staleness MUST be a separate observation, never a metadata
rewrite. Imported references MUST identify their external origin without invented
runtime identities. Report and baseline history MUST remain immutable.
## Isolated guest test artifacts
Test build output MUST live in `.studio/test-builds/<targetId>/<buildId>/`; test
run media/transcript identity MUST live under `.studio/test-runs/<runId>/`. These
are separate from session restoration and the production build output. Successful
builds MUST retain immutable target/configuration/source/dependency/asset provenance.
Incomplete or cancelled output MUST NOT publish a usable build identity. Test media
MUST be disposable and explicit; default/personal card paths MUST NOT be reused.
Closing/reopening a process for persistence proof MUST retain the same selected
disposable image and distinguish RAM, accepted commit and demonstrated durability.
Each run retains media.json with the explicit mode/creating image identity and
result.json with its immutable completion/verdict, native causes, provenance and
cleanup observation. Reopen accepts only a service-owned disposable-create run,
never an arbitrary media path or a personal/default-image alias. These records
are historical results, not restored task authority or permission to resume work.
## Recoverable asset batches and ownership
Asset batch staging, journals, source grants and retained request/result
correlation MUST remain separate from session restoration. The project-local
batch store is `.studio/asset-batches/`; ownership/dependency declarations are
separate versioned authoring metadata at `.studio/asset-ownership.json`.
These stores MUST NOT duplicate registry authority over AssetId, UUID, location
or build inclusion. Restoring a journal/result MUST NOT restore task authority
or an external source grant.
A revision covers the relevant project/asset manifests, the authoritative
`assets/.prometeu/index.json`, ordered composition, Studio metadata including
animation bindings, declared ownership/dependencies and relevant input-byte
hashes. Missing expected inputs are explicit revision facts. Every preview
declares all asset/manifest/registry/metadata/input changes before publication.
Revalidation immediately before commit MUST reject changed inputs.
Staging and a durable recoverable journal MUST precede publication. Shared
readers/writers MUST recover pending publication before accessing project truth.
Before the commit point, failure/cancellation leaves the old complete state;
after it, recovery and result queries report the new complete applied state,
including after a lost response or late cancellation. Never expose an
intermediate batch as committed. The service detects external changes during
revalidation; it does not serialize external writers that ignore Studio
coordination. Request correlation records MUST NOT act as access credentials.
PNG sources inside the canonical project use current project read authority.
External PNGs require an opaque project-bound grant issued by explicit human
source selection. Validate canonical scope, expected bytes and PNG bounds before
staging, then revalidate relevant source bytes at commit. A path, hash or
caller-supplied claim alone is not an external-source grant.