[SaladDay]

Summary

Phase 0 of the new-user install work: small fixes that make a first install less confusing. None of them needs a product decision.

• Installer output (deploy/install/install.py):
  • With a public URL, it prints the public Console URL and API base URL (<public_url>/v1), plus Core's loopback /v1, labelled local-only.
  • A loopback --public-url is labelled local-only. If that URL is on Web's port, the installer prints Core's own loopback /v1 instead, because Web answers 404 on /v1.
  • The next step points to Web: sign in with the Core key file, then create a Project and key on Projects and keys. Core-only installs get http://127.0.0.1:<core_port>/core/v1 (local only).
• Local node defaults: the installer's local Docker node now starts at 2 CPU / 2048 MiB, matching Web. Microsandbox is unchanged and already matched.
• Distribution build on Docker 29's containerd image store (scripts/build-core-distribution.sh, core-distribution-manifest.py built-image):
  • Images are built with --provenance=false and a build metadata file. The tool records the one digest the local store resolves to itself.
  • The database image is pinned by its linux/amd64 manifest digest (postgres:16-alpine@sha256:1a66d744…), so the export is a single platform on both stores.
  • Recorded identities stay exactly as strict: the real config digest and OCI manifest digest of each exported image. Any ambiguity or mismatch fails the build.
• Docs:
  • README local-provider commands include the required --public-url.
  • E2B CPU and memory are documented as optional; Core adopts the template build's size.
  • Core's images are described as the digest-pinned debian:bookworm-slim base.
  • UI names match Web: Nodes, Save configuration, Projects and keys.
  • Corrected: the release tag format, the scope of --offline-root, the landing-page release text, E2B management wording, .env.example, and "account setup" wording in web-management.md.

Review

• An independent blind review of the full diff found:
  • one P1: the containerd-store build still failed on the multi-platform PostgreSQL index. It failed closed, but only at the end of the build;
  • one P2: the loopback --public-url label;
  • several P3s.
• All were fixed in 1db8de90 and 08064743. With a single P1 that had a local fix, the fixes were verified by targeted checks and the gate rather than a new review round:
  • a two-platform test image on the containerd and classic stores, reproducing the failure with the old default and passing with the pinned digest;
  • new installer and manifest-tool tests.

Verification

• Full local server gate on 08064743 (the exact head): passed.
• Playwright browser cases were skipped on the server (Chrome unavailable; the skip is approved).
• Installer tests: 130 OK. Manifest tool tests: 13 OK. bash -n passes, git diff --check is clean, and the relative-link check over the changed docs passes.
• A full distribution build was not run on this host: it can't reach Docker Hub for the other pinned base images. The changed build steps were verified in isolation on Docker 29.1.3, on both image stores.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}