fix(site): repair stale DevRail links

content/blog/2026-05-05-kotlin-as-reference-plugin.md

@@ -4,7 +4,7 @@ date: 2026-05-05
 description: "v1.11 ships devrail-plugin-kotlin — the first language ecosystem moved out of dev-toolchain core into a standalone plugin repo. It proves the plugin model end-to-end and gives future contributors a working extraction recipe."
 ---
 
-A few hours after [v1.10 introduced the plugin architecture](/blog/2026-05-05-plugin-architecture/), v1.11 ships the first proof. **`devrail-plugin-kotlin`** is now a separate repo, a separate release cadence, and -- for consumers who declare it -- the canonical way to use Kotlin tooling under DevRail.
+A few hours after [v1.10 introduced the plugin architecture](/blog/2026/05/plugin-architecture-v1.10-ships/), v1.11 ships the first proof. **`devrail-plugin-kotlin`** is now a separate repo, a separate release cadence, and -- for consumers who declare it -- the canonical way to use Kotlin tooling under DevRail.
 
 In v1.11, the extraction is **additive**: dev-toolchain still ships Kotlin in core (so existing `languages: [kotlin]` consumers see zero change). v2.0.0 will retire the in-core path and make the plugin the only path. This release is the rehearsal.
 

content/blog/2026-05-05-plugin-architecture.md

@@ -135,4 +135,4 @@ Plugin signing (cosign-style signature verification opt-in) is a separate track
 
 If you build a plugin we should know about, open a PR against the (forthcoming) `awesome-devrail` discovery list. For now, drop it in your team's repo or publish on GitHub and link it from your README.
 
-The full [plugin architecture design doc](https://github.com/devrail-dev/dev-toolchain/blob/main/docs/plugin-architecture.md) and the [v1.10.6 changelog entry](https://github.com/devrail-dev/dev-toolchain/blob/main/CHANGELOG.md) cover the contract in detail. Questions, plugin authors who want feedback, or edge cases we should think about -- as always, open an issue.
+The full [plugin architecture design doc](https://github.com/devrail-dev/devrail-standards/blob/main/_bmad-output/planning-artifacts/plugin-architecture-design.md) and the [v1.10.6 changelog entry](https://github.com/devrail-dev/dev-toolchain/blob/main/CHANGELOG.md) cover the contract in detail. Questions, plugin authors who want feedback, or edge cases we should think about -- as always, open an issue.

hugo.toml

@@ -14,7 +14,7 @@ languageCode = "en-us"
 [params]
   description = "Opinionated development standards for teams that ship with AI agents"
   github_repo = "https://github.com/devrail-dev/devrail.dev"
-  github_project_repo = "https://github.com/devrail-dev"
+  github_project_repo = "https://github.com/devrail-dev/devrail.dev"
   offlineSearch = false
   images = ["images/devrail-icon.png"]