Add hosted registry install smoke coverage

[DeanoC]

Summary

• route the packages control-plane operations through the direct Spiderweb websocket control path
• extend the installer smoke test to exercise hosted registry discovery, update, and batch update flows
• update the SpiderProtocol submodule pointer for the new control message types

Testing

• zig build test
• OrbStack Ubuntu: timeout 1200 bash ./test-env/test-install.sh source

Depends on

• Add packages control message types SpiderProtocol#29

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2f64ae94c

ℹ️ 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".

[DeanoC]

Addressed the review by removing the hard-coded assumption from the installer smoke. The test now derives a one-patch-older seeded release from whatever version the hosted registry currently advertises, so it still exercises update behavior without depending on mutable external catalog state. Revalidated with and the full OrbStack Ubuntu smoke.

[DeanoC]

Addressed the review by removing the hard-coded 0.5.7 assumption from the installer smoke. The test now derives a one-patch-older seeded release from whatever version the hosted registry currently advertises, so it still exercises update behavior without depending on mutable external catalog state. Revalidated with bash -n test-env/test-install.sh and the full OrbStack Ubuntu timeout 1200 bash ./test-env/test-install.sh source smoke.