feat(studio): deliver asset authoring and automation workflows
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:
@@ -453,3 +453,62 @@ Its requirements apply in addition to this chapter; pause/resume remain independ
|
||||
A result success evaluates its payload once. Propagation and handle evaluate their operand once; only the selected recovery arm runs. Error remapping returns the enclosing error; traps are not caught. Animation advances only through explicit ticks. Queries/emissions are pure with respect to playback; repeated play/select resets the selected clip even when its name is unchanged.
|
||||
|
||||
See [Core Sprite and Animation](27.%20Core%20Sprite%20and%20Animation%20Specification.md) for the complete API, ranges, state table and conformance obligations.
|
||||
|
||||
## Isolated guest tests preserve lifecycle and visibility
|
||||
|
||||
The selected test entrypoint MUST own exactly one program lifecycle. Existing
|
||||
MemcardBoot, bootstrap, Init and Frame rules and budgets remain normative. Test
|
||||
support MUST use normal PBS visibility and exist only in explicitly selected roots.
|
||||
Work MUST be distributed across guest frames; the host MUST advance in bounded
|
||||
blocks and inspect tagged logs between blocks, including completion/failure when
|
||||
available. Timeout, cancellation and explicit completion are distinct.
|
||||
|
||||
Test-only support MUST emit versioned JSON via existing sdk/log and the target's
|
||||
declared logTag. Every envelope contains schemaVersion 1, suiteId, eventId, kind,
|
||||
nullable caseId for suite events, and payload. Kinds are suite_start, case_start,
|
||||
assertion, checkpoint, case_end and suite_end. Assertions MUST retain name/message,
|
||||
optional expected/actual and boolean passed. Checkpoints MAY reference retained
|
||||
visual evidence IDs; ordinary game log text MUST NOT be interpreted as test events.
|
||||
|
||||
Host validation MUST enforce declared tag, schema/types, event order, suite/case
|
||||
identity, expected case catalogue and consistent duplicate event IDs. Reconsulting
|
||||
a native sequence MUST NOT reapply it. Unread gaps or sequence discontinuity, malformed/conflicting events,
|
||||
session/epoch changes and native faults MUST prevent success. Case states are
|
||||
passed, failed, not_run and infrastructure_failure. Pass requires a nonempty suite,
|
||||
at least one assertion, explicit suite completion, every expected case completed,
|
||||
no failed assertion and no loss/protocol/fault condition. Fault alone, missing cases
|
||||
or an empty suite MUST NOT become a successful assertion report. Accepted contract
|
||||
implementation is in progress under PLN-0172.
|
||||
|
||||
### Structured assertion detail and host retention
|
||||
|
||||
Optional expected/actual values MUST retain independent availability flags, so an
|
||||
omitted value differs from an observed null. Native sequence/frame/timestamp,
|
||||
source/tag/application and the original event MUST remain correlated in transcript
|
||||
entries. Wall timestamps MUST NOT determine the verdict. An optional boolean
|
||||
passed on case_end/suite_end MAY explicitly reject that case/suite; it MUST NOT
|
||||
override a failed assertion. Non-boolean completion flags are invalid. Checkpoint
|
||||
artifact IDs MUST pass current project admission before inclusion as valid links.
|
||||
|
||||
The initial host accumulator retains at most 16 MiB and 100000 native records per
|
||||
run. Exceeding a host retention bound MUST report explicit infrastructure failure
|
||||
with the bound and retained position, never silently discard records or pass.
|
||||
These are host transcript bounds and do not alter firmware budgets. The installed
|
||||
isolated-tests example uses target-only helpers with complete versioned JSON
|
||||
literals and predicate booleans; it assumes no new guest string formatting ABI.
|
||||
|
||||
### 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.
|
||||
|
||||
Reference in New Issue
Block a user