skills: v6.6.3 catch-up

[seidroid]

Skill catch-up for v6.6.3.

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

source PR	files touched	summary
sei-protocol/sei-chain#3978	skill/references/cli/seid-cli.md, skill/references/ecosystem/node-operations.md	Adds a new '--freeze-height' CLI flag and 'freeze-height' app.toml config field that stops a node before executing a target block while continuing to serve RPC, with validation constraints against halt-height/halt-time, grpc-only, state sync, seed mode, and Autobahn.
sei-protocol/sei-chain#4024	skill/references/cli/frozen-rpc-router.md, skill/references/cli/seid-cli.md	Adds a new frozen-rpc-router binary that proxies EVM JSON-RPC requests to live and freeze-height-frozen nodes based on block number, plus a new --freeze-height flag on seid start.
sei-protocol/sei-chain#4034	skill/references/cli/frozen-rpc-router.md	The frozen-rpc-router command adds a new --max-block-reference-depth CLI flag (default 16) to bound nested block reference parsing depth.
sei-protocol/sei-chain#4048	skill/references/cli/frozen-rpc-router.md	The frozen-rpc-router adds two new CLI flags, --batch-request-limit and --write-timeout, to configure JSON-RPC batch size limits and HTTP response write timeouts.

⛔ Failed final verification against the release tag

Each touched page was re-checked claim-by-claim against the v6.6.3 checkout after all commits were assembled. The items below contradict what actually ships at the tag and must be resolved before merging.

• skill/references/cli/seid-cli.md (Node Start (seid start) → --freeze-height, bullet: "Also settable via the freeze-height field in the [base] section of app.toml") — The freeze height is also settable via the freeze-height field in the [base] section of app.toml.
  • evidence: sei-cosmos/server/config/toml.go:44-47 renders freeze-height = {{ .BaseConfig.FreezeHeight }} inside the ManualConfigTemplate under the "Base Configuration" comment banner (toml.go:17-19), which is at the TOP LEVEL of app.toml with no [base] TOML section header. The first section header in the template is [state-sync] (toml.go:77); grep for [base] in toml.go returns no matches. There is no [base] section in app.toml, so the key does not live under a [base] section.

Reviewer notes

• Backport release/v6.6: Add freeze mode for historical EVM RPC sei-chain#3978 — The primary home for this change is node-operations.md, which already documents app.toml BaseConfig fields (halt-height is a natural sibling) and node startup/systemd usage. The seid-cli.md addition is a secondary/optional judgment call — that file focuses on wallet/query/tx subcommands and does not currently document 'seid start' flags at all, so a reviewer may prefer to keep the flag documentation solely in node-operations.md. No existing skill mentions halt-height, so this is net-new content in both cases.
• Backport release/v6.6: Add frozen RPC router and Docker integration cluster (#3989) sei-chain#4024 — The --freeze-height flag is already well-documented in both cli/seid-cli.md and ecosystem/node-operations.md, and the existing exclusive-boundary description ('settles at freeze-height - 1') matches the PR — so the freeze-height flag itself is largely covered and may only need a cross-reference to the new router. The genuinely new, undocumented artifact is the frozen-rpc-router binary and its CLI flags, which no skill file mentions; a new reference file is the primary gap. Proposed path cli/frozen-rpc-router.md fits the existing cli/ category; alternatively it could live under ecosystem/ since it's an operational proxy tool — judgment call left to the reviewer.
• Backport release/v6.6: Bound block reference parsing depth sei-chain#4034 — The change is a single new CLI flag on frozen-rpc-router, fully covered by the existing frozen-rpc-router.md skill. The flag bounds nested block-reference depth (e.g. EIP-1898 {"blockNumber": ...} objects); the router now returns an empty/unknown reference (routing to live) when depth exceeds the limit. A brief note on this routing behavior for over-deep references could also be added to the Routing behaviour section, but the primary gap is the missing flag entry. The seid-cli.md frozen-rpc-router mentions are only cross-references and need no change.
• Backport release/v6.6: Bound frozen RPC router batch allocations sei-chain#4048 — The frozen-rpc-router skill file is the only place documenting this command. The Flags table needs the two new rows, and the 'Other error codes' section should note that batches exceeding --batch-request-limit are rejected with code -32600 and message 'batch too large'. No other skill files reference these flags.

⚠️ 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.

Analyzing the pages for the specified issues.

• Contradiction on --freeze-height app.toml section (seid-cli.md): The new text says freeze-height is settable via the [base] section of app.toml, while node-operations.md (and the router page) treat it consistently—but within seid-cli.md itself it's stated as [base], whereas node-operations.md says BaseConfig section "alongside halt-height / halt-time". These are two different section names ([base] vs BaseConfig) for the same field across the update, but not on the same page — noting only same-page issues: no direct same-page contradiction here.
• sei_traceBlockByNumberExcludeTraceFail removal vs sei2_*ExcludeTraceFail remaining (node-operations.md): The "Removed (as of Sei v6.6.0)" bullet says the two sei_* block-trace endpoints are removed and can no longer be enabled, but then states the sei2_*ExcludeTraceFail block variants "all remain." Meanwhile the sei2_* namespace section lists "the *ExcludeTraceFail variants" as gated/enable-able methods. This is consistent (sei_ removed, sei2_ remain), so not a contradiction.

NONE

---

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