chore(links): repoint dig-store repo links to DIG-Network/digs (#764)

docs/browser/chia-protocol.md

@@ -106,7 +106,7 @@ urn:dig:chia:2855390f…aade:1a2b3c…/readme.txt      # pinned version
 
 When you type a URN (`urn:dig:…`) or a chain-qualified shorthand (`chia://chia:<storeId>…`), the browser **canonicalizes** it to the host-bearing form `chia://[<rootHash>.]<storeId>/<resource>`. Two benefits: it parses as an ordinary URL, and **relative subresources** (the page's images, scripts, links) resolve against the same store and version automatically.
 
-The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/dig-store), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
+The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/digs), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
 
 ## For integrating developers — the shorthand grammar
 

docs/digstore/cli/deploy-from-github-actions.md

@@ -27,7 +27,7 @@ Publish your site or dapp to DIG automatically — a new **capsule** of your exi
 - **Pull request → a free preview.** Your build is compiled and verified through the real `chia://` read path and you get a shareable, content-addressed preview. **No chain, no wallet, no spend.**
 - **Push to your default branch → a real deploy.** The Action advances your store's on-chain root and publishes the new capsule, then posts the live URL + cost back on the commit.
 
-The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/dig-store) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
+The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/digs) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
 
 :::note You create the store once; CI only updates it
 Your store already exists (you ran [`digs init`](./onchain-anchoring.md) once, which mints it and spends $DIG). The Action only **advances** that store — it never mints. Each real deploy is a new capsule and costs the uniform capsule price in $DIG + a small XCH fee, paid from your deploy wallet. **PR previews are free.**

docs/digstore/cli/install.md

@@ -21,7 +21,7 @@ Every install method below places two binaries on your `PATH`: `dig-store` and i
 
 ## Raw binary (Windows / macOS / Linux)
 
-Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/dig-store/releases) page:
+Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/digs/releases) page:
 
 - **`dig-store-<ver>-windows-x64.exe`** — Windows
 - **`dig-store-<ver>-macos-arm64`** — Apple Silicon Mac (M1/M2/M3)
