fix: remove stale pod guidance references

docs/design/overview.md

@@ -11,7 +11,7 @@ That rule shapes the crate split. The runtime can restart, attach, compact, or d
 - `llm-engine` owns model-facing turns: history append, retries, continuation, pruning/compaction mechanics, tool loops, and provider-independent callbacks.
 - `session-store` owns replayable append-only conversation/session logs.
 - `pod-store` owns current Worker metadata keyed by Worker name.
-- `protocol` defines the socket message boundary between clients and Pods.
+- `protocol` defines the socket message boundary between clients and Workers.
 - `client` contains reusable one-shot socket/runtime-command mechanics so lower crates do not depend on the product CLI.
 - `manifest` resolves Profiles, Manifests, model/provider references, scopes, prompts, and tool permission policy into a runtime contract.
 - `tools` implements built-in tools with bounded output and policy-aware execution.

docs/design/profiles-manifests-prompts.md

@@ -60,7 +60,7 @@ mcp = {
 
 Local stdio MCP servers are ordinary local executables running with the user's OS permissions. Yoi's feature flags, Plugin permissions, and MCP config validation are not an operating-system sandbox and cannot prevent filesystem/network/process side effects once a later lifecycle implementation chooses to spawn a configured server.
 
-## Spawned Pods
+## Spawned Workers
 
 `SpawnWorker.profile` is optional and resolves through defaults when omitted. The only concrete capability delegation in the tool call is `SpawnWorker.scope`, and it must be a subset of the parent's effective scope.
 

docs/development/dogfooding.md

@@ -19,7 +19,7 @@ After rebuilding and restarting during dogfooding, `current_exe()` can point at
 
 ## Multi-Worker work
 
-Use child Pods for scoped tasks and reviews, but keep orchestration decisions in visible project records. Do not merge, close, or clean up merely because a child notification arrived.
+Use child Workers for scoped tasks and reviews, but keep orchestration decisions in visible project records. Do not merge, close, or clean up merely because a child notification arrived.
 
 ## Secrets and logs
 

docs/development/workflows.md

@@ -19,7 +19,7 @@ Current workflow themes include:
 
 ## Child Pods
 
-Spawned Pods are useful for scoped implementation, review, or exploration. They are not independent project authorities.
+Spawned Workers are useful for scoped implementation, review, or exploration. They are not independent project authorities.
 
 A parent/orchestrator must verify: