AI media harness for planning, generating, and editing locally
TypeScript
Rename the settings file to polstudio.json in the docs too
Bittib504ee450e9f
diff --git a/README.md b/README.mdindex 323852f..7e31bd3 100644--- a/README.md+++ b/README.md@@ -29,13 +29,13 @@ Each project is a normal folder owned by the user:```textMy project/-├── pols.json+├── polstudio.json├── assets/├── generated/├── exports/└── cache/```-`pols.json` is schema-versioned and contains the creative brief, render settings, asset metadata, and timeline structure. The Rust shell validates it before reads and writes; the web build uses validated local-storage records as a development fallback.+`polstudio.json` is schema-versioned and contains the creative brief, render settings, asset metadata, and timeline structure. The Rust shell validates it before reads and writes; the web build uses validated local-storage records as a development fallback.The web fallback seeds three deterministic showcase projects on first launch. Remove the `polstudio.web-projects.v1` local-storage entry to restore that initial demo library.diff --git a/docs/architecture.md b/docs/architecture.mdindex c3ce89c..fb8f692 100644--- a/docs/architecture.md+++ b/docs/architecture.md@@ -6,11 +6,11 @@ In a blind side-by-side evaluation, a first-time creator should pick PolStudio o## Project boundary-A project is a portable folder. Its source of truth is `pols.json`; every path stored in that file is relative to the project root. Generated and imported content lives below that root so moving or archiving the folder does not break it.+A project is a portable folder. Its source of truth is `polstudio.json` (older projects may still hold `pols.json` or `polstudio.project.json`, both of which still open). Paths in that file are one of two kinds: project-relative for what the folder contains — everything generated here, and imported images — and an absolute `sourcePath` for imported video and audio, which are never copied. A rush is tens of gigabytes and duplicating it to call the folder portable costs the user that disk for nothing.```textproject-folder/- pols.json+ polstudio.jsonmedia/imported/media/generated/references/diff --git a/src/components/workspace/MediaThumbnail.tsx b/src/components/workspace/MediaThumbnail.tsxindex b9d18be..b8da776 100644--- a/src/components/workspace/MediaThumbnail.tsx+++ b/src/components/workspace/MediaThumbnail.tsx@@ -92,7 +92,7 @@ export function MediaThumbnail({ folderPath, asset }: { folderPath: string; assevoid (async () => {let url: string | null = null;try {- url = await readMediaFileUrl(folderPath, asset, asset.mimeType);+ url = await readMediaFileUrl(folderPath, { relativePath: asset.relativePath, sourcePath: asset.sourcePath }, asset.mimeType);// Browser preview: there is no project folder, so there is nothing to// show and nothing has gone wrong. The kind icon stands in.if (!url) return;@@ -106,7 +106,7 @@ export function MediaThumbnail({ folderPath, asset }: { folderPath: string; asse}})();return () => { live = false; };- }, [cacheKey, folderPath, asset, asset.mimeType, asset.kind]);+ }, [cacheKey, folderPath, asset.relativePath, asset.sourcePath, asset.mimeType, asset.kind]);if (poster) {return <span className="media-thumb media-thumb--poster">diff --git a/src/lib/settings.ts b/src/lib/settings.tsindex a4f15ef..ef21d0c 100644--- a/src/lib/settings.ts+++ b/src/lib/settings.ts@@ -3,7 +3,7 @@* The video engine and its weights are a property of THIS computer, not of a* project: a project folder copied from another machine carries paths that do* not exist here. They therefore live in localStorage rather than in- * pols.json, and are merged into `providerSettings.vidfab` only+ * polstudio.json, and are merged into `providerSettings.vidfab` only* on the way into a Tauri command — never on the way into a saved config.* Keep it that way: writing them into a project file would put one machine's* disk layout into a file the user is invited to move, copy, and share.@@ -131,7 +131,7 @@ export function saveAgentProvider(provider: ProviderId): void {/* --- Panel layout ----------------------------------------------------------How the media panel lays its footage out. A working habit, not a property ofany one project, so it lives beside the engine paths rather than in- pols.json — a project file the user may copy to another machine should not+ polstudio.json — a project file the user may copy to another machine should notcarry one editor's panel preference with it. */export type MediaLayout = "grid" | "list";