docs(digstore): note digs as a first-class alias for the digstore CLI

docs/digstore/cli/command-reference.md

@@ -21,7 +21,7 @@ tags:
 
 # Command reference
 
-Every `digstore` command. Run `digstore <command> --help` for full flags and examples.
+Every `digstore` command. Run `digstore <command> --help` for full flags and examples. Every command below also works via `digs`, a first-class shorthand — `digs` and `digstore` are the same program.
 
 > **On-chain by default.** `init` mints the store's singleton on **Chia mainnet** and `commit` anchors each new deployment root on-chain (both block until confirmed and spend real XCH). Each publishes one **capsule** and costs the **uniform capsule price in $DIG** (mint or commit) — paid to the DIG treasury in the same spend bundle (memo = store id). Both commands disclose the cost and check your balance before submitting; they block if the wallet is short on XCH **or** DIG. You need an unlocked wallet seed and a funded wallet first — see [On-chain anchoring](./onchain-anchoring.md).
 

docs/digstore/cli/install.md

@@ -17,6 +17,8 @@ tags:
 
 # Installing the CLI
 
+Every install method below places two binaries on your `PATH`: `digstore` and its shorthand `digs`. They're the same program — `digs <args>` behaves identically to `digstore <args>` (same commands, flags, and `--json` output) — so use whichever you prefer. For example, `digs new my-app` and `digstore new my-app` do exactly the same thing.
+
 ## Raw binary (Windows / macOS / Linux)
 
 Download the binary for your OS/CPU from the [Releases](https://github.com/DIG-Network/digstore/releases) page:

package.json

@@ -1,6 +1,6 @@
 {
   "name": "docs-dig-net",
-  "version": "0.3.22",
+  "version": "0.4.0",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",

static/openrpc-node.json

@@ -2,7 +2,7 @@
   "openrpc": "1.2.6",
   "info": {
     "title": "dig RPC — node profile (local dig-node / in-process DIG Browser)",
-    "version": "0.3.22",
+    "version": "0.4.0",
     "description": "The NODE PROFILE: a distinct, smaller surface than the network profile. Of the byte methods it implements ONLY dig.getContent (local-first, else proxy); everything else proxies upstream or returns -32601. It ADDS node-only methods the security model depends on — chiefly dig.getAnchoredRoot (the CHIP-0035 on-chain head, the trusted root for mandatory root-pinning), dig.stage, and cache.*. Gate on dig.methods rather than assuming one uniform surface. See https://docs.dig.net/docs/protocol/dig-rpc#node-profile.",
     "license": {
       "name": "GPL-2.0",

static/openrpc.json

@@ -2,7 +2,7 @@
   "openrpc": "1.2.6",
   "info": {
     "title": "dig RPC — DIG Network Content Interface (network profile)",
-    "version": "0.3.22",
+    "version": "0.4.0",
     "description": "The network-wide read interface for DIG content over JSON-RPC 2.0 — the NETWORK PROFILE served by the canonical node at rpc.dig.net. Blind by construction (the node holds no URN and no key), verifiable without trust (merkle inclusion proofs against the chain-anchored root), and streamable at any size. There is no `decoy` field on the wire and no CDN. See https://docs.dig.net/docs/protocol/dig-rpc.",
     "license": {
       "name": "GPL-2.0",