[szmyty]

Summary

Finalizes the application-ready résumé baseline and turns the repository into a durable public resume surface.

Baseline modernization

• keeps content/career.json as the canonical evidence ledger;
• preserves the verified MIT Lincoln Laboratory chronology, bounded funding language, education, public-location policy, and DOI-backed Reflector artifact;
• replaces two generic independent-work bullets with concrete public-system evidence:
  • Renderflow — Rust, specification-driven document rendering, graph-planned transformations, parallel execution, incremental caching, and multi-format output;
  • Relay — versioned reusable GitHub Actions and CI contracts with consumer-owned configuration/deployment boundaries;
• refreshes the evidenced skills surface with Rust, Git, CLI Design, Dev Containers, and a cleaner current Platform/DevEx vocabulary;
• sharpens the general and platform summaries around Rust/Python tooling, reproducibility, local-first systems, and bounded AI-assisted workflows without adding unsupported impact claims.

GitHub Pages

Publishes a permanent sanitized career surface at:

• https://szmyty.github.io/resume/
• https://szmyty.github.io/resume/resume.pdf

The site is intentionally static and framework-free:

• responsive light/dark landing page;
• direct canonical PDF route;
• portfolio, GitHub, ORCID, and source links;
• no JavaScript requirement;
• no email, phone, application overlay, or application PDFs.

The existing build workflow remains the single document pipeline. On successful main pushes it now:

1. completes the existing fact/privacy/profile/test gates;
2. builds and validates all public and application résumé variants plus the research CV;
3. assembles site-dist/ using the already-validated general public PDF;
4. uploads the GitHub Pages artifact;
5. deploys it through the github-pages environment.

One-time Pages setup

Before the first deployment, set the repository publishing source once:

Settings → Pages → Build and deployment → Source → GitHub Actions

This is intentionally not automated: GitHub's standard GITHUB_TOKEN cannot safely perform first-time Pages enablement. After that one-time setting, successful main builds deploy automatically.

Validation

CI run #27 is green end-to-end:

• canonical facts/privacy/configuration ✅
• document/profile/evidence validation ✅
• public and application destination checks ✅
• unit tests ✅
• all four public résumé variants built and validated ✅
• all four application résumé variants built and validated ✅
• public research CV built and validated ✅
• ATS/PDF/privacy/font/link/page-balance gates ✅
• public artifacts and visual renders uploaded ✅

Pages assembly/deployment is correctly skipped on pull requests and runs only after merge to main.

Closes #23

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 15⭐
  Check Your Progress