@@ -72,7 +72,7 @@ dig-store update          # download + install the latest release, in place
 dig-store update --check  # just report whether a newer release exists
 ```
 
-On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/dig-store/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
+On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/digs/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
 
 ## Related
 

docs/intro.md

@@ -106,7 +106,7 @@ The docs are organized around **what you're doing**. Each track opens with a ten
 New to the vocabulary? Skim [Concepts & glossary](./concepts.md). Want the full design? Read the [Protocol deep-dive](./protocol-deep-dive.md).
 
 :::note
-DIG Network and its primitives are open source. dig-store is licensed under GPL-2.0; see the [dig-store repository](https://github.com/DIG-Network/dig-store).
+DIG Network and its primitives are open source. dig-store is licensed under GPL-2.0; see the [dig-store repository](https://github.com/DIG-Network/digs).
 :::
 
 ## Related

docs/support/changelog.md

@@ -28,7 +28,7 @@ DIG is pre-release. Until a `1.0`, surfaces may change between releases; breakin
 
 | Surface | Version source | Where to read it |
 |---|---|---|
-| **`dig-store` CLI** | semver tags on the `dig-store` repo (`vX.Y.Z`) | `digs --version` · [Releases ↗](https://github.com/DIG-Network/dig-store/releases) |
+| **`dig-store` CLI** | semver tags on the `dig-store` repo (`vX.Y.Z`) | `digs --version` · [Releases ↗](https://github.com/DIG-Network/digs/releases) |
 | **dig RPC** | the JSON-RPC method set; a node advertises what it implements via `dig.methods` | [dig RPC methods](../rpc/methods.md) |
 | **`window.chia`** | the injected provider's capability/version surface (the DIG Browser is the reference implementation) | [Using window.chia](../browser/using-window-chia.md) |
 | **`@dignetwork/dig-sdk`** | semver on npm | [npm ↗](https://www.npmjs.com/package/@dignetwork/dig-sdk) |
@@ -69,7 +69,7 @@ _None recorded yet (pre-release baseline)._ Breaking changes to the CLI flags/ou
 ## Related
 
 - [Status](./status.md) — live health of the DIG services
-- [dig-store releases ↗](https://github.com/DIG-Network/dig-store/releases) — commit-level CLI history
+- [dig-store releases ↗](https://github.com/DIG-Network/digs/releases) — commit-level CLI history
 - [dig RPC methods](../rpc/methods.md) — the read method set this tracks
 - [Using window.chia](../browser/using-window-chia.md) — the provider surface this tracks
 - [Concepts & glossary](../concepts.md) — the vocabulary, defined once

docs/support/faq.md

@@ -83,7 +83,7 @@ Add the [GitHub Action](../digstore/cli/deploy-from-github-actions.md): push to
 
 ## Is it open source?
 
-Yes. dig-store is GPL-2.0 — see the [dig-store repository ↗](https://github.com/DIG-Network/dig-store). The whole protocol is [specified in the Protocol section](../protocol-deep-dive.md).
+Yes. dig-store is GPL-2.0 — see the [dig-store repository ↗](https://github.com/DIG-Network/digs). The whole protocol is [specified in the Protocol section](../protocol-deep-dive.md).
 
 ## Related
 

docs/support/get-help.md

@@ -21,7 +21,7 @@ Stuck on something? Start here.
 | Where | Best for |
 |---|---|
 | [**Discord ↗**](https://discord.gg/v78aygUZt) | Quick questions, deploy help, talking to other builders and the team. |
-| [**dig-store issues ↗**](https://github.com/DIG-Network/dig-store/issues) | CLI bugs, feature requests, anything `dig-store`. |
+| [**dig-store issues ↗**](https://github.com/DIG-Network/digs/issues) | CLI bugs, feature requests, anything `dig-store`. |
 | [**DIGHUb issues ↗**](https://github.com/DIG-Network/hub.dig.net/issues) | Web app / publish / domain problems. |
 | [Troubleshooting](./troubleshooting.md) · [FAQ](./faq.md) · [Error codes](./error-codes.md) | Answers you can find without waiting. |
 

docusaurus.config.ts

@@ -303,7 +303,7 @@ const config: Config = {
           "aria-label": "DIG Network Discord",
         },
         {
-          href: "https://github.com/DIG-Network/dig-store",
+          href: "https://github.com/DIG-Network/digs",
           position: "right",
           className: "navbar-github-link",
           "aria-label": "GitHub repository",
@@ -353,8 +353,8 @@ const config: Config = {
         {
           title: "Project",
           items: [
-            { label: "dig-store on GitHub", href: "https://github.com/DIG-Network/dig-store" },
-            { label: "Releases", href: "https://github.com/DIG-Network/dig-store/releases" },
+            { label: "dig-store on GitHub", href: "https://github.com/DIG-Network/digs" },
+            { label: "Releases", href: "https://github.com/DIG-Network/digs/releases" },
             { label: "DIG Network", href: "https://dig.net" },
           ],
         },

i18n/de/docusaurus-plugin-content-docs/current/browser/chia-protocol.md

@@ -102,7 +102,7 @@ urn:dig:chia:2855390f…aade:1a2b3c…/readme.txt      # pinned version
 
 When you type a URN (`urn:dig:…`) or a chain-qualified shorthand (`chia://chia:<storeId>…`), the browser **canonicalizes** it to the host-bearing form `chia://[<rootHash>.]<storeId>/<resource>`. Two benefits: it parses as an ordinary URL, and **relative subresources** (the page's images, scripts, links) resolve against the same store and version automatically.
 
-The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/dig-store), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
+The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/digs), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
 
 ## For integrating developers — the shorthand grammar
 

i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/deploy-from-github-actions.md

@@ -27,7 +27,7 @@ Publish your site or dapp to DIG automatically — a new **capsule** of your exi
 - **Pull request → a free preview.** Your build is compiled and verified through the real `chia://` read path and you get a shareable, content-addressed preview. **No chain, no wallet, no spend.**
 - **Push to your default branch → a real deploy.** The Action advances your store's on-chain root and publishes the new capsule, then posts the live URL + cost back on the commit.
 
-The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/dig-store) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
+The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/digs) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
 
 :::note You create the store once; CI only updates it
 Your store already exists (you ran [`digs init`](./onchain-anchoring.md) once, which mints it and spends $DIG). The Action only **advances** that store — it never mints. Each real deploy is a new capsule and costs the uniform capsule price in $DIG + a small XCH fee, paid from your deploy wallet. **PR previews are free.**

i18n/de/docusaurus-plugin-content-docs/current/digstore/cli/install.md

@@ -19,7 +19,7 @@ tags:
 
 ## Raw binary (Windows / macOS / Linux)
 
-Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/dig-store/releases) page:
+Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/digs/releases) page:
 
 - **`dig-store-<ver>-windows-x64.exe`** — Windows
 - **`dig-store-<ver>-macos-arm64`** — Apple Silicon Mac (M1/M2/M3)
