Migrate whynot-design npm catalog and docs to Forgejo registry

Update catalog, docs, tests, and exec_delivery comment for Forgejo npm API.

docs/cli.md

@@ -13,7 +13,7 @@
 A catalog entry carries `org` + `repo` explicitly (never a bare "owner"), and the
 npm registry/scope live in `delivery_config.npm` as data — the engine never
 hardcodes a registry. The pilot publishes `@whynot/design` from the
-`coulomb/whynot-design` repo to `https://gitea.coulomb.social/api/packages/coulomb/npm/`.
+`coulomb/whynot-design` repo to `https://forgejo.coulomb.social/api/packages/coulomb/npm/`.
 
 ## Install
 

docs/publication-scope-policy.md

@@ -63,7 +63,7 @@ when the backend can only enforce a coarser one.
 ```yaml
 delivery_config:
   npm:
-    registry: "https://gitea.coulomb.social/api/packages/coulomb/npm/"
+    registry: "https://forgejo.coulomb.social/api/packages/coulomb/npm/"
     scope: "@whynot"
     package: "@whynot/design"
     maturity: maturity-build          # feeds the policy

docs/whynot-design-real-publish-closeout.md

@@ -16,7 +16,7 @@ prompts, workplans, or normal logs.
 | Canonical decision | `e6381a56-6b04-4fd5-b2de-f3ef59cde888` |
 | Org/repo | `coulomb/whynot-design` |
 | npm package | `@whynot/design` |
-| npm registry | `https://gitea.coulomb.social/api/packages/coulomb/npm/` |
+| npm registry | `https://forgejo.coulomb.social/api/packages/coulomb/npm/` |
 | Catalog mount/path | `secret/coulomb/whynot-design/npm/publish` |
 | Catalog field | `npm_token` |
 | Injected env var | `NPM_AUTH_TOKEN` |