seo(content): seed contextual /platform/ backlinks from 8 platform-flavored posts (#19)

Follow-up to PR #18. The repositioning gave us two landing pages
(/ai/ and /platform/) that GSC sees with just 1 impression each over
28 days. PR #18 fixed /ai/ inbound by repointing two blog /mcp/ links;
/platform/ had nothing pointing at it from content, only nav and
footer.

Adds one contextual /platform/ link to the closing paragraph of every
blog post whose subject is pure platform / API-gateway material:

- api-retirement-done-right (API lifecycle)
- authorization-at-the-gateway (CEL/OPA)
- beyond-configuration-drift (spec-first compilation)
- compliance-by-construction-part-1 (compliance evidence)
- compliance-by-construction-part-2 (compliance controls)
- how-we-build-our-roadmap (roadmap principles)
- one-gateway-many-specs (multi-spec compilation)
- strangler-fig-pattern-api-gateway (migration)

Anchor text is varied per post topic (platform-teams page, platform
team story, capabilities platform teams reach for first, ...) so this
does not read as exact-match anchor spam. Each link is on-topic to the
post's own subject; nothing was forced into a post where it would not
naturally fit.

Also swaps one em dash in beyond-configuration-drift's footer for a
hyphen, per project preference.

The three AI-adjacent posts (what-is-an-mcp-gateway, why-agents-break-
where-developers-cope, barbacane-vs-portkey-litellm) already link to
/ai/ from PR #18 and are intentionally left alone.

Author: ndreno

src/content/blog/api-retirement-done-right.md

@@ -283,4 +283,4 @@ API retirement shouldn't require a committee. It should require a pull request.
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). API lifecycle is one of the concerns on the [platform-teams page](/platform/). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*

src/content/blog/authorization-at-the-gateway.md

@@ -278,4 +278,4 @@ The [middleware documentation](https://docs.barbacane.dev/guide/middlewares.html
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). The CEL and OPA authorization plugins ship with v0.1.x. Try them against your specs and let us know what works.*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Gateway-enforced authorization is one of the [capabilities platform teams reach for first](/platform/). The CEL and OPA authorization plugins ship with v0.1.x. Try them against your specs and let us know what works.*

src/content/blog/beyond-configuration-drift.md

@@ -253,4 +253,4 @@ The goal: your API contract *is* your production configuration. Security policie
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). As of February 2026, it remains an early-stage project—evaluate thoroughly before production use.*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Spec-first compilation is the foundation of [Barbacane's platform-team story](/platform/). As of February 2026, it remains an early-stage project - evaluate thoroughly before production use.*

src/content/blog/compliance-by-construction-part-1.md

@@ -170,4 +170,4 @@ We'll cover all of that in [Part 2: the compliance controls](/blog/compliance-by
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). These compliance mechanisms are part of the broader [platform-team story](/platform/). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*

src/content/blog/compliance-by-construction-part-2.md

@@ -155,4 +155,4 @@ Conformity requirements are ultimately about demonstrating that your controls wo
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). These controls are part of [Barbacane's platform-team story](/platform/). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*

src/content/blog/how-we-build-our-roadmap.md

@@ -134,4 +134,4 @@ If you have ideas, constraints, or feedback that should inform our next decision
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). For a snapshot of where this roadmap is going for platform teams, see [the platform page](/platform/). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*

src/content/blog/one-gateway-many-specs.md

@@ -189,4 +189,4 @@ It's not a silver bullet. Cross-service consistency is a hard problem, and route
 
 ---
 
-*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*
+*Barbacane is open source (AGPLv3) and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Multi-spec compilation is one of the capabilities described on the [platform-teams page](/platform/). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*

src/content/blog/strangler-fig-pattern-api-gateway.md

@@ -300,4 +300,4 @@ By compiling OpenAPI into portable artifacts, enforcing safety at build time, an
 
 ---
 
-*Barbacane is open source and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). Questions or feedback? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*
+*Barbacane is open source and available at [github.com/barbacane-dev/barbacane](https://github.com/barbacane-dev/barbacane). For the broader picture of how Barbacane fits a platform-team migration, see [the platform page](/platform/). Questions or feedback? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*