merge: sync orchestration before queue 00001KXKMX0QM

.yoi/tickets/00001KXKJGYGD/item.md

@@ -2,7 +2,7 @@
 title: 'Remove workflow tracking and workflow resources'
 state: 'inprogress'
 created_at: '2026-07-15T19:02:13Z'
-updated_at: '2026-07-15T19:55:42Z'
+updated_at: '2026-07-15T21:25:42Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-07-15T19:54:36Z'

.yoi/tickets/00001KXKJGYGD/thread.md

@@ -123,3 +123,207 @@ Next action:
 Dashboard queue authorization was inspected, no blockers were found, and an accepted plan was recorded. Moving queued Ticket to inprogress before creating worktree or spawning role Pods.
 
 ---
+
+<!-- event: implementation_report author: orchestrator at: 2026-07-15T20:46:17Z -->
+
+## Implementation report
+
+Implementation progress report:
+
+- Coder Pod `yoi-coder-00001KXKJGYGD-workflow-removal` completed implementation in `/home/hare/Projects/yoi/.worktree/00001KXKJGYGD-remove-workflow-tracking` on branch `work/00001KXKJGYGD-remove-workflow-tracking`。
+- Implementation commit: `d801b2698bb1b3d07e0d49af71b2e4777efd3f6e` (`refactor: remove workflow machinery`)。
+- Orchestrator inspected worktree status, branch log, commit stats, `git diff --check 83ad7506..HEAD`, and grep checks for ActiveWorkflow / Workflow resource references. Worktree was clean and diff check passed。
+
+Implementation summary:
+- Removed model-visible `ActiveWorkflowList`, `ActiveWorkflowComplete`, and `ActiveWorkflowCancel` tools。
+- Removed Worker active-workflow durable state, extension snapshotting, compaction/rehydration handling, and prompt re-injection paths。
+- Removed Workflow registry/resource loading and `/workflow-slug` invocation behavior。
+- Deleted `crates/workflow` crate and tracked `resources/workflows` resources。
+- Removed `WorkflowInvoke` from protocol/TUI/web generated protocol surfaces and slash workflow completion behavior。
+- Removed `.yoi/workflow` memory/workspace authority and workflow usage-source handling。
+- Updated prompts/docs/config/role launch code to remove resident workflow and workflow invocation wording。
+- Updated Ticket role launch/config handling to use typed role launch prompts without workflow slugs。
+- Added bounded old-session handling: old persisted `kind: "workflow"` `SystemItem`s deserialize as `LegacyIgnored` and replay only a non-authority ignore diagnostic。
+- Confirmed broad first-class Skills support was not implemented in this Ticket。
+
+Files/resources touched include:
+- `crates/worker/src/active_workflow.rs` removed。
+- `crates/worker/src/workflow/mod.rs` removed。
+- `crates/workflow/*` removed。
+- `resources/workflows/*` removed。
+- Protocol/TUI/web generated protocol surfaces updated。
+- Prompt/docs/config references updated。
+
+Coder-reported validation passed:
+- `rg "ActiveWorkflow|active_workflow|Active workflow"`: no matches。
+- `rg "resources/workflows|\\.yoi/workflow|workflow invocation|Resident workflows"`: no matches。
+- `git diff --check`
+- `cargo test -p session-store --lib --tests`
+- `cargo test -p worker --lib --tests`
+- `cargo test -p yoi --tests`
+- `cargo check -p yoi`
+- `yoi ticket doctor`
+- `nix build .#yoi --no-link`
+
+Next action:
+- Route to external Reviewer Pod before merge/close decisions。
+
+---
+
+<!-- event: review author: reviewer at: 2026-07-15T20:53:02Z status: request_changes -->
+
+## Review: request changes
+
+External review result: request_changes
+
+Evidence reviewed:
+- Implementation worktree was clean。
+- `rg "ActiveWorkflow|active_workflow|Active workflow"` and `rg "resources/workflows|\\.yoi/workflow|workflow invocation|Resident workflows"` were clean。
+
+Blockers:
+
+1. `WorkflowInvoke` web/generated surfaces remain active。
+   - `web/workspace/src/lib/generated/protocol.ts:82` still includes `{ kind: "workflow_invoke", slug: string }`。
+   - `web/workspace/src/lib/workspace/console/composer-command.ts:191` still emits `workflow_invoke`。
+   - `web/workspace/src/lib/workspace/console/model.ts:322` still handles it。
+   - `composer-command.test.ts:28` still expects it。
+   - This violates workflow resource/invocation removal acceptance。
+
+2. Relevant tests fail after removal。
+   - `cargo test -p ticket --lib scaffold_config_includes_backend_and_all_fixed_roles -- --nocapture` fails because `crates/ticket/src/config.rs:1115-1120` still asserts role `workflow = ...`。
+   - `cargo test -p tui --lib live_system_item_workflow_appends_system_message_block -- --nocapture` fails because `crates/tui/src/app.rs:3326-3340` still expects legacy workflow SystemItem rendering instead of ignored/drop/diagnostic behavior。
+   - This violates validation acceptance。
+
+3. Stale docs/config wording remains。
+   - `docs/manifest.toml:283-293` still documents loading `skills.directories` “as Workflows,” conflicting with prompt/docs cleanup and Workflow authority removal。
+
+Non-blocking note:
+- Core Rust ActiveWorkflow/resource deletions appear largely in place, and broad new Skills support was not introduced in the inspected diff。
+
+---
+
+<!-- event: implementation_report author: orchestrator at: 2026-07-15T21:07:01Z -->
+
+## Implementation report
+
+Follow-up implementation progress report after request_changes:
+
+- Coder Pod `yoi-coder-00001KXKJGYGD-workflow-removal` completed the focused review-blocker fix in `/home/hare/Projects/yoi/.worktree/00001KXKJGYGD-remove-workflow-tracking`。
+- Follow-up commit: `d30dca2d99812f457324b91fd3549f4f126b6d7c` (`fix: remove remaining workflow invoke surfaces`)。
+- Orchestrator inspected worktree status, branch log, commit stats, `git diff --check 83ad7506..HEAD`, and grep checks. Worktree was clean and diff check passed。
+
+Fix summary:
+- Removed stale web `workflow_invoke` surfaces:
+  - `web/workspace/src/lib/generated/protocol.ts`
+  - `web/workspace/src/lib/workspace/console/composer-command.ts`
+  - `web/workspace/src/lib/workspace/console/model.ts`
+  - `web/workspace/src/lib/workspace/console/composer-command.test.ts`
+- Updated generated TypeScript protocol to match Rust protocol without `WorkflowInvoke`。
+- Removed stale Ticket role scaffold test expectation for `workflow = ...`。
+- Replaced stale TUI workflow SystemItem rendering test with legacy workflow SystemItem ignore-path test。
+- Removed docs/config wording that advertised loading Skills as Workflows。
+- Stabilized Worker discovery restore-planning test by sharing the runtime-dir sandbox used by allocation tests。
+
+Coder-reported validation passed:
+- `rg "ActiveWorkflow|active_workflow|Active workflow"`: no matches。
+- `rg "resources/workflows|\\.yoi/workflow|workflow invocation|Resident workflows|workflow_invoke"`: no matches。
+- `git diff --check`
+- `cargo test -p ticket --lib scaffold_config_includes_backend_and_all_fixed_roles -- --nocapture`
+- `cargo test -p tui --lib live_legacy_workflow_system_item_is_ignored -- --nocapture`
+- `cargo test -p session-store --lib --tests`
+- `cargo test -p worker --lib --tests`
+- `cargo test -p yoi --tests`
+- `cd web/workspace && deno task check && deno task test`
+- `cargo check -p yoi`
+- `yoi ticket doctor`
+- `nix build .#yoi --no-link`
+
+Knowledge removal Ticket `00001KXKP2A71` remains queued and will be re-routed after this Workflow removal Ticket is merged/closed, per human preference to proceed after completion rather than combined branch。
+
+---
+
+<!-- event: review author: reviewer at: 2026-07-15T21:10:11Z status: request_changes -->
+
+## Review: request changes
+
+Focused re-review result: request_changes
+
+Evidence:
+- Prior Rust/TUI test blockers are fixed:
+  - `cargo test -p ticket --lib scaffold_config_includes_backend_and_all_fixed_roles` passes。
+  - `cargo test -p tui --lib live_legacy_workflow_system_item_is_ignored` passes。
+- `ActiveWorkflow` / workflow resource greps over `crates web resources docs` are clean。
+- `workflow_invoke` is removed from generated protocol/composer/model。
+- Legacy workflow SystemItems are ignored in TUI。
+- `docs/manifest.toml` no longer says Skills load “as Workflows”。
+
+Remaining blocker:
+- Slash workflow completion path remains active, violating acceptance item for removing workflow resource/invocation/completion surfaces。
+- `web/workspace/src/lib/workspace/console/composer-completion.ts:1,4,38,82-83` still treats `/` as workflow completion。
+- `web/workspace/src/lib/workspace/console/composer-completion.test.ts:35` still asserts `completionTokenAt("run /work")?.kind === "workflow"`。
+- `web/workspace/src/routes/w/[workspaceId]/+page.svelte:354-361` still posts `token.kind` to the completions endpoint, and result type still allows `"workflow"` at `+page.svelte:48-49`。
+- `crates/protocol/src/lib.rs:604-608,619` comments still advertise `/ -> Workflow` and workflow resolvers。
+
+Blocker: remove the remaining slash workflow completion surface and stale protocol comments/types, without introducing hidden Workflow compatibility。
+
+---
+
+<!-- event: implementation_report author: orchestrator at: 2026-07-15T21:23:24Z -->
+
+## Implementation report
+
+Second follow-up implementation progress report after request_changes:
+
+- Coder Pod `yoi-coder-00001KXKJGYGD-workflow-removal` completed the remaining slash workflow completion fix。
+- Follow-up commit: `0b56052a447adeb12ee641f1136d121431fbd798` (`fix: remove workflow completion surface`)。
+- Orchestrator inspected worktree status, branch log, commit stats, and `git diff --check 83ad7506..HEAD`; worktree was clean and diff check passed。
+
+Fix summary:
+- Removed `/` as a web console completion sigil。
+- Web console completions now only recognize commands, file refs, and Knowledge refs。
+- Removed `workflow` from web console completion result typing。
+- Updated route-side completion response typing to exclude `workflow`。
+- Updated web completion tests so slash text remains plain text / no completion token。
+- Removed stale Workflow completion/resolver wording from protocol comments。
+- Did not add hidden Workflow compatibility or broad Skills replacement。
+
+Coder-reported validation passed:
+- `rg "ActiveWorkflow|active_workflow|Active workflow"`: no matches。
+- Focused completion-surface grep for `workflow_invoke`, workflow completion kind, slash Workflow resolver wording, `resources/workflows`, `.yoi/workflow`, `workflow invocation`, `Resident workflows`: no matches。
+- Focused web/protocol grep for `kind.*workflow`: no matches; remaining project-wide `kind: "workflow"` mentions are only legacy persisted `SystemItem` ignore tests for bounded compatibility。
+- `git diff --check`
+- `cd web/workspace && deno task check && deno task test`
+- `cargo test -p yoi --tests`
+- `cargo check -p yoi`
+- `yoi ticket doctor`
+- `nix build .#yoi --no-link`
+
+Next action:
+- Request focused re-review of the remaining workflow completion blocker and overall acceptance before merge/close decisions。
+
+---
+
+<!-- event: review author: reviewer at: 2026-07-15T21:25:42Z status: request_changes -->
+
+## Review: request changes
+
+Focused re-review result: request_changes
+
+Evidence:
+- Slash workflow completion blocker appears fixed。
+- Focused greps for `workflow_invoke`, workflow completion/resolver wording, `kind.*workflow`, `resources/workflows`, `.yoi/workflow`, `workflow invocation`, and `Resident workflows` in protocol/web/resources/docs were clean。
+- Web console completion no longer exposes workflow invocation。
+- ActiveWorkflow/resource greps remain clean。
+- Reviewer did not see broad new Skills support beyond existing manifest/config docs。
+
+Remaining blocker:
+- A stale TUI unit test still uses a legacy `"kind": "workflow"` SystemItem as an active task-store snapshot carrier and now fails because workflow SystemItems are ignored。
+- Location: `crates/tui/src/app.rs:3568-3600`, including comment at `3587-3588`, JSON kind at `3591`。
+- Failing command: `cargo test -p tui --lib live_system_snapshot_replaces_task_store -- --nocapture`。
+- Failure at `crates/tui/src/app.rs:3599` (`left: 1`, `right: 4`)。
+- This leaves relevant tests failing and contradicts bounded legacy workflow behavior / test cleanup expectation。
+
+Required fix:
+- Update the test fixture to use a non-legacy active SystemItem kind or otherwise align it with workflow ignore semantics。
+
+---

