docs: fix stale content across 9 pages (round 2) (#645)

* fix(ledger): use per-pool deposit map for deposits_stake in epoch-state dump

`epoch_state_debug::capture` was computing the pool-deposit component of
`deposited` as `pool_params.len() × curPParams.pool_deposit`. This breaks
when `pool_deposit` changes via PPUP after some pools are already registered:
pools registered before the change paid the old deposit, so the approximation
drifts from the actual locked amount.

`certs.pool_deposits` already tracks the exact deposit paid at registration
time for each pool (same map used by shelley.rs and conway.rs for obligation
calc). Switch the dump to sum that map instead.

Ref: issue #615 (deposits_stake divergence sub-item).

* style: rustfmt epoch_state_debug.rs

* chore(docs): update crate count 14→15 in CLAUDE.md, add dugite-uplc and dugite-lsm

* chore(conformance): update corpus to v20260524-075059; fix mithril stub check

Mithril area now has 20 real fixture files at the pinned SHA, so the
verification step's "mithril must be stub" assertion is no longer correct.
Remove that check (it was based on an outdated observation).

New corpus stats:
  ouroboros-consensus: 277 files
  cardano-ledger:       17 files
  cardano-node:         14 files
  plutus:             3001 files
  ledger-rules:      28295 files  ← ImpSpec Haskell ledger-rules corpus
  cardano-base:         14 files
  mithril:              20 files  ← now real (was stub)

* fix(conformance): expand DELEG decoder to accept tags 2 and 13

The new ImpSpec corpus (conformance-corpus-v20260524-075059) includes
DELEG vectors with:
  - tag 2: Shelley `StakeDelegation` (backwards-compat delegation in Conway)
  - tag 13: `ConwayRegDelegCert DelegStakeVote` (register + pool + DRep)

The decoder previously only accepted tags 7–12. Extend to:
  tag == 2  || 7..=13  (matching the full Conway TxCert spec)

Reference: cardano-ledger TxCert.hs ConwayTxCert encoding.

* test(ledger): update capture_combines_stake_key_and_pool_deposits to use pool_deposits map

The test was inserting pools into pool_params but not pool_deposits, so
the new implementation (pool_deposits.values().sum()) returned 0 pool
deposits. Update the test to:
  - populate pool_deposits with per-pool historical deposit amounts
  - demonstrate the key property: dumps use historical values even when
    pool_deposit has changed via PPUP (pool 0xaa at 400 ADA, pools 0x10/0x11
    at 500 ADA, current param 600 ADA; expected total uses historical values)

* docs: fix stale content across 9 pages (round 2)

- quickstart.md: remove unpublished Docker image examples (#507)
- running/configuration.md: fix peer target defaults (EstablishedPeers 40→30,
  ActivePeers 15→20, KnownPeers 85→150 to match code defaults)
- running/config-editor.md: fix EstablishedPeers example 40→30
- running/relay.md: add dugite_ prefix to metric names in monitoring table
- running/block-producer.md: add dugite_ prefix + _total suffix to metrics
  in deployment checklist
- running/kubernetes.md: add "image not yet published" note (#507)
- reference/upgrading.md: remove Docker pull example (image not published)
- reference/mini-protocols.md: remove N2N V16/perasSupport (not implemented;
  Dugite supports V14/V15 only — #607)
- architecture/networking.md: fix EstablishedPeers default 30→"40 (30 on preview)"
  to correctly reflect mainnet/preprod vs preview config difference

Author: michaeljfazio

docs/src/architecture/networking.md

@@ -314,7 +314,7 @@ The governor maintains six independent target counts (matching cardano-node defa
 | Target | Default | Description |
 |--------|---------|-------------|
 | `TargetNumberOfKnownPeers` | 85 | Total peers in the peer table (cold + warm + hot) |
-| `TargetNumberOfEstablishedPeers` | 30 | Warm + hot peers (TCP connected) |
+| `TargetNumberOfEstablishedPeers` | 40 (30 on preview) | Warm + hot peers (TCP connected) |
 | `TargetNumberOfActivePeers` | 15 | Hot peers (fully syncing) |
 | `TargetNumberOfKnownBigLedgerPeers` | 15 | Known big ledger peers |
 | `TargetNumberOfEstablishedBigLedgerPeers` | 10 | Established big ledger peers |

docs/src/quickstart.md

@@ -12,11 +12,7 @@ tar xzf dugite-x86_64-linux.tar.gz
 sudo mv dugite-node dugite-cli dugite-monitor dugite-config /usr/local/bin/
 ```
 
-**Option B: Container image**
-
-```bash
-docker pull ghcr.io/michaeljfazio/dugite:latest
-```
+**Option B: Container image** *(coming soon — [#507](https://github.com/michaeljfazio/dugite/issues/507))*
 
 **Option C: Build from source**
 
@@ -58,17 +54,6 @@ Or via the top-level [justfile](./development.md):
 just run-relay preview
 ```
 
-Or with Docker:
-
-```bash
-docker run -d \
-  --name dugite \
-  -p 3001:3001 \
-  -p 12798:12798 \
-  -v dugite-data:/opt/dugite/db \
-  ghcr.io/michaeljfazio/dugite:latest
-```
-
 The node will:
 1. Load the configuration and genesis files
 2. Replay imported blocks through the ledger (builds UTxO set, protocol params, delegations)

docs/src/reference/mini-protocols.md

@@ -173,20 +173,18 @@ MsgQueryReply      = [3, versionTable]
 ; Keys are encoded in ascending order.
 versionTable = { * versionNumber => versionData }
 
-; N2N version numbers (V14=14, V15=15, V16=16, ...)
+; N2N version numbers implemented by Dugite (V14=14, V15=15)
 ; Note: N2N does NOT set bit-15. Only N2C uses bit-15.
-versionNumber = 14 / 15 / 16
+; V16 (adds perasSupport) is defined in the Peras spec but not yet implemented.
+versionNumber = 14 / 15
 
 ; Version data for V14/V15: 4-element array
 versionData_v14 = [networkMagic, initiatorOnly, peerSharing, query]
-; Version data for V16+: 5-element array (adds perasSupport)
-versionData_v16 = [networkMagic, initiatorOnly, peerSharing, query, perasSupport]
 
 networkMagic = uint .size 4   ; word32 (mainnet=764824073, preview=2, preprod=1)
 initiatorOnly = bool           ; true=InitiatorOnly, false=InitiatorAndResponder
 peerSharing   = 0 / 1          ; 0=Disabled, 1=Enabled
 query         = bool
-perasSupport  = bool
 
 refuseReason
   = [0, [* versionNumber]]           ; VersionMismatch

docs/src/reference/upgrading.md

@@ -42,11 +42,7 @@ sudo cp target/release/dugite-node target/release/dugite-cli \
          /usr/local/bin/
 ```
 
-**Container:**
-
-```bash
-docker pull ghcr.io/michaeljfazio/dugite:latest
-```
+**Container:** *(coming soon — [#507](https://github.com/michaeljfazio/dugite/issues/507))*
 
 ### 3. Clear Ledger Snapshots (if the snapshot format changed)
 

docs/src/running/block-producer.md

@@ -354,6 +354,6 @@ graph TB
 
 4. **Verify block production**
    - Confirm sync progress is 100% on all nodes
-   - Check `peers_connected` metrics on relays and BP
-   - Monitor `blocks_forged` metric on the BP after epoch transition
+   - Check `dugite_peers_connected` metrics on relays and BP
+   - Monitor `dugite_blocks_forged_total` metric on the BP after epoch transition
    - Set up [monitoring](./monitoring.md) and KES rotation reminders

docs/src/running/config-editor.md

@@ -157,7 +157,7 @@ dugite-config init --out-file "$CONFIG" \
 dugite-config set "$CONFIG" EnableP2P true
 dugite-config set "$CONFIG" DiffusionMode InitiatorAndResponder
 dugite-config set "$CONFIG" TargetNumberOfActivePeers 15
-dugite-config set "$CONFIG" TargetNumberOfEstablishedPeers 40
+dugite-config set "$CONFIG" TargetNumberOfEstablishedPeers 30
 dugite-config set "$CONFIG" TargetNumberOfKnownPeers 85
 dugite-config validate "$CONFIG"
 ```

docs/src/running/configuration.md

@@ -22,7 +22,7 @@ The configuration file uses PascalCase keys (matching the cardano-node conventio
   "ConwayGenesisFile": "conway-genesis.json",
   "TargetNumberOfRootPeers": 60,
   "TargetNumberOfActivePeers": 15,
-  "TargetNumberOfEstablishedPeers": 40,
+  "TargetNumberOfEstablishedPeers": 30,
   "TargetNumberOfKnownPeers": 85,
   "TargetNumberOfActiveBigLedgerPeers": 5,
   "TargetNumberOfEstablishedBigLedgerPeers": 10,
@@ -78,9 +78,9 @@ These parameters control the P2P peer governor's target counts, matching the car
 | Field | Type | Default | Description |
 |-------|------|---------|-------------|
 | `TargetNumberOfRootPeers` | integer | 60 | Target number of root peers (bootstrap + local + public roots) |
-| `TargetNumberOfActivePeers` | integer | 15 | Target number of active (hot) peers — fully syncing with ChainSync + BlockFetch |
-| `TargetNumberOfEstablishedPeers` | integer | 40 | Target number of established (warm) peers — TCP connected, keepalive running |
-| `TargetNumberOfKnownPeers` | integer | 85 | Target number of known (cold) peers in the peer table |
+| `TargetNumberOfActivePeers` | integer | 20 | Target number of active (hot) peers — fully syncing with ChainSync + BlockFetch |
+| `TargetNumberOfEstablishedPeers` | integer | 30 | Target number of established (warm) peers — TCP connected, keepalive running |
+| `TargetNumberOfKnownPeers` | integer | 150 | Target number of known (cold) peers in the peer table |
 | `TargetNumberOfActiveBigLedgerPeers` | integer | 5 | Target number of active big ledger peers (high-stake SPOs, prioritised during sync) |
 | `TargetNumberOfEstablishedBigLedgerPeers` | integer | 10 | Target number of established big ledger peers |
 | `TargetNumberOfKnownBigLedgerPeers` | integer | 15 | Target number of known big ledger peers |

docs/src/running/kubernetes.md

@@ -1,5 +1,7 @@
 # Kubernetes Deployment
 
+> **Note:** The Dugite container image is not yet published to a registry ([#507](https://github.com/michaeljfazio/dugite/issues/507)). The Helm chart and instructions below describe the target deployment model; they will be fully operational once the image is available.
+
 Dugite includes a Helm chart for deploying to Kubernetes as either a **relay node** or a **block producer**.
 
 ## Prerequisites

docs/src/running/relay.md

@@ -167,10 +167,10 @@ Dugite exposes Prometheus metrics on port 12798 by default. Key metrics to watch
 
 | Metric | What it tells you |
 |--------|-------------------|
-| `peers_connected` | Number of active peer connections. Should be > 0 at all times |
-| `sync_progress_percent` | Sync progress (10000 = 100%). Must be at 100% for the BP to produce blocks |
-| `blocks_received` | Total blocks received from peers. Should increase steadily |
-| `slot_number` | Current slot. Compare against network tip to verify sync |
+| `dugite_peers_connected` | Number of active peer connections. Should be > 0 at all times |
+| `dugite_sync_progress_percent` | Sync progress (10000 = 100%). Must be at 100% for the BP to produce blocks |
+| `dugite_blocks_received_total` | Total blocks received from peers. Should increase steadily |
+| `dugite_slot_number` | Current slot. Compare against network tip to verify sync |
 
 ```bash
 curl -s http://localhost:12798/metrics | grep -E "peers_connected|sync_progress"