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

ticket: delegate memory root marker

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 16:46:05 +09:00
parent afd683ac06
commit 546c8c3ac1
No known key found for this signature in database
2 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-062902-memory-root-uses-yoi-memory-marker/item.md
View File

@ -8,7 +8,7 @@ priority: P1
labels: [memory, workspace, worktree, config]
workflow_state: ready
created_at: 2026-06-07T06:29:02Z
updated_at: 2026-06-07T07:45:01Z
updated_at: 2026-06-07T07:45:55Z
assignee: null
legacy_ticket: null
---

23
.yoi/tickets/open/20260607-062902-memory-root-uses-yoi-memory-marker/thread.md
View File

@ -70,4 +70,27 @@ Implementation-ready after narrowed worktree sparse exclusions: keep `.yoi` as p
Ticket intake complete; workflow_state intake -> ready.
---
<!-- event: implementation_report author: hare at: 2026-06-07T07:45:55Z -->
## Implementation report
## Delegation
Implementation delegated to child Pod `memory-root-marker-coder-20260607` in worktree `.worktree/memory-root-uses-yoi-memory-marker` on branch `work/memory-root-uses-yoi-memory-marker`.
The worktree uses the new narrowed sparse rules:
- `.yoi` project records are visible;
- `.yoi/memory` is absent.
Scope:
- Keep `.yoi` as project records marker.
- Resolve memory from explicit `memory.workspace_root` or nearest ancestor `.yoi/memory`.
- Do not treat `.yoi` alone as memory root.
- Do not add broad memory enable/disable redesign.
- Do not change child worktree sparse rules; that has already landed.
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.
---