feat: add prototype quest progress loop

[JOY (JOY)]

Summary

• Add server-owned prototype quest state in Nakama with list, accept, and progress RPCs.
• Gate the first demo quest reward behind validated quest completion before BodyTime can be claimed.
• Wire nearby NPC chat to request prototype quest progress and refresh the HUD quest tracker.
• Update ROADMAP tracking for the new prototype quest loop.

Local code review

• Verdict: APPROVED WITH SUGGESTIONS.
• No blocking findings.
• Suggestion tracked for later: production quest progress should be triggered by Fusion/server-authoritative proximity and objective events, not by the prototype client-side chat bridge alone.

Verification

• npm run build in backend/nakama
• npm test in backend/nakama
• dotnet build SecondSpawn.AI.csproj --no-restore
• dotnet build SecondSpawn.UI.csproj --no-restore
• git diff --check
• Em dash scan on changed files
• Restarted local second-spawn-nakama; healthcheck passed and new quest RPCs registered

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9c7852416

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

[chatgpt-codex-connector]

Use canonical quest step IDs in NPC chat progress

ResolvePrototypeQuestStepId emits ask-route-or-gate / confirm-second-source, but the server quest catalog and progress path use ask_route_or_gate / confirm_second_source (backend/nakama/modules/index.ts, prototypeQuestCatalog and requirePrototypeQuestStep). Because normalizeQuestStepId does not convert hyphens to underscores, these chat-triggered progress RPCs hit unknown prototype quest step, so the new nearby-NPC chat loop cannot advance the quest and players can be blocked from reaching the reward-claim state through this intended path.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Choose incomplete step before routing quest progress

ResolvePrototypeQuestStepId always prefers route/gate actors over second-source actors, regardless of current quest progress. When both actor groups are nearby and the first step is already complete, chat keeps sending progress for the completed first step; the server treats completed steps as a no-op, so the second step never advances until the player leaves route/gate proximity. This can stall quest completion in mixed-NPC areas.

Useful? React with 👍 / 👎.