1.2 KiB
1.2 KiB
Implemented, reviewed, merged, and validated.
Summary:
- Added strict Ticket role launch readiness validation while preserving backend config loading/list/show behavior.
- Role launch planning now rejects missing role table, missing role
profile, explicit top-levelprofile = "inherit", and unresolvable concrete selectors before spawn. plan_ticket_role_launch(_with_config)uses launch-specific validation instead of implicit role defaults.- No implicit builtin/default/inherit fallback was added.
TicketRoleLaunchPlan::spawn_configstill defensively rejectsinherit.- Diagnostics are bounded/actionable for Panel/launcher surfaces.
- Init/scaffold generation was intentionally not implemented here;
ticket-init-role-profile-scaffoldremains the next task.
Implementation:
- Child commit:
30a07b7 ticket: validate role launch config - Merge commit:
merge: role launch config validation
Review:
- External reviewer
role-launch-config-validation-reviewer-20260607approved with no blockers.
Validation after merge:
cargo test -p ticket config --libcargo test -p client ticket_role --libcargo test -p tui multi_pod --libcargo fmt --checkgit diff --checktarget/debug/yoi ticket doctor