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

ticket: plan manifest profile phase two

Browse Source
This commit is contained in:
Keisuke Hirata 2026-05-30 01:59:42 +09:00
parent 9e99764927
commit 06c778a725
No known key found for this signature in database
2 changed files with 21 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
work-items/open/20260527-000022-manifest-profiles/item.md
View File

@ -7,7 +7,7 @@ kind: feature
priority: P2
labels: [manifest, profiles, nix, tui]
created_at: 2026-05-27T00:00:22Z
updated_at: 2026-05-29T16:52:47Z
updated_at: 2026-05-29T16:59:41Z
assignee: null
legacy_ticket: null
---

20
work-items/open/20260527-000022-manifest-profiles/thread.md
View File

@ -58,4 +58,24 @@ Non-blocking follow-up candidates:
- Build richer profile discovery/default selection and the full TUI profile picker.
---
<!-- event: plan author: hare at: 2026-05-29T16:59:41Z -->
## Plan
Continue implementation beyond the merged Nix profile foundation. The previous nested delegation stopped at a reviewable vertical slice; this phase should keep iterating until the work item acceptance criteria are materially closer to completion or a real blocker is found.
Phase 2 target:
- Add profile discovery/default selection instead of requiring only explicit `--profile <path>`.
- Support discovered-name selection with source disambiguation where needed, e.g. builtin/user/project/path semantics.
- Add or substantially advance the new Pod profile selection UX so a default can be displayed as `profile: coder (default)` and changed before spawn.
- Preserve the core design: selected Nix profile resolves to a standalone manifest/config artifact; ambient user/project manifests do not merge into it.
- Keep Pod resume using resolved snapshots rather than silent Nix re-evaluation.
- Keep secrets as references only.
The delegated orchestrator should not return merely because one slice is reviewable. It should internally review acceptance criteria, delegate sub-Pods as needed, and continue with the next reachable slice unless it hits a concrete design or technical blocker. Parent-side merge/close remains reserved for this parent Pod.
---