[Alejandro Lopez (soyalejolopez)]

Category

• New resource (script, agent, guide, analytics, skill)
• Update to an existing resource
• Bug fix
• Docs, site, or tooling

What's in this pull request?

Publishes the Agent 365 Enablement Checklist (the sample Agent 365 deployment plan) as a new catalog resource under copilot-agent-strategy/agent-365-enablement-checklist/.

It is a single self-contained HTML file with no external scripts, fetches, or dependencies. Customers can scope a rollout by agent type, pillar, or feature, track role-based tasks to go-live on a readiness dashboard, and export to Excel, CSV, or JSON. A built-in "Explore sample data" mode (fictional Contoso) lets viewers try it without entering anything. Everything a user enters stays in their browser (localStorage); nothing is sent anywhere.

What changed

• New resource: index.html, README.md (front matter, privacy note, companion links, disclaimer), CHANGELOG.md, preview.webp.
• Tagged agent-365, so it appears automatically in the landing page Agent 365 row (first, as the newest), with the New badge, a shareable page at /r/agent-365-enablement-checklist/, and a social card.
• Regenerated catalog output: catalog.json, r/ pages, sitemap.xml, feed.xml, and assets/og/.
• Added a row to copilot-agent-strategy/README.md for the checklist and for the Customer Implementation Guide it pairs with.
• New guardrail: tools/catalog-build/test-internal-links.js, wired into npm run check. It fails when a FastTrack Pages or GitHub tree/blob link in a resource page or README no longer resolves to a real path, so the checklist, the Implementation Guide, the Cost Calculator, and the Atlas stay aligned. All links resolve today.

Link alignment

The checklist links to the Implementation Guide (Detailed view, #advanced), the Cost Calculator, the Lifecycle Atlas, and agent365-skills. Each path was checked by the new test.

Heads up

The checklist links to the Lifecycle Atlas. The Atlas replacement is a separate follow-up PR, which will update that link in the same change.

Related issues

Part of the revamp tracked in #482.

Checklist

• No private, customer-specific, or unlicensed content, and no secrets (sample data is fictional; the GUIDs are Microsoft first-party app IDs)
• README front matter is valid: npm ci --prefix tools/catalog-build && npm run check --prefix tools/catalog-build (passes: metadata valid for 57 resources, internal links resolve, all tests pass)
• version and updated were bumped (and published was preserved) (new resource: 1.0.0, published and updated 2026-10-28)
• Installation and usage steps were tested (opened in a browser via the landing page row, the /r/ page, and the tool itself)
• Files over 5 MB were avoided (the largest new file is index.html at 0.65 MB)

See CONTRIBUTING.md for details.