localnet up reports Splice 0.6.14 ready while splice is still syncing

[zheli]

Finding

localnet up reports a Splice 0.6.14 instance as ready while the splice service is still syncing. The registry then changes the instance to partial, so Token V2 actions cannot resolve the participant endpoint.

Environment

• DevKit commit: 317e235
• Splice: 0.6.14 at resolved upstream commit 398919a
• Docker: 29.6.2
• Docker Compose: 5.3.1
• Browser route: http://127.0.0.1:7777/tokens?instance=<test-instance>

Splice 0.6.14 required --allow-uncurated. Docker reported 8.84 GB available and recommended 12 GB.

Reproduction

1. Build the current worktree with make ui.
2. Run bin/canton-devkit localnet up <test-instance> --version 0.6.14 --allow-uncurated.
3. Wait for the command to print that the instance is ready.
4. Start bin/canton-devkit localnet ui --port 7777.
5. Open the Tokens page and select the test instance.
6. Click Launch demo.
7. Inspect instance status after the action and again after a bounded 10-minute wait.

Observed

• localnet up printed that the instance was ready after 6 minutes 9 seconds.
• The dashboard initially showed 9 of 12 healthy containers.
• POST /api/tokens/demo?instance=<test-instance> returned HTTP 412 with code NEEDS_V2_LOCALNET.
• The UI displayed: This action needs a running Splice 0.6.11 or newer LocalNet (localnet up --version 0.6.12).
• Status reported the instance as partial; 11 services were healthy and splice remained syncing after another 10 minutes.
• The issue 308 invalid-transfer-preview regression could not be reached through the Web UI because no token or party could be provisioned.

Expected

localnet up must not report ready until all required services satisfy the health condition used by registry status and endpoint resolution. Once ready, Token V2 actions on Splice 0.6.14 should resolve the recorded app-provider participant endpoint.

Evidence

• Screenshot: artifacts/chrome-devtools/splice-0614-v2-gate.png
• Browser console: the demo request produced a normal HTTP 412 resource error; no connection reset occurred at this stage.