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
@@ -159,6 +159,34 @@ Build and advance admission MUST return a promptly queryable operation identity.
## Conformance Gates
Runtime observations and control observations are neutral immutable API values.
The process adapter validates native state, fault, media and error payloads; Core
retains project/task/operation/request correlation and authorization independently.
Neither JavaFX nor MCP may infer native phases, fabricate unknown progress or
implement recovery by replaying commands. Passive observation getters MUST perform
no native IO and MUST be safe to read while the authority monitor is held.
An operation-final observation MUST remain unchanged by a later state query,
reset, rebuild or shutdown. A separate current-session observation carries the
latest known facts. Every retained native snapshot carries its own source and
observation time, so an earlier state is not mislabeled as a later observation.
Failed follow-up inspection MUST retain the original native cause and record the
missing observation separately. Runtime wire codecs remain in application adapters; the
API supplies plain Java values and the JavaFX adapter presents those values.
Observation updates MUST serialize with process-loss invalidation: late native
progress/state cannot resurrect a lost process. Inspection admission MUST serialize
with shutdown; unavailable inspection during closing is reported without sending
a competing native query.
Diagnostic defaults and immutable value trees belong to the neutral Studio API.
Studio's bounded diagnostic aggregation belongs to the existing Core shipper
module; it MUST preserve whole-issue/count/UTF-8 budgets and producer fields.
Project-bound diagnostic source reads belong to the existing Core project module,
through `DiagnosticSources` exposed by the project session. JavaFX only presents
values and requests read-only navigation through that port; it MUST NOT perform
filesystem admission, read source bytes or serialize diagnostic wire payloads.
The architecture is conformant only when all of the following hold together:
- API and core compile without JavaFX, Spring, HTTP/MCP SDKs or concrete transport DTO dependencies;
@@ -221,3 +249,111 @@ The app compiler gateway translates complete warnings and BuildException payload
A shared public view contains issues, summary and context. Detail projection is limited to 1024 whole issues and 1 MiB of UTF-8 JSON issues. At a boundary, include a whole prefix, report partial detail coverage and LIMIT_EXCEEDED with budgets/total count, and retain full authoritative counts/evaluation separately. No issue field may be silently cut. UI and MCP consume this same view; underlying producer results remain complete.
Conformance: DiagnosticPayloadTest, StructuredShipperTest, StructuredDiagnosticsIntegrationTest and the compiler attribution/conversion regressions.
## Visual evidence service boundaries
The Studio API MUST expose neutral artifact, RGBA8, comparison, bounded reading,
publication and baseline-revision values and storage/codec ports. Core MUST own
comparison and task/operation orchestration; concrete filesystem, PNG and wire
codecs belong to application adapters. JavaFX MUST present the shared result.
Persistence MUST resolve a terminated operation by operationId/clientRequestId
and copy exactly its retained runtimeResult.capture. It MUST NOT call advance or
capture again. Publication requests MUST deduplicate by request identity and full
parameters; changed parameters MUST conflict. A lost response MUST be recoverable
from retained publication identity without guest replay. Mutations MUST use the
existing project worker or human manual lease; no second runner is introduced.
Comparison MUST expand PNG samples losslessly to RGBA8 without gamma/perceptual
correction or resize. Coordinates are top-left; ROI/masks are half-open rectangles
validated against original dimensions without clipping. Masks exclude their union
inside the ROI, counting overlaps once. An empty compared region is invalid. Alpha
policy MUST be explicit compare/ignore, and RGB MUST be compared even at zero
alpha. Defaults are exact: channel limit zero, differing-pixel allowance zero.
Tolerant comparison declares an integer channel limit 0..255 and nonnegative
allowed differing-pixel count. A pixel differs when any compared channel exceeds
that limit; the maximum channel error records the observed error before tolerance.
Dimension mismatch MUST be an explicit comparison rejection, distinct from invalid
parameters, decode, storage and authority errors. Reports MUST retain normalized
parameters, both original byte hashes, expected/actual/diff IDs, verdict, compared
and differing-pixel counts, maximum error and original-coordinate difference
bounds (null without differences). The diff MUST distinguish excluded pixels
(transparent black), compared pixels within tolerance (opaque green), and differing
pixels (opaque red/yellow). It MUST retain original image dimensions/coordinates.
## Shared isolated guest test service
Target selection MUST propagate through the existing project/API/compiler/shipper
services and resolver; the host test service MUST reuse existing task authority,
operationId/clientRequestId deduplication, cancellation and worker termination.
It MUST NOT introduce another resolver, runner authority, guest ABI or larger
budgets. Test-only support and ordinary PBS visibility MUST preserve production
source/barrel bytes and identity. Usable test builds MUST be exclusive and immutable
per target/build, retaining effective source/configuration/dependency/asset hashes.
The application adapter MUST validate negotiated log_read before executing a test
guest. It translates typed native get_logs records to neutral log pages with lossless
uint64 session/epoch/cursor/retention information. Core MUST accumulate tagged
versioned events, validate ordering/catalogue/duplicates/loss, and produce the same
case/assertion/checkpoint/run result for all adapters. It MUST read logs after each
bounded frame block and at completion/failure when available, without automatic
advance replay or destructive draining. Timeout, cancellation, native failure and
explicit suite completion MUST remain distinct; cancelled results are final only
after actual worker termination. Checkpoint references retain original evidence
identity from the shared visual service. The project Tests workspace and task MCP
tools consume one shared service. Manual runs hold the existing execution lease;
task runs use the existing automation worker. A retained manual test runtime blocks
grant/production execution until explicit cleanup. A provider correction requires
its own scoped authorization before runtime writes/builds.
## Shared asset authoring, revisions and capacity
The neutral API owns immutable batch requests/previews/results, revision and
conflict values, affected references/rebinds, generated-output ownership graphs,
producer diagnostics and separate content/global budget values. Core owns shared
authority admission and orchestration over existing asset, composition, metadata,
animation and packer services. Packer owns the project write lane and atomic
recoverable publication. App adapters own canonical file authorization,
serialization and distributed runtime-profile loading/identity verification.
JavaFX and MCP render the same API projection.
Human mutations MUST enter the existing manual guard; task mutations MUST enter
the existing current-task/project worker and recheck revocation at execution.
Inspection remains available under its read authority. Preview does not commit.
Commit is explicit, revision-checked and deduplicated by project/task/request ID
and full parameters. Identical retries return the retained result; changed
parameters conflict. Knowing a batch/request ID cannot restore revoked access.
All shared readers, including build and animation readers, participate in packer
publication exclusion/recovery; an MCP wrapper cannot bypass this boundary.
The application distributes capacity profiles by contract version, runtime
version and exact verified executable digest, together with qualification
evidence for every bank type it explicitly qualifies. The first profile covers
glyph and scene only; sound qualification is deferred. There is no runtime-family fallback
or ordinary-build access to runtime checkout sources. Missing, malformed or
mismatched qualification is unknown. Core's one budget/preflight projection is
consumed by shipper, headless and desktop execution. Unqualified builds may be
produced, explicitly marked unknown; managed execution requires the matching
qualified profile and valid effective budget.
The final packer preload list is authoritative. Runtime selection/input changes
invalidate earlier qualification and require rechecking. Build provenance MUST
include the profile and input revision actually checked. A known excess MUST
fail before cartridge publication, retaining the previous valid output.
### Guest producer continuity and native retention
Every structured guest event payload MUST include a zero-based contiguous integer
ordinal; suite_end MUST include eventCount counting all unique events including
itself. Retries with the same event identity/content are idempotent. Missing or
inconsistent ordinals/final counts fail as infrastructure errors, even if native
sequences remain contiguous. Native overflow records historical eviction; only
unread gap or actual continuity loss causes a retention failure. Preserve the
overflow observation separately.
Encoded guest messages MUST fit 256 UTF-8 bytes and stay within the unchanged
10 messages/application/frame budget, including ordinary application logs. The
runner drains every pending native page before another bounded advance. Native
continuity alone cannot detect events dropped before ring insertion. No new guest
ABI, formatting facility or increased execution/logging budget is introduced.