fix(content): correct Barbacane license to AGPLv3 across blog and site

Eight blog articles and the trademarks page incorrectly stated Barbacane
was Apache 2.0; the project is dual-licensed under AGPLv3 and a commercial
license. Footer mentions swapped to (AGPLv3). The roadmap article's body
paragraph rewritten to acknowledge the dual-license without weakening the
anti-open-core stance. Also dropped the unused Apache-2.0 license field
from this website repo's README and package.json.

Author: ndreno

README.md

@@ -37,7 +37,3 @@ src/
 └── styles/         # Global styles
 public/             # Static assets
 ```
-
-## License
-
-Apache-2.0

package-lock.json

@@ -15,7 +15,6 @@
   },
   "keywords": [],
   "author": "",
-  "license": "Apache-2.0",
   "bugs": {
     "url": "https://github.com/barbacane-dev/website/issues"
   },

package.json

@@ -283,4 +283,4 @@ API retirement shouldn't require a committee. It should require a pull request.
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*

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

@@ -278,4 +278,4 @@ The [middleware documentation](https://docs.barbacane.dev/guide/middlewares.html
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). 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/authorization-at-the-gateway.md

@@ -253,4 +253,4 @@ The goal: your API contract *is* your production configuration. Security policie
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). As of February 2026, it remains an early-stage project—evaluate thoroughly before production use.*

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

@@ -170,4 +170,4 @@ We'll cover all of that in [Part 2: the compliance controls](/blog/compliance-by
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*

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

@@ -155,4 +155,4 @@ Conformity requirements are ultimately about demonstrating that your controls wo
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). Questions about compliance use cases? Reach us at [contact@barbacane.dev](mailto:contact@barbacane.dev).*

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

@@ -103,7 +103,7 @@ A roadmap is defined as much by what's absent as by what's present. Here are rec
 
 **"Build a plugin marketplace."** Barbacane plugins are WASM modules compiled from Rust via Wasmtime with AOT compilation. A marketplace would incentivize quantity over quality and create a maintenance surface we can't control. We've shipped over a dozen first-party plugins, from basic auth to correlation IDs to request size limits, and we'd rather have twelve solid plugins than a hundred fragile ones.
 
-**"Create an enterprise edition."** I've lived through the open-core playbook from the inside. Kong's split between Gateway OSS and Kong Enterprise, Tyk's gated dashboard and developer portal, Gravitee's community-versus-enterprise feature matrix: I've seen how this plays out. The community version gets slower updates, the best features land behind a paywall, and contributors eventually realize they're building someone else's commercial product. Barbacane is fully open source under Apache 2.0. There is no enterprise edition. We generate revenue through professional services, not feature paywalls.
+**"Create an enterprise edition."** I've lived through the open-core playbook from the inside. Kong's split between Gateway OSS and Kong Enterprise, Tyk's gated dashboard and developer portal, Gravitee's community-versus-enterprise feature matrix: I've seen how this plays out. The community version gets slower updates, the best features land behind a paywall, and contributors eventually realize they're building someone else's commercial product. Barbacane's source is AGPLv3. There is no enterprise edition, no paid tier of features. We do offer a commercial license for organisations that cannot comply with AGPL copyleft (typically SaaS vendors building on top of Barbacane), but it unlocks the *same* code, not extra capabilities. Revenue comes from that commercial license and from professional services, not from feature paywalls.
 
 ---
 
@@ -134,4 +134,4 @@ If you have ideas, constraints, or feedback that should inform our next decision
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*

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

@@ -189,4 +189,4 @@ It's not a silver bullet. Cross-service consistency is a hard problem, and route
 
 ---
 
-*Barbacane is open source (Apache 2.0) 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). Check the [documentation](https://docs.barbacane.dev/) for the full CLI reference and getting started guide.*