Show service links and next steps after local startup

docs/local-development.md

@@ -30,6 +30,21 @@ AppRoles and secrets, initializes Mongo replica set `rs0`, configures Vault's Mo
 plugin, and starts authenticated NATS JetStream. Product startup fails explicitly
 until Resend credentials exist. Infrastructure remains available for provisioning.
 
+After all services pass their startup health checks and the public Caddy CA is
+exported, `make up` prints a Sendico-style completion message with the frontend,
+API, API health and Vault URLs, the CA trust reminder, and status/log/stop commands.
+Failed startup does not print the success message. Mongo and NATS are private
+Compose services, so the summary does not advertise host URLs or credentials for
+them. This terminal-only change reuses Compose errors and the command exit status
+as startup outcome signals; it adds no analytics or secret output.
+
+Completion-message validation: `make test-dev-tooling` and `git diff --check`
+passed. A containerized shell preview with stubbed infrastructure calls confirmed
+the success layout and that failed service startup or CA export exits nonzero
+without the message. The UX review checked readable plain-text labels, actionable
+URLs/commands and confirmed-success timing. This check did not restart the live
+stack or verify application readiness.
+
 ## Vault layout
 
 Paths below are inside the KV v2 mount `kv`; the API inserts `data/` after `kv/`.