refactor: rename pod crate to worker

resources/prompts/common/worker-orchestration.md

@@ -1,12 +1,12 @@
 ---
-## Pod orchestration
+## Worker orchestration
 
-When Pod-management tools are available, spawned Pod notifications are background signals for the parent to handle at a natural stopping point. Do not ignore routine follow-up, but do not interrupt the current user request unnecessarily.
+When Worker-management tools are available, spawned Worker notifications are background signals for the parent to handle at a natural stopping point. Do not ignore routine follow-up, but do not interrupt the current user request unnecessarily.
 
-The parent does not need to keep a turn open or call tools solely to wait for a notification. Do not use `sleep` or polling loops just to wait for Pod output; if there is no useful immediate work, return control and handle the child when notified or when the user next asks.
+The parent does not need to keep a turn open or call tools solely to wait for a notification. Do not use `sleep` or polling loops just to wait for Worker output; if there is no useful immediate work, return control and handle the child when notified or when the user next asks.
 
 Before treating delegated work as complete, read the child output and inspect concrete evidence such as worktree state, diff, and test results. Notifications are hints, not proof of completion.
 
 Peer Pods made visible by reciprocal metadata registration are not spawned children. Use peer messaging only as explicit communication; it does not grant scope, produce a child output cursor, imply parent ownership, or create child completion notifications. Peer sends require a live peer and do not auto-restore stopped peers.
 
-This guidance is not scheduler or auto-maintain authorization. Do not start workflows, merge or clean up work, close tickets, or bypass user/workflow authorization solely because Pod tools or notifications exist.
+This guidance is not scheduler or auto-maintain authorization. Do not start workflows, merge or clean up work, close tickets, or bypass user/workflow authorization solely because Worker tools or notifications exist.

resources/prompts/internal.toml

@@ -1,11 +1,11 @@
-# Pod internal prompts (builtin pack).
+# Worker internal prompts (builtin pack).
 #
 # Values are minijinja template strings. Use `{% include "$prefix/..." %}`
 # to pull in long text from the $yoi / $user / $workspace prompt
 # libraries.
 #
-# Every key here MUST correspond to a `PodPrompt` variant; missing or
-# extra keys cause a build-time error (see `crates/pod/build.rs`).
+# Every key here MUST correspond to a `WorkerPrompt` variant; missing or
+# extra keys cause a build-time error (see `crates/worker/build.rs`).
 
 [prompt]
 compact_system = "{% include \"$yoi/internal/compact_system\" %}"
@@ -66,19 +66,19 @@ The following workflows are advertised resident. When a user request matches one
 {{ entries }}\
 """
 
-pod_orchestration_guidance_section = "{% include \"$yoi/common/pod-orchestration\" %}"
+worker_orchestration_guidance_section = "{% include \"$yoi/common/worker-orchestration\" %}"
 
-ticket_event_companion_notice = "{% include \"$yoi/pod/ticket_event_companion_notice\" %}"
+ticket_event_companion_notice = "{% include \"$yoi/worker/ticket_event_companion_notice\" %}"
 
-spawn_pod_tool_description = """\
-Spawn a new Pod process to work on a delegated task. The spawner's write scope is reduced by the scope passed here; the spawned Pod receives its own socket and starts running `task` immediately. The spawned Pod outlives the spawner's current turn and can be contacted again through its socket path.
+spawn_worker_tool_description = """\
+Spawn a new Worker process to work on a delegated task. The spawner's write scope is reduced by the scope passed here; the spawned Worker receives its own socket and starts running `task` immediately. The spawned Worker outlives the spawner's current turn and can be contacted again through its socket path.
 
 Optional `cwd`: when provided, it is the child process/tool default working directory only. It must be an absolute existing directory covered by the child's delegated readable scope, and it does not change workspace/Profile/memory/Ticket roots or grant authority.
 
-Profile selection: `profile` may be omitted or set to `default` to use the effective child default profile, set to `inherit` to derive reusable child configuration from this Pod, or set to one of the registry selectors below. Raw/path profile selectors are not accepted by SpawnPod. `scope` is always the only delegated filesystem capability; profile scope is replaced by the explicit SpawnPod scope.
+Profile selection: `profile` may be omitted or set to `default` to use the effective child default profile, set to `inherit` to derive reusable child configuration from this Worker, or set to one of the registry selectors below. Raw/path profile selectors are not accepted by SpawnWorker. `scope` is always the only delegated filesystem capability; profile scope is replaced by the explicit SpawnWorker scope.
 
 Default profile: {{ default_profile }}
-Special selector: inherit — derive reusable model/worker/tool policy from the spawner while replacing pod.name and scope.
+Special selector: inherit — derive reusable model/worker/tool policy from the spawner while replacing worker.name and scope.
 Available registry profiles:
 {{ available_profiles }}{% if profile_diagnostic %}
 

resources/prompts/panel/orchestrator_idle_queue_notice.md

@@ -1,5 +1,5 @@
 <system-reminder>
-Workspace Dashboard observed that this Orchestrator Pod is idle while queued Ticket work is present.
+Workspace Dashboard observed that this Orchestrator Worker is idle while queued Ticket work is present.
 
 This is bounded attention only, not scheduler authority. Do not drain the queue automatically. Before implementation side effects, verify the Ticket state and record the normal `queued -> inprogress` acceptance through Ticket tools.