docs: repoint the docs site + drift guard off reusable-workflows once actions#314 archives it

[devantler]

🤖 Generated by the Daily AI Assistant

Problem

actions#314 (feat!: merge reusable-workflows INTO actions, merged 2026-06-24) is migrating the reusable workflows out of the standalone devantler-tech/reusable-workflows repo and into devantler-tech/actions. The migration is in progress, not complete: the reusable-workflows repo is not yet archived, it still hosts all the workflow_call workflows, and consumers still pin them there (e.g. go-template pins devantler-tech/reusable-workflows/.github/workflows/create-release.yaml@v5.6.6). So today the docs site is accurate — updating it now would be premature.

But the devantler.tech docs site (this product) hardcodes the reusable-workflows repo in five places, and the moment the maintainer completes the migration — archives reusable-workflows and/or removes it as a submodule of this monorepo — they all go stale at once, with nothing tracking it. One of them fails loudly and confusingly:

• The drift guard docs/scripts/check-active-projects-drift.sh hard-fails (die_missing "reusable-workflows submodule") if the github/devantler-tech/github-actions/reusable-workflows/.github/workflows path is absent. The instant the RW submodule is removed, the docs CI lane (🧪 Test scripts) goes RED with a "is the submodule checked out?" error — before any docs content is even touched. This is the non-obvious one.

This is precisely the failure mode roadmap epic #1813 theme 2 ("make site content self-sustaining — site content cannot silently go stale between maintenance runs") exists to prevent. Capturing it now (rather than discovering it as a surprise red CI lane) is the right "capture before you build" discipline.

Blast radius — surfaces that reference devantler-tech/reusable-workflows

#	Surface	What references RW	Stale how
1	docs/scripts/check-active-projects-drift.sh	rw_workflows_dir path + the whole "Reusable Workflows" check (reusable-workflows-count / reusable-workflows-names markers)	die_missing → CI RED on submodule removal
2	docs/src/content/docs/projects/active.mdx	## 🔄 Reusable Workflows section + projects-submodules: …reusable-workflows=section disposition marker	section + marker describe a dead repo
3	docs/src/content/docs/templates/go.md	"🔄 Reusable workflows used by this template" link	dead link
4	docs/src/content/docs/templates/dotnet.md	same link	dead link
5	docs/src/content/docs/templates/gitops-tenant-template.md	same link + template-sync.yaml ownership note	dead link

(platform-template.md does not carry the RW link — verified.)

Trigger (do NOT start before this)

Act only once the maintainer completes actions#314: the reusable-workflows repo is archived and/or removed as a submodule of this monorepo (.gitmodules no longer lists github/devantler-tech/github-actions/reusable-workflows). Until then the references are correct and this is a no-op. Watch the reusable-workflows repo's archived flag and .gitmodules.

Proposed direction (when triggered)

1. Drift guard — repoint the reusable-workflows check at the workflows' new home inside actions (path TBD by how chore(deps): Bump projects/data-product from 9bc2603 to 5b66aab #314 lays them out), or fold them into the Actions check; ensure the guard no longer hard-depends on a removed submodule. Keep the count/name set-equality semantics. Update its self-test fixture (check-active-projects-drift.test.sh) in lockstep.
2. active.mdx — update the ## 🔄 Reusable Workflows section + the projects-submodules disposition marker to reflect the new layout (RW workflows now under actions).
3. Template pages — repoint the three "Reusable workflows used by this template" links to the workflows' new location in actions (and re-pin the consumers in lockstep if that's tracked here).
4. Re-run the docs drift guard locally + in CI to prove green.

Rough size

S–M, incremental and mechanical once the migration lands — but blocked on the maintainer's #314 completing. This issue is the tracking anchor so the blast radius (especially the silent CI-red from the guard's die_missing) isn't rediscovered the hard way.

Child of #1813 (theme 2). Related: #1837 (the drift guard), actions#314 (the migration).