[Feature] An entry that fails to activate is only a launcher warning while health stays 200 — make it fatal or visible to readiness

[xiangxiaoyong]

Version: 0.2.0-rc.2 (launcher / dsh-app-boot, Web profile)

Problem. When a composition entry throws during apply, the launcher only prints dsh: warning: 1 entry did not activate. Examples: an invalid config value, such as time-context with timeZone: Not/AZone; a missing injected service. The process keeps running and the Web health endpoint answers 200. A deployment health check or readiness probe therefore cannot tell that a plugin is missing, and a release ships without it silently.

Repro. Add a user patch - id: time-context\n config:\n timeZone: Not/AZone and start a Web profile. You get the warning on stderr, and health and readiness stay OK.

What we do today. A CI smoke boots our composed profile and fails if the launcher output contains "did not activate".

Ask. Choose one or both:

• a launcher option (or profile setting) that makes an inactive entry fatal at startup;
• an official readiness signal that reports inactive entries, so orchestrators can hold the rollout.