feat(hire): add /hire studio page and footer entry link

[Koopa0]

Summary

• New public /hire page ("Work with me") carrying the finalized studio positioning copy verbatim from the approved draft (only markdown to HTML format conversion). Lazy-loaded route + RenderMode.Prerender, matching the other static single-owner pages.
• Rendered in the editorial reading style (.ed-prose reading column + the kintsugi seam), consistent with /about — not the plain legal-page style of /privacy (see "Design decisions" below). No new CSS: reuses existing .ed-* atoms.
• Site-wide entry link: a low-key "Hire" link in the editorial footer next to GitHub/RSS. The masthead nav is left untouched.
• "Get in touch" reuses the four contact channels already published on /about (email, LinkedIn, GitHub, X).
• Adds hire.spec.ts (5 cases) and one footer-spec case for the new link.

Recon corrections (from the scoping notes)

• The scoping note assumed /privacy is footer-linked and that copying it is ~2 files + 2 route edits. Verified: /privacy and /terms are orphan pages — referenced only in the two route files, linked nowhere in the UI. The footer was a minimal koopa0.dev - GitHub - RSS - copyright colophon; the only linked personal page is /about, in the masthead nav. So there was no existing "privacy entry link" to match — the footer "Hire" link is a new, deliberately low-key entry.
• Followed the repo's testing standard (every component ships a component test, like /about) rather than the thinner /privacy / /terms (which have no spec), so 3 new files instead of 2.

Design decisions (please confirm or adjust in review)

• Editorial style over privacy-clone. A hire pitch rendered in the throwaway legal-page style would read as a legal page. The best-practice, existing-style home for a personal positioning page is the .ed-prose reading column used by /about and the article bodies.
• Footer entry link, not nav. Honors the "footer, do not touch nav" steer; the link is site-wide (present on every public page).
• Placeholders / draft reconciliation. The source draft was edited mid-work (after the page was first built); the second commit reconciles the page to the current draft verbatim:
  • Get in touch: the draft moved to a single dedicated-address Contact: line (TODO, suggesting hi@koopa0.dev). Rendered with the existing live contact@koopa0.dev for now (owner's call) — trivially swappable to hi@koopa0.dev later, per the draft's own note. The earlier four-channel row was dropped.
  • Receipts: koopa0.dev links to /articles (the writing); GitHub ("public work and profile") links to github.com/koopa0. The case study has no URL yet, so it is rendered as plain (unlinked) text — no fabricated link. Supply a URL if it should link somewhere.

Test Plan

• npx tsc --noEmit — clean
• npx ng lint — all files pass
• npx ng test — 615/615 pass (89 files), incl. hire.spec.ts (5) and editorial-footer.spec.ts (3)
• npx ng build — succeeds; /hire prerenders to dist/.../browser/hire/index.html with the correct content, and the footer "Hire" link renders on every prerendered public page

Out of scope

• No other pages, no refactors, no DB or content changes. The masthead nav is unchanged. Unrelated working-tree docs changes were left untouched and unstaged.

[augmentcode]

🤖 Augment PR Summary

Summary: Adds a new public /hire “Work with me” studio page and a site-wide entry point in the editorial footer.

Changes:

• Registers hire in both client routing (app.routes.ts) and SSR prerender routing (app.routes.server.ts).
• Introduces HireComponent with editorial reading-column layout and SEO meta updates via SeoService.
• Adds the hire page template content (positioning, service lines, receipts, and contact channels).
• Updates the editorial footer to include an internal “Hire” routerLink.
• Adds new component specs for the hire page plus a footer spec asserting the new link.

Technical Notes: /hire is prerendered using RenderMode.Prerender, and canonical/OG URL is set using environment.siteUrl.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.