Product design archive and future comeback blockers

[Iron-Mark]

Summary

A public-safe product design archive has been prepared for HireProof so the project can be picked back up later without re-discovering the design state.

The archive is intended for product, UI/UX, and portfolio review. It documents the responsive app screens, Figma overview pages, and capture metadata without including secrets or private credentials.

Archive Contents

• Parent index: docs/product-design/README.md
• Screen archive index: docs/product-design/screens/README.md
• Machine-readable manifest: docs/product-design/screens/_manifest.json
• 195 PNG screenshots, about 20.9 MiB
• 192 responsive route screenshots across 64 routes
• Figma overview exports:
  • 00-preview.png
  • 02-design-system.png
  • 03-product-strategy.png

Verification Already Done

• Figma page order verified: 00 Preview, 01 Responsive Screens, 02 Design System, 03 Product Strategy
• 02 Design System expected horizontal frame order verified
• 03 Product Strategy visible title and 11 expected sections verified
• Duplicate top-level layer checks passed for the target Figma pages
• Clipped-text heuristic checks passed for the target Figma pages
• Screenshot files render from disk with valid dimensions
• Manifest parses successfully
• Archive links resolve locally
• No raw local capture URL remains in the archive metadata
• No .env, key, certificate, database, log, or temp files found in the archive
• Text and PNG raw-string scans found no token-shaped secrets
• PNG metadata scan found only basic Figma software metadata in the Figma exports

Future Comeback Blockers

• Commit and merge the archive when ready so the GitHub repo has the design snapshot.
• Optional: run OCR over screenshots before making the archive a long-term public reference. Local OCR tooling was not available during the first safety pass.
• Refresh screenshots if product UI changes before the repo becomes active again.
• Re-run product checks before any release work: lint/typecheck, runtime wiring tests, production build, and browser smoke checks.
• Re-check GitHub Dependabot, CodeQL, and security alerts before resuming development.
• Verify live production behavior only with current deployment state and credentials. Do not assume authenticated flows are healthy without exercising real logged-in paths.
• Reconfirm Vercel environment variables and deployment protection before changing production.
• Reconfirm branch policy before active work resumes: feature branches to dev, then dev to main.
• Confirm Figma access and ownership before relying on the Figma MCP workflow again.

Definition of Ready to Resume

• Design archive is committed and reachable in the repo.
• Current screenshots are either accepted as the historical snapshot or refreshed.
• Security alerts are triaged.
• Local production-like checks pass on the intended Node version.
• Live production smoke checks are completed for public and credential-backed flows that matter.