eric/narratio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Removed legacy interfaces and old documentation references to the previous on-disk layout

Browse Source
This commit is contained in:
Eric Rakestraw
2026-05-18 03:02:22 +00:00
parent 1054b64d9f
commit 2356688cb9
20 changed files with 150 additions and 759 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/development/workspace.md
View File

@@ -668,27 +668,18 @@ For v1.0, conservative retention is preferred:
* If cleanup is enabled, remove only documented run-scoped or spool-scoped paths.
* Local development audio inputs must never be deleted by workspace cleanup.
## 15. Migration From Existing Layout
## 15. Canonical-Only Layout Policy
Existing installations may currently use a simpler path such as:
```text
{workspace.root}/work/{session_id}/manifest.json
```
The v1.0 layout introduces campaign-aware session roots:
Narratio now supports only the canonical campaign-aware layout:
```text
{workspace.root}/work/{campaign_id}/{session_id}/manifest.json
{workspace.root}/work/{campaign_id}/{session_id}/runs/{run_id}/...
```
Migration options:
Legacy session-only layout compatibility is intentionally not implemented.
1. Best-effort automatic discovery of legacy session manifests.
2. A one-time migration command.
3. Clear release notes requiring users to move or regenerate workspace state.
For v1.0, it is acceptable to require explicit migration if the user base is small and the archive contains the authoritative durable outputs. However, the application should fail clearly when it detects an ambiguous legacy layout rather than silently creating duplicate state.
If legacy workspace data exists, operators should recreate or manually migrate that data outside Narratio before running v1.0 commands.
## 16. Documentation Updates Required