Promote Sourcemeta One in the README (#717)

Signed-off-by: Juan Cruz Viotti <jv@jviotti.com>

Author: jviotti

.github/workflows/package.yml

@@ -220,7 +220,8 @@ jobs:
       - run: sudo npm install --global npm@11.6.4
       - run: npm --version
       - run: make npm-pack npm-publish
-      - run: |
+      - name: Blaze (JS)
+        run: |
           VERSION="$(tr -d '\n\r' < VERSION)"
           cd vendor/blaze/ports/javascript
           npm version "$VERSION" --no-git-tag-version

README.markdown

@@ -24,6 +24,9 @@ local development and when running on CI/CD pipelines. For example:
 
 [**Check out the documentation to learn more**](#usage)
 
+Pairs with [Sourcemeta One](https://www.sourcemeta.com) for a complete schema
+registry workflow.
+
 ***
 
 > [!TIP]
@@ -254,6 +257,16 @@ aggressive processor-specific optimisations cause any issues (we heard of some
 `Illegal instruction` cases), then configure the project with
 `-DJSONSCHEMA_PORTABLE:BOOL=ON`.
 
+Going Further
+-------------
+
+The JSON Schema CLI handles the local development and CI/CD side of schema
+management. For teams that need to publish, discover, and govern schemas across
+an organisation, [Sourcemeta One](https://www.sourcemeta.com) is a self-hosted
+JSON Schema registry that pairs directly with this CLI. It is designed by the
+same team, requires no database, deploys as a single Docker container, and is
+free to deploy.
+
 License
 -------
 

docs/install.markdown

@@ -18,6 +18,13 @@ results need to be
 to inline those references for local consumption. The `install` command solves
 this in a single step.
 
+> [!TIP]
+> The `install` command works with any resolvable URI, but it pairs especially
+> well with a JSON Schema registry. If you don't have one yet, [Sourcemeta
+> One](https://www.sourcemeta.com) is a self-hosted registry built for this
+> CLI, including dependency resolution, checksum verification, and GitOps-native
+> deployment.
+
 **NOTE**: Pass `--frozen` to strictly verify dependencies against the lock file
 without modifying it. This is intended for CI/CD pipelines where
 reproducibility is important. The lock file must exist and all dependencies