fix(catalogue): alias the playbook dependency-versions address

src/src/data/projects/engineering-playbook.yml

@@ -41,6 +41,13 @@ docs:
   # `Home.md` is the hub (`rootPage` above) and is published as the landing page.
   exclude:
     - _Sidebar.md
+  # A page's folder is part of its URL (ADR 0011), so `Dependency-Versions.md`
+  # publishes at `/docs/engineering-playbook/foundations/dependency-versions/`.
+  # The flat address is kept as an alias for anyone who looks for that page at
+  # the docs root: the build writes a meta-refresh redirect there, and only once
+  # the nested page it forwards to actually exists.
+  redirects:
+    dependency-versions: foundations/dependency-versions
 related:
   - build-sdk
   - containers

src/tests/unit/docs-redirects.test.ts

@@ -197,6 +197,20 @@ describe('moved documentation page redirects', () => {
     ).toEqual([['/docs/zodsharp/performance/', '/docs/zodsharp/quality/performance/']]);
   });
 
+  test('the playbook keeps its docs-root dependency-versions address', () => {
+    // The page lives under its topic folder, which makes the folder part of the
+    // URL (ADR 0011), so the catalogue declares the docs-root address as an
+    // alias: a reader or a link that looks for `dependency-versions` at the
+    // project root lands on the page instead of a 404. The pair is only written
+    // while the nested page it forwards to is published.
+    expect(docsPageRedirects(projects)).toContainEqual({
+      from: '/docs/engineering-playbook/dependency-versions/',
+      to: '/docs/engineering-playbook/foundations/dependency-versions/',
+      title: 'This documentation page moved…',
+      message: 'The page now lives at its new address.',
+    });
+  });
+
   test('a moved page is written as a redirect once its new address is published', () => {
     const dist = mkdtempSync(join(tmpdir(), 'purview-redirects-'));
     try {