Skip to content

docs: refresh snapshot operator guidance + tx submission caveats#22

Open
mikedotexe wants to merge 5 commits into
mainfrom
docs/snapshots-and-tx-guidance-refresh
Open

docs: refresh snapshot operator guidance + tx submission caveats#22
mikedotexe wants to merge 5 commits into
mainfrom
docs/snapshots-and-tx-guidance-refresh

Conversation

@mikedotexe
Copy link
Copy Markdown
Collaborator

Summary

Salvages three small docs commits from #16 (codex/agent-readiness-phase1) that were not captured by #18 (codex/agent-discoverability-core) or any of the recent example-tightening sweeps:

  • fba0924 Tighten snapshot and transaction guidance — reframes `docs/snapshots/index.mdx` (en + ru) from a self-serve download tutorial into a status/escalation page reflecting reality ("FastNear does not currently publish a working public self-serve snapshot download flow from this docs site"). Tightens `mainnet.mdx` and `testnet.mdx` to match. Adds a one-liner to `broadcast-tx-commit.mdx` and `send-tx.mdx`: "Use a freshly signed base64 transaction for each request. The sample payload shown in the interactive docs is illustrative only and will fail if you paste it unchanged."
  • b260b03 Refine snapshot operator guidance — adds "Useful operator references" (links to NEAR Nodes state-sync, archival, and split-storage guides) and "What to have ready before you request archival access" (operator checklist).
  • d77610f Clarify boot node refresh for snapshot bootstrap — small clarifications across `mainnet.mdx` and `testnet.mdx` about boot-node refresh.

Plus a regen commit so `static/ru/**` matches current authored content (snapshot pages reflect the new structure; non-snapshot files are regenerator catching up to drift that already existed on `main`).

Why now

These three commits were on `codex/agent-readiness-phase1` (PR #16, the "first attempt" superseded by #18) which is being closed. Pulling them out into a focused PR so the snapshot/tx clarifications aren't lost.

The rest of #16 is either superseded (the agent-readiness static surfaces, now in #18) or intentionally cut (the MCP guide).

Test plan

  • `yarn build` clean (en + ru both compile)
  • `node scripts/audit-indexing-surface.js` clean (`Indexing surface audit passed for 105 explicit docs routes, 78 docs operation pages, and 78 hosted operation pages.`)
  • `yarn audit:ru-terminology` clean (106 files scanned)
  • Spot-check rendered snapshot pages — current-status framing matches the deprecation reality

mikedotexe and others added 4 commits April 25, 2026 12:18
Snapshot pages reflect the new "Current status / Useful operator
references / What to have ready" structure. Other static/ru/* files
are regenerator catching up to main's already-authored content
(no source changes outside the snapshot/tx commits).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Apr 25, 2026

Deploying builder-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: d85b0ac
Status: ✅  Deploy successful!
Preview URL: https://9bad1e33.builder-docs.pages.dev
Branch Preview URL: https://docs-snapshots-and-tx-guidan.builder-docs.pages.dev

View logs

Russian terminology audit flagged "boot nodes" as suspicious untranslated
English. Match the precedent set in mainnet.mdx and testnet.mdx, which
refer to the config field as `boot_nodes` (backticked). The link is
about updating that field before first start, so the config-field form
is the natural reference and passes the i18n gate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant