Canonicalize mission links and preserve mission context in the service gateway #5

2026-06-09T21:30:11Z

dv commented

2026-06-09 21:30:11 +00:00

Summary

 This PR updates the backend mission contracts so notifications, actions, suggestions, and service handoffs all resolve
 around canonical mission instance routes and mission-aware event recording.

 ## What changed
 - restored the home feed contract to the full six dashboard modules
 - added canonical mission detail href helpers and updated mission notifications, action fallbacks, suggestions, and seeded
 mission links to point to `/missions/[id]` or `/missions/available` instead of legacy
 `/missions/active?missionInstanceId=...` URLs
 - updated mission reducers and routes so mission-generated CTAs consistently emit canonical mission detail links
 - taught the service gateway to derive mission context from top-level JSON payloads or mission query params on interview,
 roleplay, and resume requests
 - stripped mission-only fields and query params before forwarding requests downstream so existing service contracts remain
 unchanged
 - kept grow-event recording attached to the originating mission instance for interview, roleplay, and resume handoffs

 ## Outcome
 Mission CTAs now resolve to the right dashboard surfaces, the home feed reflects the intended mission model, and service

## Summary This PR updates the backend mission contracts so notifications, actions, suggestions, and service handoffs all resolve around canonical mission instance routes and mission-aware event recording. ## What changed - restored the home feed contract to the full six dashboard modules - added canonical mission detail href helpers and updated mission notifications, action fallbacks, suggestions, and seeded mission links to point to `/missions/[id]` or `/missions/available` instead of legacy `/missions/active?missionInstanceId=...` URLs - updated mission reducers and routes so mission-generated CTAs consistently emit canonical mission detail links - taught the service gateway to derive mission context from top-level JSON payloads or mission query params on interview, roleplay, and resume requests - stripped mission-only fields and query params before forwarding requests downstream so existing service contracts remain unchanged - kept grow-event recording attached to the originating mission instance for interview, roleplay, and resume handoffs ## Outcome Mission CTAs now resolve to the right dashboard surfaces, the home feed reflects the intended mission model, and service

dv added 1 commit 2026-06-09 21:30:11 +00:00

feat: enhance mission detail handling and update hrefs across services 92ab414048

dv merged commit 72b3f03dad into staging

2026-06-14 13:29:26 +00:00

dv referenced this issue from a commit

2026-06-14 13:29:26 +00:00

Merge pull request 'Canonicalize mission links and preserve mission context in the service gateway' (#5) from prm-47/agent-harness-over-microservice into staging

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: growqr-app/growqr-backend#5