feat: sync content with v2.8.1

[yjkellyjoo]

What does this PR resolve? 🚀

Updates the docs for the upcoming Bee v2.8.1 release (new config options, upgrade path, dev-mode removal), and adopts a one-sentence-per-line writing convention.

Details 📝

• Merge before the automated OpenAPI update. That workflow's openapi-auto-update PR bumps the version strings and, on merge, tags the commit v2.8.1 and publishes the site — so this hand-written content must land first. (Also why version strings aren't bumped here.)
• Config blocks in configuration.md are regenerated verbatim from a v2.8.1-rc4 build, so the diff includes rc4 changes beyond the two headline flags.

Checklist ✅

• Merged latest master and resolved conflicts
• npm run build succeeds
• Links checked (npm run check:links) where relevant
• static/llms.txt updated if pages were added / renamed / deleted
• Content follows CODING.md conventions (Swarm vs swarm, ..)
• Self-reviewed the diff
• Commits are signed off (git commit -s)

---

[netlify]

✅ Deploy Preview for test-twitter-preview-testing-3 ready!

Name	Link
🔨 Latest commit	e9f395b
🔍 Latest deploy log	https://app.netlify.com/projects/test-twitter-preview-testing-3/deploys/6a44e2cd77eca30008979d03
😎 Deploy Preview	https://deploy-preview-824--test-twitter-preview-testing-3.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[GasperX93]

Thanks for this — solid v2.8.1 sync. The regenerated config dump correctly drops the leaked password value and the removed flags, the Sepolia anchor link resolves, and the bee dev → bee-factory link changes keep working via the id: bee-dev-mode slug. A few documentation-consistency items before merge:

1. Contradictory descriptions of --chequebook-verification
The regenerated flag help now reads "reject full-node hive/handshake records that carry no chequebook address", but the prose here (Chequebook Verification section) and in staking.md still describe it as a balance-threshold check ("rejects peers whose balance falls below the configured threshold"). Those are two different mechanisms. Since the flag table was regenerated from rc4 but the prose wasn't, readers get contradictory answers. Could we confirm the actual v2.8.1 behavior and reconcile the wording (and clarify how it relates to chequebook-min-balance)?

2. staking.md is stale after the PLUR unit change
docs/bee/working-with-bee/staking.md still says "The default minimum balance threshold is 11 BZZ and can be adjusted with --chequebook-min-balance." With this PR the flag now takes PLUR (smallest units) — default 110000000000000000. A reader following that page would pass --chequebook-min-balance 11, which now means 11 PLUR (≈ 0 BZZ) and silently disables the threshold. Suggest adding the same PLUR caveat or linking to the configuration section.

3. Verify the block-sync-interval: 0 claim
The section states "0 is not allowed; the node treats it as 'no interval' and clamps it to 1." This is a specific runtime assertion aimed at rate-limited-RPC operators — worth double-checking against the Bee source that 0 actually clamps to 1 (vs. erroring or disabling refresh) before it ships.

Minor: the api-addr default changed from 0.0.0.0:1633 to 127.0.0.1:1633 in the regenerated dump. If that's a real rc4 default change (API now localhost-only), it's an operator-facing behavior change worth a one-line call-out, since remote API access would break for anyone relying on the old default.

The BZZ→PLUR math itself checks out (16 decimals: 11 × 10^16 = 110000000000000000). Nice cleanup overall.

[yjkellyjoo]

1. False positive. staking.md describes the flag correctly: --chequebook-verification can be turned on to reject incoming peers whose chequebook balance falls below a configurable threshold, and the minimum balance threshold is adjusted with --chequebook-min-balance.
2. Also false positive. staking.md Chequebook verification section says to "See the configuration page for details." and the configuration page specifically explains to set the value in PLUR.
3. Yes, verified and true.

[GasperX93]

Thanks for checking each point, Kelly — you're right: 1 and 2 are false positives on my end (the flag does both the address and balance checks, and staking.md already links to the PLUR explanation). Appreciate you verifying point 3. LGTM, approving. 🚀