docs: remove obsolete local profile override guidance

docs/design/profiles-manifests-prompts.md

@@ -25,9 +25,9 @@ A resolved Manifest is the concrete contract used to create or restore a Worker.
 
 Source/partial layers may omit fields. Resolved manifests should be explicit enough that Worker creation does not depend on ambient configuration later changing under it.
 
-`--manifest <path>` exists as an explicit low-level escape hatch. Normal fresh startup should select a Profile through `profiles.toml` / builtin defaults rather than ambient manifest cascades.
+`--manifest <path>` exists as an explicit low-level escape hatch. Normal fresh startup selects a `builtin:*` or `project:*` Profile from the Backend-managed Workspace Config revision rather than applying an ambient manifest cascade.
 
-For normal Profile/default startup, a workspace may add `.yoi/override.local.toml` as a final local manifest layer. Yoi discovers the nearest ancestor `.yoi/override.local.toml` from the workspace base used for profile resolution, resolves relative paths in that file against its containing `.yoi` directory, and applies it after the selected Profile and builtin defaults. This file is intended for machine-local choices such as provider/model, worker language, prompt pack, and permission policy tweaks; it is ignored by git via the repository `*.local.*` rule. It is not applied in explicit `--manifest <path>` mode, and it cannot set `worker.name` because Worker identity remains a runtime input.
+Project Profiles are evaluated from the revisioned Virtual Config's Decodal source/import closure. The Backend packages that closure into a digest-bound Profile source archive, delivers it with the resolved launch bundle, and the Worker persists the resulting Manifest for restore. Files below the Workdir are not implicit Profile override layers.
 
 ## Local stdio MCP server declarations
 
@@ -77,7 +77,7 @@ Prompts live under `resources/prompts` so builtins, project overrides, and user
 
 The prompt layer should explain policy and behavior, but it should not smuggle volatile state into model context. Runtime facts that affect later turns must still go through history.
 
-Builtin resources should be embedded at compile time. User/project profiles, explicit profile paths, prompt overlays, provider/model overrides, and explicit manifests remain filesystem-based.
+Builtin resources should be embedded at compile time. Project Profiles and prompt overlays belong to the Backend-managed revisioned Workspace Config and travel as digest-bound source archives. User Profile registries, provider/model catalog overrides, and explicit low-level Manifests remain filesystem-based where those local resolution paths are used.
 
 ## Why this separation matters
 

docs/development/plugin-development.md

@@ -224,13 +224,13 @@ The expected authoring flow is Rust-first: generate the starter, edit `src/lib.r
 
 ## Enabling a Plugin in a workspace
 
-Enablement belongs in the resolved Profile/config path for the workspace. For local dogfooding or private experiments, use the ignored local overlay rather than committing secrets or local paths:
+Enablement belongs in the resolved Profile/config path for the workspace. Add it to the project Profile source selected by the Backend-managed, revisioned Workspace Virtual Config. Ambient files below the Workdir are not a Profile override layer and are not read when the Worker starts. Keep raw secrets and machine-local paths out of the Profile; refer to separately managed secrets where a capability supports them.
+
+The following TOML shows the equivalent low-level Profile/config artifact shape; it is not an ambient workspace override file:
 
 ```toml
-# .yoi/override.local.toml
-
-[features]
-plugins = true
+[feature.plugins]
+enabled = true
 
 [[plugins.enabled]]
 id = "project:example.echo"

docs/report/2026-06-14-session-jsonl-partial-write-restore-failure.md

@@ -49,4 +49,4 @@ The corrupted `tool_result` was manually replaced with a synthetic repair record
 ## Related fixes made during investigation
 
 - Added safer SSE parse diagnostics in `agen` so future provider-stream failures include HTTP status and selected safe response headers.
-- Enabled local trace via `.yoi/override.local.toml` and manually set `record_event_trace = true` in the `yoi-orchestrator` metadata snapshot for future restores.
+- Enabled local trace through the workspace configuration used at the time and manually set `record_event_trace = true` in the `yoi-orchestrator` metadata snapshot for future restores.