Greedy Growers Calculator

English-first, fan-made Greedy Growers harvest calculator and evidence-backed data site. The product works with player-supplied estimates before community data exists; unverified data pages remain transparent and noindex.

Local setup

npm ci
Copy-Item .env.example .env.local
npm run dev

Production-like local run:

npm run build
npm start -- --hostname 127.0.0.1 --port 3421

Quality gates

npm run check
npm run test:e2e
npm run audit:prod
npm run lhci
npm run evidence:validate

npm run check runs ESLint, TypeScript, unit/integration tests, canonical data validation, brand contamination checks, and the production build.

Environment variables

• NEXT_PUBLIC_SITE_URL: optional canonical-origin override. Production builds default to https://greedygrowersgame.com; any production override must use HTTPS.
• NEXT_PUBLIC_GA_ID: optional consent-gated GA property. Microsoft Clarity uses the consent-gated project ID embedded in the analytics module.
• NEXT_PUBLIC_SUPPORT_EMAIL: real support/deletion contact; leave unset rather than using a placeholder.
• DATA_SUBMISSION_WEBHOOK_URL and DATA_SUBMISSION_WEBHOOK_TOKEN: server-only moderation inbox.
• SUBMISSION_RETENTION_DAYS: approved pending-submission retention. The form stays disabled when it is absent.
• MODERATION_INBOX_DRIVER=file: optional local-development inbox stored under ignored .local-data/; production deliberately refuses this driver.
• GREEDY_DATASET=fixtures: development/E2E only; production use throws.

Never commit .env.local or real secrets.

For a local end-to-end moderation test, set MODERATION_INBOX_DRIVER=file and SUBMISSION_RETENTION_DAYS in .env.local, restart the app, and submit through /submit-data. Review by receipt from PowerShell:

$env:SUBMISSION_RETENTION_DAYS='30'
npm run moderation -- show <receipt>
npm run moderation -- review <receipt> rejected local-reviewer 'Evidence is incomplete'
npm run moderation -- purge

An approved local inbox decision records review state only. It never edits or publishes files under data/; canonical promotion remains a separate reviewed commit. npm run moderation -- purge deletes every expired raw inbox payload, including approved submissions after their canonical promotion.

Route map and SEO decisions

• /: canonical calculator, indexable.
• /guides, /guides/beginner-guide, /guides/when-to-harvest, and /about: evidence-bounded editorial pages, indexable without Phase 0 gameplay recordings.
• /seeds, /seeds/[slug], /seeds/compare, /lightning, /codes, /updates, /data-status: evidence-gated; empty production states are noindex or absent from the sitemap.
• /submit-data, /contact, /privacy, /terms: useful public utility/legal pages, noindex.
• /calculator: exact 301 to /.

Data workflow

Public canonical records live under data/ and are validated against features/data/schemas.ts. Submissions never write to those files. Promotion is manual and receipt-based; see docs/data-moderation-runbook.md.

Current production data intentionally keeps gameVersion: unverified until gameplay/version evidence is supplied. Do not fabricate values, codes, mechanics, probabilities, or detail pages to unlock indexing.

Phase 0 recording state lives in research/evidence-manifest.json. Raw videos remain private; only reviewed, privacy-safe evidence URLs belong in the manifest. REC-01 through REC-05 must all be approved in independent server sessions before the evidence gate opens. The Beginner Guide is an indexable editorial page because it stays within the official public description and labels all unknowns. Its publicationApprovals.beginnerGuideReviewed field remains an evidence-workflow audit flag, not an indexing gate. Seed, compare, growth, and lightning routes still have their own record/model thresholds; the Phase 0 flag alone cannot index them. An official version basis must reference source IDs that exist as official records in data/sources.json; an observational basis may reference only approved recording IDs. The Lightning Guide additionally requires lightningGuideReviewed: true and explicit lightningGuideSourceIds.

Analytics and privacy

Analytics consent is denied by default. Microsoft Clarity loads only after the user opts in and can collect page interactions and masked session replays. Custom events contain event names only, not calculator values, evidence URLs, receipts, or identifiers. The submission form collects pseudonymous tree/session IDs and evidence fields, not names, handles, or email addresses.

Deployment and rollback

1. Run all quality gates locally.
2. Deploy a preview with production canonicals; previews return X-Robots-Tag: noindex, nofollow.
3. Verify HTTPS, canonical, robots, sitemap, JSON-LD, consented analytics and the moderation receipt flow.
4. Enable the submission form only after the hosting firewall proves the 11th controlled request is rate-limited (429).
5. Verify Search Console ownership and submit the production sitemap.

Rollback data with git revert <data-commit> and rerun the full gate. Roll back deployment to the previous known-good release, then recheck canonical, robots and sitemap. Never rewrite shared history.