Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: delegate yoi worktree sparse exclusions

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 16:15:42 +09:00
parent 0cc81cfd4f
commit f6f10c7f9d
No known key found for this signature in database
2 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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

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

@ -56,4 +56,26 @@ Implementation-ready: keep `.yoi` as the project records marker, stop excluding
Ticket intake complete; workflow_state intake -> ready. Ticket intake complete; workflow_state intake -> ready.
---
<!-- event: implementation_report author: hare at: 2026-06-07T07:15:31Z -->
## Implementation report
## Delegation
Implementation delegated to child Pod `narrow-yoi-worktree-coder-20260607` in worktree `.worktree/narrow-yoi-worktree-sparse-exclusions` on branch `work/narrow-yoi-worktree-sparse-exclusions`.
This worktree intentionally uses the proposed narrower sparse rules:
- includes `.yoi` project records;
- excludes `.yoi/memory`, memory logs, ticket backend lock, and local/runtime paths.
Scope:
- Update `worktree-workflow` and `multi-agent-workflow` away from `.yoi` whole-directory exclusion.
- Define project-record vs generated-memory/local-runtime boundaries.
- Update role guidance/tests if they still say child worktrees exclude all `.yoi`.
- Do not implement memory-root detection; `memory-root-uses-yoi-memory-marker` follows after this.
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.
--- ---