Apply portfolio-quality pass: sanitize copy, links-only contact, accessible navigation, and content tests

[cbratkovics]

Motivation

• Implement the Portfolio_Audit_and_Fix_Plan to harden privacy, clarify case studies, and make core content resilient and accessible.
• Ensure published identity and contact model remain links-only and remove internal editorial notes or defensive copy from public pages.
• Improve in-page navigation, respect reduced-motion preferences, and add reproducible content-level checks so the site can be validated in CI.

Description

• Sanitized and clarified public case-study and highlight copy in portfolio/components/WorkStories.tsx, portfolio/components/Impact.tsx, and the featured project descriptions so stories present outcomes, contribution, decisions, and scope without editorial metadata.
• Enforced links-only contact policy and the approved hero eyebrow in portfolio/components/Contact.tsx and portfolio/components/MinimalHero.tsx so only GitHub/LinkedIn appear and the eyebrow reads 7+ years in enterprise analytics.
• Reworked navigation and fragment handling in portfolio/components/Navigation.tsx to use native anchors, expose an accessible mobile disclosure (aria-expanded/aria-controls), and highlight the active section for keyboard users.
• Added/ensured reduced-motion handling and resilient initial rendering in portfolio/app/globals.css so animations respect prefers-reduced-motion and decorative elements do not block core content.
• Tightened metadata and structured data (site canonical and Person JSON-LD) in portfolio/app/layout.tsx and portfolio/config/site.ts to preserve location‑free content and canonical URL configuration.
• Kept the image and asset references consistent in portfolio/data/projects.ts and inspected large thumbnails under portfolio/public/images//portfolio/images/ to prepare responsive/optimized delivery without replacing images in this pass.
• Strengthened a reproducible content contract in portfolio/tests/content-contract.test.mjs to assert chronology, education order, links-only contact, featured project destinations, and that private/availability language is absent.

Testing

• Ran the repository's content contract tests with node --test tests/content-contract.test.mjs from portfolio/ and all assertions passed (5 tests, 0 failures).
• Verified Node and npm runtimes during the run (node -v, npm -v) to record the local environment used to execute the tests.
• External package/version queries and some remote artifact fetches were attempted as part of verification but failed due to registry/read access; these network checks are recorded but not treated as test passes.

---

Codex Task

[vercel]

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

Project	Deployment	Actions	Updated
cbratkovics-dev	Ready	Preview	Sep 12, 2026 3:05am UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-12T03:10:19.501252Z	6870670	PR opened
🔒 Security Review	✅ Completed 2026-09-12T03:08:45.820146Z	6870670	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.