chore: upgrade Unity baseline to 6000.5.0b8

[JOY (JOY)]

Summary

• Upgrade the Unity project baseline from 6000.5.0b7 to 6000.5.0b8 and update package lock state.
• Sync public docs, ADR notes, AGENTS/CLAUDE context, and Cloud Run deployment notes with the new baseline.
• Keep Unity Play Mode backend integration working by accepting second_balance_seconds / reincarnation_count in the Go gateway, raising the staging token budget, and hardening Nakama storage writes against create/version conflicts.
• Deployed Cloud Run staging revision second-spawn-gateway-00008-cnn and refreshed the local Nakama container runtime with the current module build.

Verification

• dotnet build SecondSpawn.AI.csproj --no-restore
• dotnet build SecondSpawn.UI.csproj --no-restore
• dotnet build SecondSpawn.Networking.csproj --no-restore
• npm run build in backend/nakama
• npm test in backend/nakama
• go test -count=1 ./... in backend/gateway
• go vet ./... in backend/gateway
• npx --yes markdownlint-cli2 "README.md" "ROADMAP.md" "CHANGELOG.md" "CONTRIBUTING.md" "SECURITY.md" "AGENTS.md" ".claude/CLAUDE.md" "docs/**/*.md"
• git diff --check
• em/en dash scan over docs, backend, and _SecondSpawn
• Cloud Run /readyz smoke
• Cloud Run /v1/agent/decide smoke with Unity second_balance_seconds payload
• Local Nakama secondspawn_health RPC smoke
• Unity MCP Play Mode smoke on ZoneTest_Hub: backend/gateway warnings cleared; only remaining warning is Unity Visual Studio UDP port 56026

Local review

Used the repo code-review skill guidance for a targeted architectural/quality pass. No blocking findings found. .Codex/docs/technical-preferences.md is not present, so engine-specialist routing was skipped.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[JOY (JOY)]

Codex (@codex) please review PR #20.

Local code-review fallback after implementation:

Scope reviewed:

• Unity 6000.5.0b8 project/package baseline and synced docs.
• Go gateway AgentContext player schema compatibility with Unity/Nakama second_balance_seconds and
  eincarnation_count.
• Nakama storage create/version handling for player and actor profile persistence.
• Cloud Run staging deployment docs and env budget.

Findings:

• No blocking issues found.
• Hard Rule feat(backend): add Nakama OSS local base #2 preserved: gateway and Nakama still return structured intent/state only; LLM output does not mutate authoritative game state.
• Hard Rule feat(controller): add Simple KCC controller base #3 preserved: Unity stores only public gateway/Nakama URLs and no provider keys. Staging Cloud Run keeps ANTHROPIC_API_KEY in Secret Manager.
• Unity Play Mode surfaced real integration issues; fixed gateway schema drift, stale Nakama runtime RPCs, Nakama storage version handling, and staging budget exhaustion.
• Gemini Code Assist could not review because it hit daily quota.

Verification:

• dotnet build SecondSpawn.AI.csproj --no-restore
• dotnet build SecondSpawn.UI.csproj --no-restore
• dotnet build SecondSpawn.Networking.csproj --no-restore

pm run build and
pm test in �ackend/nakama

• go test -count=1 ./... and go vet ./... in �ackend/gateway
• markdownlint-cli2
• git diff --check
• em/en dash scan
• Cloud Run revision second-spawn-gateway-00008-cnn smoke: /readyz and /v1/agent/decide
• Local Nakama secondspawn_health RPC smoke after refreshing container runtime
• Unity MCP Play Mode smoke on ZoneTest_Hub: no backend/gateway errors or warnings; only remaining warning is Unity Visual Studio UDP port 56026

Verdict: local fallback APPROVED, pending external reviewer if available.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[JOY (JOY)]

Codex (@codex) please retry code review for PR #20. Codex code review credits are enabled for DOS/Second-Spawn, and repository auto review is set to Review all PRs / On every push.

Please focus on:

• Unity 6000.5.0b8 baseline update.
• Gateway player schema compatibility with Unity/Nakama second_balance_seconds and reincarnation_count.
• Nakama storage create/version handling under concurrent profile normalization.
• Cloud Run staging env/doc changes.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.