Align outcome-first positioning and publish the discoverability site

[mzored]

SkipHow is still described publicly with the pre-2.11.1 positioning, and the prepared canonical site is not published. This work should make the problem, audience, fit, non-fit cases, limits, and evidence boundary consistent across the README, manifests, FAQ, GitHub metadata, and Pages site.

Done when:

• public copy identifies SkipHow as an outcome-first Agent Skill for Claude Code and Codex;
• base-agent, owner-operated workflow, and runtime-orchestrator non-fit cases are explicit;
• unsupported behavior remains marked UNVERIFIED;
• the product, comparison, evidence, and sitemap URLs are live;
• GitHub description, homepage, topics, and social preview match the canonical metadata;
• package, host, link, metadata, responsive, and keyboard checks pass;
• the public destination is verified after delivery.

[mzored]

The outcome-first positioning, repository metadata, and three-page GitHub Pages site are live. The audit also corrected unsupported trigger-loading claims, added non-fit recommendation cases, aligned measurement with GitHub's 14-day referral window and current Google/Bing reporting, and fixed keyboard access for overflow content.

The repository social preview is prepared at site/assets/social-preview.png but is not uploaded in GitHub repository settings. Search Console and Bing Webmaster Tools were not changed.

[mzored]

Reopened because the repository-level custom social preview is still not uploaded. The prepared 1280×640 asset is live at https://mzored.github.io/SkipHow/assets/social-preview.png and tracked as site/assets/social-preview.png. GitHub exposes this upload through the repository Settings UI, not its public REST API; the authenticated browser connection was unavailable in this session. The Pages site and repository description, homepage, and topics are already live and verified.

[mzored]

Follow-up audit on the live site confirmed two repository-side gaps in the same discoverability outcome: the GitHub link exists in navigation and the footer but is not a prominent homepage action, and the homepage carries three invalid ARIA labels that deterministic checks did not catch. The Open Graph image also lacks alternate text. I am taking these fixes through the existing review and Pages deployment path. The repository-level social-preview upload remains separate because GitHub exposes it only through the Settings UI.

[mzored]

Repository-side follow-up is integrated in PR #78 and published from merge commit e0786b1. The homepage now has a visible “View on GitHub” action. All three live HTML pages match main, return HTTP 200, and pass the W3C Nu validator; the live homepage has no axe-core 4.13.0 violations or document overflow. CI and the post-merge local check passed.

The issue remains open only for the repository-level custom social preview upload through GitHub Settings. Search Console, Bing Webmaster Tools, and the v2.11.1 release were not changed.