ticket: review yoi worktree sparse exclusions

.yoi/tickets/open/20260607-062902-narrow-yoi-worktree-sparse-exclusions/item.md

@@ -8,7 +8,7 @@ priority: P1
 labels: [worktree, workflow, memory, ticket, orchestration]
 workflow_state: ready
 created_at: 2026-06-07T06:29:02Z
-updated_at: 2026-06-07T07:15:31Z
+updated_at: 2026-06-07T07:28:48Z
 assignee: null
 legacy_ticket: null
 ---

.yoi/tickets/open/20260607-062902-narrow-yoi-worktree-sparse-exclusions/thread.md

@@ -79,3 +79,35 @@ Scope:
 The child should commit implementation work in the child worktree and report diff/tests. Merge, review, Ticket closure, and cleanup remain with the parent/human workflow.
 
 ---
+
+<!-- event: implementation_report author: hare at: 2026-06-07T07:28:48Z -->
+
+## Implementation report
+
+## Implementation report
+
+Coder Pod `narrow-yoi-worktree-coder-20260607` completed implementation in `.worktree/narrow-yoi-worktree-sparse-exclusions`.
+
+Commit:
+- `ee85b51 workflow: narrow yoi worktree sparse exclusions`
+
+Reported summary:
+- Updated `.yoi/workflow/worktree-workflow.md` so child worktrees may include tracked `.yoi` project records.
+- Replaced broad `.yoi/**` sparse exclusion guidance with narrower exclusions for `.yoi/memory`, logs, locks, local/runtime/cache/tmp/session/socket/pod state, and secret-like paths.
+- Updated validation guidance to allow `.yoi` while checking `.yoi/memory` and local/runtime/log/lock/secret-like paths are absent.
+- Added explicit Ticket edit policy: branch-local artifacts/dossiers may live in child worktrees; active orchestration progress and final review/approval/close stay main-workspace responsibilities.
+- Updated `.yoi/workflow/multi-agent-workflow.md` to stop describing `.yoi` as broadly excluded and to clarify child-worktree project-record boundaries.
+- Updated generated role guidance/tests in `crates/client/src/ticket_role.rs` and `crates/tui/src/multi_pod.rs`.
+- Did not implement memory root detection and did not recreate `.yoi/memory`.
+
+Reported validation:
+- `cargo test -p client ticket_role --lib`
+- `cargo test -p tui ticket_queue_notification --lib`
+- `target/debug/yoi ticket doctor`
+- `cargo fmt --check`
+- `git diff --check`
+- `nix build .#yoi`
+
+External review will be delegated before merge.
+
+---

.yoi/tickets/open/20260607-072708-builtin-workflow-knowledge-resources/item.md

@@ -0,0 +1,49 @@
+---
+id: 20260607-072708-builtin-workflow-knowledge-resources
+slug: builtin-workflow-knowledge-resources
+title: Builtin Workflow and Knowledge resources
+status: open
+kind: task
+priority: P2
+labels: [workflow, knowledge, resources, builtin]
+workflow_state: intake
+created_at: 2026-06-07T07:27:08Z
+updated_at: 2026-06-07T07:27:08Z
+assignee: null
+legacy_ticket: null
+---
+
+## Background
+
+Recent Orchestrator automation work embedded key workflow contracts as role-specific builtin guidance in generated prompts. This is sufficient for now, but it is not a full builtin Workflow/Knowledge resource system.
+
+Longer term, reusable Yoi workflows and curated guidance should be available as bundled builtin Workflow/Knowledge resources that can be resolved by slug and optionally overridden/extended by project/user records.
+
+## Goal
+
+Add builtin Workflow/Knowledge resources as first-class bundled resources while preserving project/user override capability.
+
+## Requirements
+
+- Define a bundled resource location for builtin Workflows and builtin Knowledge, e.g. under `resources/`.
+- Add resolver support for builtin Workflow/Knowledge slugs such as `builtin:multi-agent-workflow` or equivalent source-qualified identifiers.
+- Preserve project-authored records under `.yoi/workflow` and `.yoi/knowledge` as project overrides/extensions.
+- Define precedence between builtin, user, and project resources.
+- Make builtin resource resolution available to role/prompt generation and workflow invocation paths where appropriate.
+- Keep existing role-specific prompt guidance working; do not require a broad migration in the first pass.
+- Ensure builtin resources can be referenced without copying them into every workspace.
+- Document how users/projects override or extend builtin Workflow/Knowledge.
+- Add tests for resource lookup, override precedence, and missing-resource diagnostics.
+
+## Non-goals
+
+- Rewriting all current workflow prompts immediately.
+- Solving active workflow compaction persistence; that remains `preserve-active-workflows-across-compaction`.
+- Removing project `.yoi/workflow` / `.yoi/knowledge` support.
+
+## Acceptance criteria
+
+- Builtin Workflow/Knowledge resources can be resolved by explicit source-qualified slug.
+- Project/user resources can override or extend builtin resources according to documented precedence.
+- Existing project workflow files continue to work.
+- Tests cover builtin lookup and override behavior.

.yoi/tickets/open/20260607-072708-builtin-workflow-knowledge-resources/thread.md

@@ -0,0 +1,7 @@
+<!-- event: create author: LocalTicketBackend at: 2026-06-07T07:27:08Z -->
+
+## Created
+
+Created by LocalTicketBackend create.
+
+---