fix(certs): move Auditor Accreditation page to /certs/auditor-accreditation

[eastagiletracker]

This PR proposes moving the Auditor Accreditation page from /certs/certified-partners to /certs/auditor-accreditation, with 301 redirects from the old path (Fixes #524). We include this PR work along with a full history of your repo at https://eastagiletracker.com/projects/693. You can sign in with your GitHub ID to claim ownership of the project.

What does this PR change?

After #520 reworked the page into Auditor Accreditation, the site still served it at /certs/certified-partners under a "Certified Partners" sidebar label, and /certs/auditor-accreditation did not exist. This PR does the four tasks listed in #524: renames docs/pages/certs/certified-partners.mdx to auditor-accreditation.mdx (content unchanged), updates the vocs.config.ts sidebar entry to "Auditor Accreditation" with the new link, updates the internal links in certs/overview.mdx and the generated certs/index.mdx (plus the matching key in utils/fetched-tags.json, in the order the tags generator writes it), and adds two rules to public/_redirects, one for /certs/certified-partners and one for /certs/certified-partners/. Both are needed because Pages canonicalizes directory pages to the trailing-slash form, so inbound links exist in both shapes.

Reproduction on current develop (b8c1e81): after pnpm run docs:build, dist/public/certs/certified-partners/index.html has the title "Auditor Accreditation | Security Alliance" but the sidebar entry "Certified Partners", and no certs/auditor-accreditation route is generated.

Verification: I served each build's dist/public locally with wrangler pages dev, which applies _redirects the same way Pages does, and followed redirects with curl -sL:

before (develop)
/certs/certified-partners       -> 200 /certs/certified-partners/
/certs/auditor-accreditation    -> 404
after (this branch)
/certs/certified-partners       -> 200 /certs/auditor-accreditation/ (2 redirects)
/certs/certified-partners/      -> 200 /certs/auditor-accreditation/ (2 redirects)
/certs/certified-partners.html  -> 200 /certs/auditor-accreditation/ (3 redirects)
/certs/auditor-accreditation    -> 200 /certs/auditor-accreditation/

As a control, I served the new build with the old _redirects file. All three old URLs returned 404, so the redirect rules are what keep existing links working. pnpm run docs:build succeeds, and grep -r certified-partners dist/public now matches only _redirects. The llms output and the search index pick up the new route. test:security-map (29/29), validate:security-map, and cspell and markdownlint on docs/pages/certs pass as they did before the change. validate:content reports the same issue set as on develop: the page's existing description_long:175 note now appears under the new filename.

How this was managed

This change was tracked as story 27y on the SEAL Frameworks board, which was imported from this repo's 620 issues and pull requests and used to manage this work.

If you'd rather not receive contributions like this, reply no-more-prs on this pull request and we won't open any further ones on your repositories.

---

Lawrence W. Sinclair
CEO / East Agile
linkedin.com/in/lwsinclair/
eastagile.com

[github-actions]

Sidebar Configuration Reminder

This PR includes added, renamed, or removed documentation files:

• docs/pages/certs/auditor-accreditation.mdx (renamed)

Please ensure that:

• The sidebar in vocs.config.ts has been updated to include these files
• New content has the dev: true parameter so it's marked as under development
• Sidebar links match the file paths - use the preview deployment to verify

See Contributing guidelines - Sidebar / Navigation for more details.

---

_{This is an automated reminder. If this PR doesn't need sidebar changes, you can ignore this message.}

[scode2277]

Hi @eastagiletracker, thanks for this contribution!

Before we review the changes, a quick heads up: the commits in this PR aren't showing as verified, and we need them signed before we can merge.
We have a guide to fix them on the site. Note that it assumes you already have a signing key set up.

Happy to help if needed :))