skills: v6.6.2 catch-up - #17
Conversation
…ed nodes for known public networks (pacific-1, atlantic-2), and the --chain-id flag is now documented as required. (sei-protocol/sei-chain#3954)
The new section was inserted between the Setup heading's intro line and its own build block, which left the clone/build steps and the Requirements list sitting under `## Node Initialization` rather than `## Setup`. Moved it to a sibling section ahead of Network Reference; the move is otherwise lossless. Also completes the --mode bullet with archive, which the synopsis above it already listed and cmd/seid/cmd/init.go accepts (it runs as a CometBFT full node but takes archive-specific app and EVM config).
PR SummaryLow Risk Overview The new text states that Reviewed by Cursor Bugbot for commit 7a7b60c. Bugbot is set up for automated code reviews on this repo. Configure here. |
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.
skill/references/cli/seid-cli.mdReviewer notes
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.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
--modevalues: The newseid initsynopsis lists[--mode full|validator|seed|archive](witharchive), but the following bullet describes onlyvalidator/seed/fulland says "Default mode isfull" — while the untouched section header shows--mode full|validator|seed|archive. (Minor, but the bullet's enumeration omitsarchive; 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 = falsepanics." This describessc-enableas both a removed/mandatory feature and a still-settable config option (sc-enable = falsecan be set to trigger the panic). This is the "removed and configurable" pattern.NONE of the newly inserted
Node Initializationtext 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:
sc-enable(legacy IAVL "fully removed"/"mandatory" yetsc-enable = falseis a settable value).Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.