@@ -70,7 +70,7 @@ dig-store update          # download + install the latest release, in place
 dig-store update --check  # just report whether a newer release exists
 ```
 
-On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/dig-store/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
+On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/digs/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
 
 ## Related
 

i18n/de/docusaurus-plugin-content-docs/current/intro.md

@@ -106,7 +106,7 @@ Die Dokumentation ist danach organisiert, **was du gerade tust**. Jeder Track be
 Neu im Vokabular? Überflieg [Konzepte & Glossar](./concepts.md). Willst du das vollständige Design? Lies den [Protocol Deep-Dive](./protocol-deep-dive.md).
 
 :::note
-DIG Network und seine Primitive sind Open Source. dig-store ist unter GPL-2.0 lizenziert; siehe das [dig-store-Repository](https://github.com/DIG-Network/dig-store).
+DIG Network und seine Primitive sind Open Source. dig-store ist unter GPL-2.0 lizenziert; siehe das [dig-store-Repository](https://github.com/DIG-Network/digs).
 :::
 
 ## Verwandte Themen {#related}

i18n/de/docusaurus-plugin-content-docs/current/support/changelog.md

@@ -28,7 +28,7 @@ DIG is pre-release. Until a `1.0`, surfaces may change between releases; breakin
 
 | Surface | Version source | Where to read it |
 |---|---|---|
-| **`dig-store` CLI** | semver tags on the `dig-store` repo (`vX.Y.Z`) | `digs --version` · [Releases ↗](https://github.com/DIG-Network/dig-store/releases) |
+| **`dig-store` CLI** | semver tags on the `dig-store` repo (`vX.Y.Z`) | `digs --version` · [Releases ↗](https://github.com/DIG-Network/digs/releases) |
 | **dig RPC** | the JSON-RPC method set; a node advertises what it implements via `dig.methods` | [dig RPC methods](../rpc/methods.md) |
 | **`window.chia`** | the injected provider's capability/version surface (the DIG Browser is the reference implementation) | [Using window.chia](../browser/using-window-chia.md) |
 | **`@dignetwork/dig-sdk`** | semver on npm | [npm ↗](https://www.npmjs.com/package/@dignetwork/dig-sdk) |
@@ -69,7 +69,7 @@ _None recorded yet (pre-release baseline)._ Breaking changes to the CLI flags/ou
 ## Related
 
 - [Status](./status.md) — live health of the DIG services
-- [dig-store releases ↗](https://github.com/DIG-Network/dig-store/releases) — commit-level CLI history
+- [dig-store releases ↗](https://github.com/DIG-Network/digs/releases) — commit-level CLI history
 - [dig RPC methods](../rpc/methods.md) — the read method set this tracks
 - [Using window.chia](../browser/using-window-chia.md) — the provider surface this tracks
 - [Concepts & glossary](../concepts.md) — the vocabulary, defined once

i18n/de/docusaurus-plugin-content-docs/current/support/faq.md

@@ -83,7 +83,7 @@ Add the [GitHub Action](../digstore/cli/deploy-from-github-actions.md): push to
 
 ## Is it open source?
 
-Yes. dig-store is GPL-2.0 — see the [dig-store repository ↗](https://github.com/DIG-Network/dig-store). The whole protocol is [specified in the Protocol section](../protocol-deep-dive.md).
+Yes. dig-store is GPL-2.0 — see the [dig-store repository ↗](https://github.com/DIG-Network/digs). The whole protocol is [specified in the Protocol section](../protocol-deep-dive.md).
 
 ## Related
 

i18n/de/docusaurus-plugin-content-docs/current/support/get-help.md

@@ -21,7 +21,7 @@ Stuck on something? Start here.
 | Where | Best for |
 |---|---|
 | [**Discord ↗**](https://discord.gg/v78aygUZt) | Quick questions, deploy help, talking to other builders and the team. |
-| [**dig-store issues ↗**](https://github.com/DIG-Network/dig-store/issues) | CLI bugs, feature requests, anything `dig-store`. |
+| [**dig-store issues ↗**](https://github.com/DIG-Network/digs/issues) | CLI bugs, feature requests, anything `dig-store`. |
 | [**DIGHUb issues ↗**](https://github.com/DIG-Network/hub.dig.net/issues) | Web app / publish / domain problems. |
 | [Troubleshooting](./troubleshooting.md) · [FAQ](./faq.md) · [Error codes](./error-codes.md) | Answers you can find without waiting. |
 

i18n/de/docusaurus-theme-classic/footer.json

@@ -65,11 +65,11 @@
   },
   "link.item.label.dig-store on GitHub": {
     "message": "dig-store auf GitHub",
-    "description": "The label of footer link with label=dig-store on GitHub linking to https://github.com/DIG-Network/dig-store"
+    "description": "The label of footer link with label=dig-store on GitHub linking to https://github.com/DIG-Network/digs"
   },
   "link.item.label.Releases": {
     "message": "Releases",
-    "description": "The label of footer link with label=Releases linking to https://github.com/DIG-Network/dig-store/releases"
+    "description": "The label of footer link with label=Releases linking to https://github.com/DIG-Network/digs/releases"
   },
   "copyright": {
     "message": "Copyright © 2026 DIG Network. dig-store is open source under GPL-2.0.",

i18n/es/docusaurus-plugin-content-docs/current/browser/chia-protocol.md

@@ -102,7 +102,7 @@ urn:dig:chia:2855390f…aade:1a2b3c…/readme.txt      # pinned version
 
 When you type a URN (`urn:dig:…`) or a chain-qualified shorthand (`chia://chia:<storeId>…`), the browser **canonicalizes** it to the host-bearing form `chia://[<rootHash>.]<storeId>/<resource>`. Two benefits: it parses as an ordinary URL, and **relative subresources** (the page's images, scripts, links) resolve against the same store and version automatically.
 
