Skip to content

docs: correct README (Gemini in prod, manual Vercel deploy)#3

Merged
vedantggwp merged 1 commit into
masterfrom
cc/readme-accuracy
Jun 11, 2026
Merged

docs: correct README (Gemini in prod, manual Vercel deploy)#3
vedantggwp merged 1 commit into
masterfrom
cc/readme-accuracy

Conversation

@vedantggwp

Copy link
Copy Markdown
Owner

Two factual corrections flagged during the live-status review: production LLM is Gemini via LLM_PROVIDER (README said Anthropic); GitHub auto-deploy is not wired, so deploys are manual via vercel --prod (README said auto-deploy).

…deploy

- Production LLM is Gemini (set via LLM_PROVIDER), not Anthropic-only.
- GitHub auto-deploy is not wired; frontend deploys manually via `vercel --prod`.
@vedantggwp vedantggwp merged commit 259047f into master Jun 11, 2026
3 checks passed
@devin-ai-integration

Copy link
Copy Markdown

Code Review — PR #3

Overall: Correct and minimal. Two factual fixes to the README — both accurate.

Findings

  1. Stale reference remains: scan.neuroedge.co.uk — The README still says the scan-service runs behind Caddy at scan.neuroedge.co.uk → localhost:3001 after this PR. Since the neuroedge.co.uk domain doesn't resolve (and PR feat: free open-source demo — remove paid subsystem #4 later confirmed "it never existed"), this is misleading. The actual path is Caddy on :80localhost:3001, reached via the VPS IP 65.21.185.228 (documented in ENGINE.md). This PR was a good opportunity to fix this reference too.

  2. "Stripe" still in the tech stack — After this PR (but before PR feat: free open-source demo — remove paid subsystem #4), the tech stack line still lists Stripe in the frontend stack. This is correct at the time of this PR (Stripe hadn't been removed yet), but worth noting the sequencing.

  3. The Deployment Protection note was removed — The old text mentioned "bare deployment-specific *.vercel.app URLs are auth-walled by Vercel Deployment Protection." The new text drops this. If Deployment Protection is still enabled on Vercel, this is useful context that was lost. If it was disabled, the removal is fine.

No bugs — clean docs fix.

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.

1 participant