Architecture correction
Part of #2005 and #2002. The selected coding agent owns planning through its native /goal session. The UI must not expose a ProPR-authored issue hierarchy or scheduler as goal authority.
Scope
Add the first-class /goals route, navigation, typed API/hooks, create workflow, and list/summary page.
Creation
- Select repository, goal-capable agent, model, objective, parallelism preference, and Ultrafix preference.
- Describe parallelism/Ultrafix as policy supplied to the coding agent.
- The final epic PR is always draft/unmerged for human approval; do not offer automatic merge.
- Use real catalog capability/model metadata.
- Preserve accessibility, validation, idempotent submission, retry, demo/read-only behavior, and existing routes.
List/summary
Show objective/repository, host lifecycle, native provider goal status, selected/requested/effective model, provider-native plan/checklist progress, tokens, elapsed/active/paused time, message/recovery state, passively associated issue/PR counts, and final PR link when known.
Do not require node counts, controller active-task counts, hierarchy progress, or controller completion blockers.
Acceptance
- Tests cover goal-capable catalog filtering, native status/checklist summaries, model state, policy settings, lifecycle/recovery, stats, socket/pagination/reconnect, accessibility, and demo mode.
- Client mocks use the shared canonical native-goal contracts.
- Existing Plans/Tasks/navigation behavior remains green.
Architecture correction
Part of #2005 and #2002. The selected coding agent owns planning through its native
/goalsession. The UI must not expose a ProPR-authored issue hierarchy or scheduler as goal authority.Scope
Add the first-class
/goalsroute, navigation, typed API/hooks, create workflow, and list/summary page.Creation
List/summary
Show objective/repository, host lifecycle, native provider goal status, selected/requested/effective model, provider-native plan/checklist progress, tokens, elapsed/active/paused time, message/recovery state, passively associated issue/PR counts, and final PR link when known.
Do not require node counts, controller active-task counts, hierarchy progress, or controller completion blockers.
Acceptance