-The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/dig-store), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
+The URN's grammar is defined once, in dig-store's [`urn.rs`](https://github.com/DIG-Network/digs), and is shared byte-for-byte by every implementation (the browser, `dig-node`, the RPC, the extension).
 
 ## For integrating developers — the shorthand grammar
 

i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/deploy-from-github-actions.md

@@ -27,7 +27,7 @@ Publish your site or dapp to DIG automatically — a new **capsule** of your exi
 - **Pull request → a free preview.** Your build is compiled and verified through the real `chia://` read path and you get a shareable, content-addressed preview. **No chain, no wallet, no spend.**
 - **Push to your default branch → a real deploy.** The Action advances your store's on-chain root and publishes the new capsule, then posts the live URL + cost back on the commit.
 
-The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/dig-store) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
+The dedicated **[`dig-network/deploy-action`](https://github.com/DIG-Network/deploy-action)** does the work: it installs the [`dig-store`](https://github.com/DIG-Network/digs) CLI on the runner, runs `digs deploy`, and reports the result as step outputs, a PR comment, a GitHub Deployment, and a commit status.
 
 :::note You create the store once; CI only updates it
 Your store already exists (you ran [`digs init`](./onchain-anchoring.md) once, which mints it and spends $DIG). The Action only **advances** that store — it never mints. Each real deploy is a new capsule and costs the uniform capsule price in $DIG + a small XCH fee, paid from your deploy wallet. **PR previews are free.**

i18n/es/docusaurus-plugin-content-docs/current/digstore/cli/install.md

@@ -19,7 +19,7 @@ tags:
 
 ## Raw binary (Windows / macOS / Linux)
 
-Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/dig-store/releases) page:
+Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/digs/releases) page:
 
 - **`dig-store-<ver>-windows-x64.exe`** — Windows
 - **`dig-store-<ver>-macos-arm64`** — Apple Silicon Mac (M1/M2/M3)
@@ -70,7 +70,7 @@ dig-store update          # download + install the latest release, in place
 dig-store update --check  # just report whether a newer release exists
 ```
 
-On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/dig-store/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
+On Windows, download the latest `dig-store-<ver>-windows-x64.exe` from the [Releases](https://github.com/DIG-Network/digs/releases) page (or re-run the [DIG Installer](../../run-a-node/universal-installer.md)) and use it to replace the binary on your `PATH`.
 
 ## Related
 

i18n/es/docusaurus-plugin-content-docs/current/intro.md

@@ -106,7 +106,7 @@ La documentación está organizada en torno a **lo que estás haciendo**. Cada r
 ¿Nuevo en el vocabulario? Repasa [Conceptos y glosario](./concepts.md). ¿Quieres el diseño completo? Lee la [Inmersión profunda en el protocolo](./protocol-deep-dive.md).
 
 :::note
-DIG Network y sus primitivos son de código abierto. dig-store está licenciado bajo GPL-2.0; consulta el [repositorio de dig-store](https://github.com/DIG-Network/dig-store).
+DIG Network y sus primitivos son de código abierto. dig-store está licenciado bajo GPL-2.0; consulta el [repositorio de dig-store](https://github.com/DIG-Network/digs).
 :::
 
 ## Relacionado {#related}