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

ticket: plan nix profile implementation delegation

Browse Source
This commit is contained in:
Keisuke Hirata 2026-05-30 01:09:28 +09:00
parent 75a333fa3b
commit 1d64c50cf2
No known key found for this signature in database
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -4,4 +4,24 @@
Migrated from TODO.md entry without a legacy ticket file. No legacy review file was present at migration time. Migrated from TODO.md entry without a legacy ticket file. No legacy review file was present at migration time.
---
<!-- event: plan author: hare at: 2026-05-29T16:09:27Z -->
## Plan
Implementation will proceed through a child orchestrator Pod in a dedicated worktree as an experiment in nested Pod delegation.
Initial implementation target:
- Introduce Nix profile resolution as a new manifest source before the existing manifest cascade.
- Start with explicit path-based profiles; discovered-name/default selection and rich TUI picker can be staged after the core resolver if necessary.
- Provide a minimal bundled Nix helper that can produce a typed resolved manifest/config artifact.
- Keep existing TOML manifest loading as compatibility/debug/test infrastructure.
- Persist enough profile identity and resolved snapshot data for future restore semantics; do not silently re-evaluate profiles on resume.
- Secret values must remain references only; plaintext secrets are out of scope for the profile resolver.
The child orchestrator may split implementation among sub-Pods, but final merge/close remains parent-side.
--- ---