Studio scene pack contract for runtime SCENE binary payload
This commit is contained in:
@@ -157,6 +157,25 @@ At minimum, the model should support fields equivalent to:
|
||||
- `applied_actions`
|
||||
- `blockers`
|
||||
|
||||
## Scene Bank Studio Integration Boundary
|
||||
|
||||
Scene Bank publication is a split workflow across Studio and packer.
|
||||
|
||||
Rules:
|
||||
|
||||
- Studio owns canonical scene validation and projection of the canonical Scene Bank request;
|
||||
- packer owns compilation of the canonical Scene Bank request into runtime `SCENE` output;
|
||||
- packer must report structural diagnostics against the canonical Scene Bank request artifact when that artifact is missing, malformed, or inconsistent with the locked format rules;
|
||||
- packer must not report editor-file parsing diagnostics as if `TMX` or `TSX` were direct runtime build inputs.
|
||||
|
||||
### Request Boundary Visibility
|
||||
|
||||
Rules:
|
||||
|
||||
- the Studio-to-packer handoff for Scene Bank publication must be a canonical request artifact or equivalent request surface derived from canonical Studio scene state;
|
||||
- if external compatibility files change without corresponding Studio import/update, packer must continue to treat the canonical request boundary as authoritative rather than silently reparsing editor files;
|
||||
- future supported editors may replace or coexist with Tiled-backed interoperability only if Studio continues to emit the same canonical request boundary.
|
||||
|
||||
## Asset Event Lane
|
||||
|
||||
The system includes a dedicated asset workspace event/reporting lane.
|
||||
|
||||
Reference in New Issue
Block a user