docs(rewards): reward-distributor pages for funders and mirroring peers

[MichaelTaylor3d]

Summary

Adds two-audience documentation for the dig-rewards-coin managed reward distributor:

• docs/audiences/reward-funders.md (NEW) — funder-facing: the funding model (AddIncentives vs CommitIncentives), clawback rule (not a computed figure — see #3303), and the SPEC §2.2 uptime warning with the required verbatim closing line and COMMITMENT_DEPTH_EPOCHS = 2 bound.
• docs/run-a-node/earn-mirror-rewards.md (NEW) — peer/mirror-facing: claim cadence/jitter, payout floor vs fee ceiling, eviction (terminal for the entry, not the mirror), and what to check if unpaid (points to node status, does not reconstruct the never-admitted-vs-evicted distinction SPEC §12.5 clause 7 forbids).
• sidebars.ts — new "Reward funders" category (funder page) + peer page added to "Node operators".
• One-line cross-links from docs/run-a-node/index.md and docs/audiences/app-developers.md.

Both pages state their audience in the first three sentences and cross-link the other page by role. No figures were added to machine-spec surfaces (scripts/dig-spec.mjs, docs/rpc/**, static/*.json) — the three unserved reward RPC methods (dig-node v0.257.0 serves only dig.getRewardProverStatus) are named in prose only.

Blast radius: two new doc files + 3 existing files touched (sidebar + 2 cross-links); ripgrep-checked, no other doc references these new IDs yet.

Figure -> source trace

• COMMITMENT_DEPTH_EPOCHS = 2 -> dig-rewards-coin SPEC.md §7.4 clause 1 (tag v0.4.0)
• withdrawal_share_bps = 9000 (90/10 clawback split) -> SPEC.md §7.4/§7.5 (tag v0.4.0)
• CLAIM_CADENCE_SECONDS = 86_400 / CLAIM_JITTER_SECONDS = 3_600 -> SPEC.md §8.6 (tag v0.4.0)
• payout_threshold = 1_000 base units -> SPEC.md §8.3 (tag v0.4.0)
• CHALLENGE_STRIKES_TO_EVICT = 3 -> SPEC.md §3.6 (tag v0.4.0)
• dig-rpc-protocol four reward methods -> dig-rpc-protocol v0.11.0
• dig-node serves only dig.getRewardProverStatus, others return -32601 -> measured against dig-node v0.257.0
• no clawback affordance in app -> dig-app 15.6.0, consequence of the -32601 gap (dated, true cause named, no upgrade promise)
• empty first-epoch is normal / accrued value carries forward -> SPEC §15 clause 9a, resolved by execution per ticket

Checks

• npm run lint — pass
• npm run typecheck — pass
• npm run build (includes drift-gate prebuild) — pass; drift gate reported "drift gate passed" with unchanged RPC method counts (9 network / 10 node) — the three unserved reward methods were NOT added to machine-spec tables
• npm run test:unit — pending, will report before marking ready

Refs #3254

🤖 Generated with Claude Code

[MichaelTaylor3d]

Independent correctness review (loop-reviewer). Verdict: CHANGES-REQUIRED. head e5573dd.

Numeric/version claims cross-checked against artifacts (not against sibling docs):

• dig-rewards-coin 0.4.0 (chain reader): tag --contains on the adding commit (581c679, 'feat: chain reader + SPEC 0.5 cohort-pin correction (0.4.0) (#6)') = v0.4.0 only. Matches.
• COMMITMENT_DEPTH_EPOCHS = 2: dig-rewards-coin SPEC.md §7.4 clause 1 (also §2.2 clause 5, §14 table row C2).
• dig-rpc-protocol v0.11.0: Cargo.toml on main (GitHub contents API) = 0.11.0. Matches.
• dig-node v0.257.0: Cargo.toml on main = 0.257.0. Matches.
• dig-app 15.6.0: Cargo.toml on main = 15.6.0 (ahead of the last cut tag v15.4.0, but that is the checked-out artifact, so it's the correct figure). Matches.
• Only dig.getRewardProverStatus served: confirmed by reading dig-node crates/dig-node-core/src/seams/dig_rpc/dispatch.rs directly -- getRewardProverStatus is wired (line ~773); listRewardDistributors / getRewardDistributor / listRewardDistributorCommitments do not appear in dispatch at all (they exist only in crates/dig-node-core/src/rewards/port.rs and funded.rs -- port-side, not dispatched). Matches 'unserved -> -32601'.
• CLAIM_CADENCE_SECONDS=86_400, CLAIM_JITTER_SECONDS=3_600: dig-rewards-coin SPEC.md §8.6 (lines ~1453-1454). Matches.
• payout_threshold = 1_000 base units = 1.000 $DIG: SPEC.md §8.3 line 1404. Matches.
• 200,000-mojo per-claim ceiling: dig-node crates/dig-node-service/src/rewards_claim/config.rs, CLAIM_FEE_CEILING_MOJOS_DEFAULT: u64 = 200_000. Matches.
• Three-consecutive-strike eviction: dig-rewards-coin SPEC.md §3.6 heading 'Eviction is three consecutive strikes, not one failure'. Matches.

Drift-gate scope check (docs.dig.net CLAUDE.md): scripts/dig-spec.mjs, docs/rpc/**, docs/support/error-codes.md, static/*.json are all ABSENT from this diff, correctly -- three of the four reward RPC methods are unserved and must not enter the machine-spec tables.

i18n: no new files under i18n// in this diff. Confirmed by full gh pr diff --name-only.

Blocking findings below, both reproduced from the PR's own CI runs (not re-derived):

1. Docusaurus build fails for the zh-CN locale: 'Docusaurus found broken links' on docs/audiences/reward-funders.md:116 and docs/run-a-node/earn-mirror-rewards.md:76 (run 34559377374). The English default-locale build compiles; the zh-CN locale build does not resolve the same relative links and the whole build step fails, which is why 'build + a11y/SEO tests' is red on this PR.
2. 'Check version increment' is red: package.json base=0.17.3, head=0.17.3 -- this repo gates every PR (docs-only included) on a version bump, and this PR does not carry one.

check-merge-preconditions.sh --repo DIG-Network/docs.dig.net --pr 87 exit code: 1 (BLOCKED) -- draft=true, mergeStateStatus=BLOCKED, 'Check version increment' and 'build + a11y/SEO tests' both COMPLETED/FAILURE.

Not reviewed (out of my lane): the money/roles content on these pages -- that is the parallel adversarial leg's job.