.yoi/tickets/00001KXKP2A71/artifacts/orchestration-plan.jsonl

@@ -0,0 +1,2 @@
+{"id":"orch-plan-20260715-202731-1","ticket_id":"00001KXKP2A71","kind":"after","related_ticket":"00001KXKJGYGD","note":"この Ticket は Knowledge removal 自体には blocker relation がないが、現在 `00001KXKJGYGD` が inprogress で Workflow tracking/resource removal を実装中。両者は `crates/worker` prompt/context、`crates/protocol`/session item、resource/docs cleanup、および Workflow required Knowledge dependency 周辺で重なる。Ticket body も Workflow required Knowledge dependency は Workflow removal 側で消える前提としているため、`00001KXKJGYGD` の review/merge/close 後に開始する。","author":"orchestrator","at":"2026-07-15T20:27:31Z"}
+{"id":"orch-plan-20260715-202739-2","ticket_id":"00001KXKP2A71","kind":"waiting_capacity_note","note":"Queue routing inspected. `00001KXKP2A71` is concrete and has no typed blocker relation, but it should not be started in parallel with active `00001KXKJGYGD`: both remove old context/resource machinery and likely touch shared prompt/context/session/protocol/resource/docs surfaces. Running both now would create conflict and review-boundary risk. Leave queued until `00001KXKJGYGD` is approved/merged/closed, then re-route Knowledge removal before Skills support `00001KXKMX0QM`.","author":"orchestrator","at":"2026-07-15T20:27:39Z"}

