Legacy

Release handoff

v2 site handoff

Static route for reviewing the current v2 personal website scope, preservation rules, and verification checklist.

Back to v2 home Legacy site Source handoff notes

Scope to preserve

Root route

The `/` route is the v2 homepage and should keep the current evidence-backed portfolio positioning.

Legacy route

The `/legacy/` route and fixed translucent Legacy button preserve the prior site for continuity.

Evidence payload

The displayed proof items continue to come from `content/site-content.json` and public-ready source metadata.

Release checklist

  1. Confirm `/`, `/legacy/`, `/handoff/`, and `/content/site-content.json` return HTTP 200 locally and publicly.
  2. Run `node --check` for both v2 scripts and parse `content/site-content.json` before publishing.
  3. Keep full-site redaction findings limited to the documented legacy-only contact exception.
  4. Use GitHub Pages or the Vercel alias for review after confirming cache-busted v2 CSS and JS include the latest markers.

Freeze status

Final share packet checked the Turn 40 source baseline `23fce34a56aec3261c0eae3b0376b4a737a9262b` on 2026-05-15 at 19:04 -04:00.

Turn 42 release-health reconciliation deployed `4b1161562e318d1fed61087ec5372b536ab4a1af` to Vercel as `dpl_5zfX5deqYPAhmKsaJ5yRxjm7gGvT` after the alias handoff route lagged behind the final share packet.

A later log-only deploy attempt for `96d656f6a298ca88603d281d3a7e9395557815b1` hit the Vercel daily quota cap, so GitHub Pages is the freshest handoff documentation surface until quota reset or integration catch-up.

GitHub Pages and the Vercel alias returned HTTP 200 for the root, legacy, handoff, and evidence payload routes, and both public surfaces served the Turn 40 active-section rail CSS and JS markers.

Turn 45 added a native Trace proof action that links the hero proof focus to the flagship-work spotlight with custom events and a temporary visual emphasis state. This keeps the interaction useful for reviewers without adding a tour overlay, carousel package, or animation dependency.

Turn 47 release QA checked source baseline `89226320c8e8cbdb15f22ddd31b9de27a6401b7f` before this freeze-note update. Local, Browser, screenshot, GitHub Pages, and Vercel checks all preserved root, legacy, handoff, content, preview, CSS, and JS health.

Turn 48 tightened only the selected-work mobile rhythm around the PMO lead proof. The pass keeps the same evidence copy, media, routes, and top-right Legacy continuity.

Turn 50 tightened the reviewer narrative in the hero, highlights, selected-work summaries, and contact guidance. The pass keeps the same verified facts, project order, media boundary, and Legacy route.

Turn 51 release QA reset checked the current Turn 50 baseline `70e19ec9562dfbbd0203990e0dbbf7f107b1fadd` locally and publicly. GitHub Pages and the Vercel alias both served root, legacy, handoff, content JSON, docs, cache-busted CSS/JS, and the 752,937-byte social preview image without a manual deploy.

Turn 52 reopens only the CSS visual shell for a portfolio-grade art-direction reset. It keeps the same verified content, PMO media, JavaScript interactions, routes, and fixed translucent Legacy access while adding stronger editorial scale, warmer ruled bands, and richer card framing.

Turn 53 adds native first-viewport energy without changing proof claims: the hero proof chips now switch focus directly, and the portrait/proof frame gets a subtle pointer response for users who have not requested reduced motion.

Turn 54 adds artifact/source/verified chips inside the selected-work visual layer. This makes the proof cards easier to scan while keeping the current media boundary: only the PMO fixture screenshot is committed, and the remaining flagship items stay on generated proof maps until safer workflow screens are verified.

Turn 55 adds a compact builder through-line to the first-scroll highlights area. The pass makes the reviewer story more human and legible without changing evidence JSON, project links, media, contact policy, route behavior, or the top-right Legacy affordance.

Turn 56 closes the builder-story freshness gap before later visual work. The pass records the Turn 55 source commit, worker-log/freshness commit, public route checks, and automation-memory catch-up without changing homepage layout, claims, content JSON, media, or Legacy routing.

The 2026-05-16 above-fold warmth pass brings the existing `Listen / Frame / Build / Document` pattern into the hero and adds a warmer masthead frame. It changes first-scroll composition only; evidence JSON, project order, media policy, contact actions, and Legacy routing remain unchanged.

Turn 57 makes those hero method chips into native proof-path anchors. The anchors route reviewers to highlights, flagship work, and evidence with plain hash navigation, while JavaScript syncs the proof focus and selected-work spotlight as a progressive enhancement.

Turn 59 is a CSS-only first-viewport rhythm pass. It reduces hero control density, keeps the method chips as the visible proof path, and preserves the fixed translucent Legacy affordance, routes, content JSON, JavaScript, media, and contact policy.

Turn 60 adds reviewer-path sequences to the four flagship work cards. It keeps the same selected projects, PMO-only screenshot boundary, source links, contact policy, and Legacy continuity while making the case-study review path easier to follow.

Turn 61 adds a small native typed working-mode signal to the hero. It keeps the static fallback text and reduced-motion behavior, avoids the old typed/canvas dependency stack, and does not change evidence JSON, routes, contact policy, selected-work content, or Legacy continuity.

The final sprint recruiter-trust pass adds a public-only reviewer route to the contact section and refreshes the 1200x630 social preview from the current homepage. The contact path still uses selected work, resume, GitHub, and LinkedIn only; no raw email, form endpoint, scheduler, private link, or availability claim was added.

Recommendation: share `https://hardik-s.github.io/` for review, then change the site only for concrete feedback, public freshness drift, resume/profile updates, or newly verified public-safe evidence.

Current caveats

Manual Vercel CLI deploys previously hit the daily quota cap. Turn 47 did not need a manual deploy because the Vercel alias served the checked baseline during public freshness QA.

Future public claims should stay tied to reachable repositories, deployment routes, or documented source notes.

External review backlog

Must fix before sharing

None identified from the current release-candidate evidence. The next step is user review, not another broad redesign pass.

Nice polish

Consider verified project screenshots or additional native interaction only if a reviewer says it would improve comprehension. Social preview, selected-work mobile rhythm, first-two-scroll narrative tightening, the Turn 52 visual shell, Turn 53 hero proof controls, Turn 54 visual provenance chips, Turn 55 builder through-line, Turn 56 freshness closure, above-fold warmth, Turn 57 proof-path anchors, Turn 59 first-viewport rhythm, Turn 60 reviewer paths, Turn 61 typed-signal polish, and the final recruiter-trust route have already been handled.

Needs verified evidence

Keep new BioScript artifacts, screenshots, metrics, employer/customer claims, and project-status claims out of v2 until public-safe proof is documented.

Source backlog: docs/review-backlog.md.

Do not change unless

  1. A reviewer reports a concrete visual, accessibility, content, or route defect.
  2. A new public-safe project artifact is verified and materially improves the selected-work section.
  3. The user confirms a newer public resume, profile URL, or design direction.
  4. GitHub Pages or the Vercel alias becomes stale and needs a release-health repair.