Joey-nexuandJoey
f1a0b60c6c
* chore: unify product name display to OpenDesign repo-wide Rename the user-facing product name from "Open Design" to "OpenDesign" across documentation, web/desktop UI strings, i18n locales, prompts, plugin/skill/design-system content, changelogs, and specs, matching the landing-page rename already in flight. Deliberately excluded so installed-app identity stays untouched: - packages/release PRODUCT_NAME and everything derived from it (app bundle names, installer/registry identity, updater feeds) - tools/pack, tools/release, apps/packaged, landing page (PR #6983) - mocks/ recorded traces and LICENSE - test fixtures and comments that encode real on-disk install paths (Open Design.app, Program Files\Open Design, AppData paths) Validated with pnpm guard, pnpm typecheck, and targeted web/desktop/host test runs over the renamed strings. * fix(web): keep two-letter author monogram for CamelCase brand names authorInitials split words on whitespace only, so the renamed single-token author name "OpenDesign" produced a one-letter monogram. Treat lower-to-upper CamelCase boundaries as word breaks so the avatar fallback stays "OD". * fix(release): restore spaced Windows source artifact names in win.ps1 tools/pack still derives builder outputs from the unchanged PRODUCT_NAME ("Open Design"), so the asset script must look for the spaced filenames. Matches the mac/mac-intel/linux asset scripts, which were already kept on the original names. --------- Co-authored-by: Joey <236967869+joeylee12629-star@users.noreply.github.com>
3.2 KiB
Externally Prepared Workspaces
Parent: architecture.md · Related: plugins-spec.md · agent-adapters.md
OpenDesign supports OD-owned project storage and folder-backed projects. Folder-backed projects need explicit provenance so OD can tell apart user-selected local folders from disposable workspaces prepared by an external orchestrator.
The boundary is intentionally narrow: OD may read and write the workspace it is given, produce inspectable design outputs, and report enough provenance for callers to act on the result. Source checkout state, pull-request creation, deployment, publishing, and writeback policy remain outside OD unless a future feature deliberately owns that workflow.
Contract
Workspace metadata separates storage from provenance:
- Storage answers where OD reads and writes files.
od-owned: OD-owned project files under the normal data/project directory.folder-backed: files live at an external filesystem root.
- Folder provenance answers who prepared a folder-backed workspace and who owns follow-up actions.
user-local: a user-selected folder that OD edits in place.orchestrator-scratch: a disposable folder prepared by an external orchestrator. OD may read and write the scratch workspace, but source authority and writeback stay outside OD.
This keeps OD local-first and integration-friendly without expanding its responsibility into source-control, deployment, or writeback policy.
Metadata Shape
Callers should mark scratch workspaces declaratively on project metadata:
{
"baseDir": "/tmp/od-run-123/workspace",
"importedFrom": "folder",
"orchestratorWorkspace": {
"kind": "scratch",
"sourceLabel": "checkout:main",
"sourceRef": "main@abc123",
"baseRevision": "abc123",
"writeback": "external"
}
}
The orchestratorWorkspace fields are provenance, not authority. OD may surface them in run status, diagnostics, result manifests, and telemetry. It must not infer permission to mutate an external source from them.
Git And Safety
OD should not maintain a broad git command firewall for externally prepared scratch workspaces. The orchestrator owns source checkout policy, credentials, remote configuration, branch selection, and writeback. OD should treat git state inside a scratch workspace as implementation detail unless a specific skill or artifact explicitly asks for a diff.
Local user folder imports have different provenance. When a user points OD directly at their own folder, OD is editing that folder in place. It is reasonable for OD to provide narrow UX warnings or preflight checks for that local mode, but those checks must not be framed as the sandbox boundary for externally prepared scratch workspaces.
Result Boundary
The stable output boundary is a result package:
- run identity and terminal status;
- workspace storage and provenance supplied by the caller;
- project files and artifact manifests OD can enumerate;
- event-log location when configured;
- errors, exit code, signal, and cancellation state;
- optional diff or patch metadata when a future caller asks OD to compute it explicitly.
The package describes what OD produced. It does not apply the result to any source workspace.