[SaladDay]

A sandbox node runs the Runtime from its own installation. Core no longer accepts, stores or derives a Runtime image from the API, and the node wire no longer carries software versions or upgrade signals.

• Deployment spec: {provider, resources, workspace}. Docker reads native.image from the node's provider.json; microsandbox takes image, runtime_sha256 and firmware_sha256 from the installer's verified manifest.
• Removed from the node protocol:
  • generation management;
  • protocol versions and update_required;
  • NEWER_NODE_SOFTWARE;
  • runtime_download_failed;
  • the generation journal;
  • Health.ProviderReady and Health.Diagnostic.
• Removed from /core/v1: node.diagnostic. node.provider_ready stays because Core computes it (Online && ServingReady).
• Database: forward migration 000002_remove_dead_node_columns.sql drops runtime_nodes.provider_ready and protocol_version.
• One way to add a node: Web's install command. oac-node run needs the installer's layout, so the manual registration guide and its references are removed.
• Web and docs: the setup wizard and deployment settings no longer ask for a Runtime image. The node protocol, deployment and node setup docs are updated in English and Chinese.

Checks run

• go build ./... and go vet (services/core, apps/daemon, internal, services/web) pass.
• Go tests pass in the touched packages, including the integration package against Postgres 16.
• make check-docs passes.
• deploy/node Python tests pass.
• Web tsc and vitest pass, as do the agents-client vitest tests.
• The Playwright browser specs run in CI (web-acceptance).

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

Test	View Logs
e2e/ monitoring.spec.ts:10:1 › shows the deployment's health on Overview and each monitor pa ge ─	View Logs
e2e/ nodes.spec.ts:329:1 › keeps the page usable when Core refuses a sandbox change, and sho ws a safe refusal	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}