create --type bugfix
fix: peer-propagated updates never carry the docs bundle — a node updated from a peer keeps the PREVIOUS release's docs (SCELTOUIN on 0.72.0 serves the 0.71.0 changelog)
**Symptom.** SCELTOUIN runs spt 0.72.0 (counter 108, applied) but `http://localhost:5474/sceltouin/docs/changelog.html` tops out at `## [0.71.0]`. HFENDULEAM, which fetched 0.72.0 from GitHub, serves 0.72.0.

**Root cause (code).** Docs ride the update only on the `spt update fetch` GitHub path (`cli.rs` ~11177 fetches `spt-docs.tar.gz`, `cache.stage_docs`). The peer-propagation pull has no docs leg at all: `UpdRecord` (spt-net `net/update.rs`) has `Fetch`/`FetchArtifact` only, and `propagate.rs` ~533 stages just this platform's binary via `stage_update_set`. On apply, `land_staged_docs` (`cli.rs` ~9749) reads the absent staged bundle as "docs-less release" and returns SILENTLY — no `UPDATE_DOCS_SKIPPED`, and no retry ever comes because a propagated node never runs `fetch`. The serving peer can't help either: it `clear_staged_docs()` right after landing (`cli.rs` ~9827), so it holds nothing to serve.

**Contract breached.** REQ-DOCS-RELEASE-ASSET: "Apply lands/refreshes $SPT_HOME/docs (single current copy = docs always match the installed binary)" and "UPDATE_DOCS_SKIPPED loud, retried next fetch". Every node except the GitHub-fetching one is on stale docs after every release.

**Ask.** (1) Keep the verified docs bundle in the release cache after landing so a peer can serve it. (2) Add a docs leg to the pull protocol (`FetchDocs`), requester verifies with `verify_update_set_docs` against the SIGNED set and `stage_docs`. (3) When the signed set declares docs but none is staged, `land_staged_docs` must print `UPDATE_DOCS_SKIPPED`, never return silent. Evidence in comment.