Align implementation-readiness project and add canonical IRW route

[Tyler-Windes]

Summary

This branch prepares the implementation-readiness project for a cleaner, more natural public presentation while preserving the existing three-project portfolio structure.

Main changes

• Adds https://tyler-windes.com/irw/ as the canonical implementation-readiness route.
• Keeps the former project URL as a static redirect so existing links continue to work.
• Explains the platform-neutral foundation and Jira/Confluence implementation as two related layers rather than conflicting projects.
• Distinguishes the eight foundation validation cases from the ten IRW UAT cases.
• Updates the homepage project card and language without adding a fourth portfolio project.
• Uses direct, human-led project language and removes overt audience-targeting language from the refreshed surfaces.
• Updates the project metadata, repository README, sitemap, deterministic build, and validation rules.
• Keeps Jira reporting and Forge implementation in the v1.1 roadmap without claiming completed features.

Scope boundary

The branch does not change the other two case studies beyond preserving navigation through the former readiness route. It does not claim a Jira dashboard, Forge source, build, deployment, installation, or runtime result.

Validation required before merge

• GitHub Actions public-site validation
• Desktop and narrow-width visual review of the homepage and /irw/
• Legacy route redirect check
• Internal and external link review
• Social metadata and sitemap review
• Logged-out check of the linked Atlassian page

The pull request is intentionally opened as a draft and should not be merged until those checks pass.