Initialize standalone sessions from native local authoring context
This commit is contained in:
@@ -373,6 +373,9 @@ Rules:
|
||||
- `--audio-dir` and `--audio-s3-prefix` are mutually exclusive.
|
||||
- if campaign `session_template_file` is configured, `session init` renders it.
|
||||
- generated session YAML must be concrete (no unresolved `{{ ... }}` placeholders).
|
||||
- template imports and relative resources resolve in the template's local
|
||||
authoring context. Generated output contains standalone effective values.
|
||||
- relative `--audio-dir` paths resolve from the invocation directory.
|
||||
|
||||
### `session restore`
|
||||
|
||||
|
||||
@@ -146,6 +146,10 @@ documentation checks. This requires no licensing change or new release gate.
|
||||
|
||||
## 5. P2: Give session initialization the correct authoring context
|
||||
|
||||
Status: Complete. Rendered templates load with native local context and imports;
|
||||
local and remote products are standalone effective documents. Relative CLI audio,
|
||||
import removal, placeholder/identity, and initialization race checks pass.
|
||||
|
||||
Stage: 4, interacting with materialization and command validation in Stages
|
||||
6, 11, and 12.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user