2.1 KiB
2.1 KiB
Created
Created by tickets.sh create.
Review: approve
Reviewed merged implementation from branch work/builtin-profile-remove-manifest-cascade (625730c, follow-up 20ac0c9, merged as merge: builtin profile default startup).
Approved after blocking fixes:
insomnia-pod --overlayis no longer accepted as a user-facing generic TOML layer; SpawnPod now uses hidden typed--spawn-config-jsonand TUI restore uses typed--session-pod-name/--resume-scope-json.insomnia-pod --pod <name>fresh-create compatibility is explicit: absent Pod metadata resolves the default profile and applies the requested pod name as a typed override, with test coverage.- TUI fresh spawn no longer has
cascade_has_scope,CwdDefault, or cwd write-scope injection. Scope comes from the selected profile; session restore passes only the persisted scope snapshot. resources/nix/profiles/default.nixmatches the current dogfooding manifest values and builtin profile resolution resolvestarget = "."against the launch workspace/current directory rather than the bundled profile directory.- Profile and one-file manifest paths share
PodManifestConfig::builtin_defaults()plusPodManifest::try_from(...)validation, and docs now describe prompt-loader limitations without reviving ambient manifest discovery.
Validation run in the implementation worktree:
cargo fmt --checkcargo test -p manifest profile -- --nocapturecargo test -p pod profile -- --nocapturecargo test -p client spawn -- --nocapturecargo test -p tui spawn -- --nocapturenix eval --json --file resources/nix/profiles/default.nix >/dev/nullcargo test -p pod --bin insomnia-pod -- --nocapturecargo test -p pod spawn_config -- --nocapturecargo test -p manifest -p pod -p tui --lib --bins./tickets.sh doctorgit diff --check
Known unrelated full integration failures in cargo test -p manifest -p pod -p tui remain in existing pod rollback integration tests and were not introduced by this ticket.