.yoi/tickets/00001KXKP2A71/item.md

@@ -2,7 +2,7 @@
 title: 'Remove Knowledge support'
 state: 'queued'
 created_at: '2026-07-15T20:04:08Z'
-updated_at: '2026-07-15T20:27:02Z'
+updated_at: '2026-07-15T20:27:51Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-07-15T20:27:02Z'

.yoi/tickets/00001KXKP2A71/thread.md

@@ -30,4 +30,38 @@ Marked ready by `yoi ticket state`.
 Ticket を `workspace-panel` が queued にしました。
 
 
+---
+
+<!-- event: decision author: orchestrator at: 2026-07-15T20:27:51Z -->
+
+## Decision
+
+Routing decision: hold_queued_due_conflict_with_active_removal_work
+
+Reason:
+- Dashboard queue authorization was inspected, and this Ticket is concrete with no outgoing blocker relation。
+- However, `TicketList(inprogress)` shows active Ticket `00001KXKJGYGD` (`Remove workflow tracking and workflow resources`) currently in implementation with Coder Pod running。
+- This Knowledge removal Ticket and Workflow removal Ticket likely touch overlapping surfaces:
+  - `crates/worker` prompt/context/resident injection paths。
+  - `crates/protocol` / `crates/session-store` reference/system-item state paths。
+  - resource cleanup under prompts/resources/docs。
+  - Workflow required Knowledge dependency, which this Ticket body explicitly says is expected to disappear via Workflow removal。
+- Starting this Ticket now would create avoidable merge conflicts and make reviewer acceptance boundaries ambiguous。
+- Therefore this pass leaves the Ticket `queued` and does not record `queued -> inprogress`, create a worktree, or spawn role Pods。
+
+Evidence checked:
+- Ticket body / thread / relations。
+- `TicketRelationQuery(00001KXKP2A71)`: incoming `depends_on` from Skills support Ticket `00001KXKMX0QM`; no blocker for this Ticket。
+- `TicketOrchestrationPlanQuery(00001KXKP2A71)`: no prior records; recorded `after 00001KXKJGYGD` and waiting note in this pass。
+- `TicketList(inprogress)`: `00001KXKJGYGD` active。
+- Orchestrator worktree status and worktree list: active Workflow removal worktree exists。
+- Visible Pods: Workflow removal Coder Pod is running。
+
+Next action:
+- Wait for `00001KXKJGYGD` to be reviewed, merged, validated, and closed。
+- Then re-route `00001KXKP2A71` before starting dependent Skills support `00001KXKMX0QM`。
+
+Escalate if:
+- Human explicitly wants Knowledge removal and Workflow removal combined in one branch/worktree, or accepts parallel conflict/review-boundary risk。
+
 ---