Polish pre-debrief participant copy, compact stage navigation, and add research contact

[Spbd1]

Motivation

• Reduce pre-debrief priming and demand effects by removing or softening language that explicitly mentions unequal hidden conditions and similar phrasing before the debrief.
• Make the top stage navigation visually lighter and more compact while keeping progress visible and accessible.
• Add a clear, professional researcher contact block on the site and in repository-facing docs so collaborators and reviewers can reach the maintainer.

Description

• Rewrote landing and participant-facing pre-debrief copy to use neutral framing about decisions and outcome interpretation under incomplete information (notably app/page.tsx, app/layout.tsx, app/consent/page.tsx, app/game/page.tsx, app/visible-results/page.tsx, app/pre-reveal-survey/page.tsx).
• Reworded pre-debrief survey and background items to reduce priming while preserving the analytic constructs (changes in components/PreRevealSurveyForm.tsx and components/ParticipantBackgroundForm.tsx).
• Made stage labels and summaries neutral and compact by updating data/stages.ts to numbered short titles and lighter summaries.
• Replaced the large grid progress UI with a compact, horizontally-scrollable pill-style indicator and subtler current-step styling in components/ProgressIndicator.tsx, and adjusted components/SiteShell.tsx to use the new component layout.
• Softened in-task visible wording (e.g., components/HiddenCostGame.tsx, components/ResultsTable.tsx) and changed CTAs/text to avoid pre-reveal bias (e.g., Continue to debrief / Continue to questions).
• Kept post-debrief language explicit and added a short methods note on the debrief page explaining why incomplete information was used (components/HiddenRuleReveal.tsx).
• Added a small, non-distracting research contact footer (components/ResearchContact.tsx) and included contact/collaboration information in README.md, docs/RESEARCH_NOTES.md, docs/DATA_COLLECTION.md, docs/DEPLOYMENT.md, and package.json metadata (author/description/repository).

Testing

• Ran git diff --check and lint/diff checks for whitespace/newline issues and they passed.
• Ran a targeted audit (rg) for pre-debrief banned wording (phrases such as "unequal", "hidden cost", "different cost", "unfair", etc.) across the participant-facing pre-debrief files and found no matches in those audited files.
• Attempted dependency install (npm install) but it failed due to a registry access error (403 on @prisma/client), so full dependency installation was not possible in this environment.
• Attempted type checks and build commands (npm run typecheck, npm run lint, npm run build, npm run validate:sample) but these were blocked by the missing dependencies/installed tooling; the reported failures are environmental (missing Next/React/Node type packages and binaries) rather than regressions in the copy/UI edits.
• Summary of automated outcomes: code diffs and copy/audit checks succeeded; full TypeScript build/lint/validate runs were blocked by unavailable dependencies in the environment.

---

Codex Task