Initialize standalone sessions from native local authoring context

This commit is contained in:
2026-11-18 04:06:29 +00:00
parent 33d2ebf44c
commit 435ec79185
6 changed files with 126 additions and 12 deletions

View File

@@ -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`

View File

@@ -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.