Skip to content

fix: close deployment, sync, privacy, and CI issues - #8

Merged
AnasBabari merged 3 commits into
masterfrom
codex/resolve-issues-3-7
Aug 12, 2026
Merged

fix: close deployment, sync, privacy, and CI issues#8
AnasBabari merged 3 commits into
masterfrom
codex/resolve-issues-3-7

Conversation

@AnasBabari

Copy link
Copy Markdown
Owner

Closes #3\nCloses #4\nCloses #5\nCloses #6\nCloses #7\n\nSummary:\n- add native push/PR CI and retire placeholder GitLab deployment jobs\n- add a supported Docker Node runtime with a server-side, rate-limited AI proxy\n- add request throttling to the Vercel chat function\n- reconcile local/cloud progress using deterministic timestamps\n- expose only explicit leaderboard aggregates\n- track, cancel, and scrub worker tokens on logout/shutdown\n\nVerification: npm run build; node --check server/chat-proxy.mjs; Python-side equivalent fixes are in the Discord repository.

Add native CI for pushes and pull requests while disabling the obsolete GitLab placeholder pipeline. Serve the Docker build through a Node runtime that owns a validated, rate-limited OpenRouter proxy and keeps the key server-side. Add client-aware AI throttling to the Vercel function, reconcile local and cloud progress by snapshot timestamps, and expose only aggregate leaderboard fields. Update tests and deployment documentation.
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
han-path Ready Ready Preview Aug 12, 2026 6:50pm

Keep the lockfile synchronized with package.json so clean npm ci installs work on GitHub Actions and Docker builds.
Add the root @emnapi/runtime package entry required by clean Linux npm ci installs, which was absent after the platform-specific optional dependency resolution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

security: restrict leaderboard exposure to public aggregate fields only

1 participant