fix(deps): align inspector with merged module builder

[3esmit]

Closes #373

Summary:

• pin module-builder and protocol inputs to the merged fork revisions
• consume the merged storage-module API fix
• expose the sibling core module output to the QML module builder
• update release-workflow revision policy and regenerate the lock file

Validation:

• cargo fmt --all -- --check
• nix flake check --no-build --accept-flake-config
• nix build .#packages.x86_64-linux.default --no-link --accept-flake-config -L
• python3 scripts/check-build-pipeline.py ci (all checks passed, including 1,452 Rust tests, 1,325 QML tests, native CTest, UI checks, Clippy, and headless CLI)

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-18T07:28:35.531403Z	1c2f12e	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ddf9bfff72

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Gate the warning on an outstanding catalog target

When the catalog is fully synchronized and the finalized LIB remains unchanged, made_progress is naturally false even though chain_status() succeeded and the cursor already equals target. After three such healthy polling rounds, this branch publishes an error claiming that Bedrock is unreachable, and the error remains until another catalog commit occurs. Track whether the cursor is actually behind the target (or whether a range request unexpectedly returned no events) before publishing the stalled-source warning.

Useful? React with 👍 / 👎.