skills: v6.6.2 catch-up

[seidroid]

Skill catch-up for v6.6.2.

1 source PR(s) produced changes across 1 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.

source PR	files touched	summary
sei-protocol/sei-chain#3954	skill/references/cli/seid-cli.md	seid init now auto-populates bootstrap-peers with Sei Labs seed nodes for known public networks (pacific-1, atlantic-2), and the --chain-id flag is now documented as required.

Reviewer notes

• Backport release/v6.6: feat(seeds): ship Sei Labs seeds as the default bootstrap-peers sei-chain#3954 — The core behavior change (auto-populated bootstrap-peers + required --chain-id) is operator-facing and best documented in node-operations.md, which already covers seid init usage. The seid-cli.md reference does not currently document seid init at all — this is more of an add_section than a targeted update, but flagged as update since the file exists and lacks any init coverage; a reviewer may prefer to fold it into node-operations.md only. The new app/seeds Go package is internal (built-in seed data) and does not itself warrant a standalone skill file, since operators interact with it only indirectly via seid init.

⚠️ Possible contradictions or misplaced sections

Flagged by a review of every touched page's final text. Each source PR was analysed in isolation, so these were invisible to the per-PR checks. Verify before merging — the checker cannot tell which side of a contradiction is correct.

Comparing the new text against the untouched surrounding text:

• Contradiction on --mode values: The new seid init synopsis lists [--mode full|validator|seed|archive] (with archive), but the following bullet describes only validator/seed/full and says "Default mode is full" — while the untouched section header shows --mode full|validator|seed|archive. (Minor, but the bullet's enumeration omits archive; not a hard contradiction.)

• Contradiction on IAVL/SeiDB backend vs. configurability: The untouched "Proofs" bullet says "The legacy IAVL backend has been fully removed and SeiDB SC is mandatory — a node started with sc-enable = false panics." This describes sc-enable as both a removed/mandatory feature and a still-settable config option (sc-enable = false can be set to trigger the panic). This is the "removed and configurable" pattern.

NONE of the newly inserted Node Initialization text itself contradicts the untouched text, is misplaced under a contradicting heading, or misspells identifiers consistently used elsewhere.

Given the criteria, the only clear qualifying item is:

• A setting described as both removed/mandatory and configurable: sc-enable (legacy IAVL "fully removed"/"mandatory" yet sc-enable = false is a settable value).

---

Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.