v6.0.0: Observability module fails to load — 'yaml' imported but not declared in package.json (dashboard/APIs 404)

[badosanjos]

Summary

On a fresh v6.0.0 install, the Pulse Observability module fails to load because the yaml package is imported by PULSE/Observability/observability.ts but is not declared in PULSE/Observability/package.json (nor in PULSE/package.json). The unified daemon starts, but every dashboard page and /api/* route served by the observability module returns 404.

Environment

Ubuntu 24.04 (case-sensitive fs), bun 1.2.x (user install), Claude Code harness, LifeOS v6.0.0 installed via the offline bootstrap (LIFEOS_SRC), Pulse installed with PULSE/manage.sh install (systemd user unit).

Repro

1. Fresh install of the LifeOS skill; run the Setup toolchain (DeployCore etc.).
2. cd ~/.claude/LIFEOS/PULSE && bash manage.sh install
3. bun install in PULSE/ and PULSE/Observability/ + bun run build in Observability (dashboard builds fine).
4. Start Pulse and check logs.

Observed

{"level":"warn","msg":"Observability module not available","error":"ResolveMessage: Cannot find package 'yaml' from '.../PULSE/Observability/observability.ts'"}

Root / and /api/telos/overview → 404 while /healthz and /api/wiki (wiki module) work.

Expected

Observability module loads after a standard bun install.

Fix

Declare yaml in PULSE/Observability/package.json dependencies. Verified locally: bun add yaml in Observability/ → restart → module loads, dashboard + APIs 200.

Happy to send a one-line PR for this.

[danielmiessler]

Thanks for the clean diagnosis and the verified fix — you were exactly right. yaml is now declared in PULSE/Observability/package.json in the development source, so a standard bun install brings the Observability module up. The public repo is regenerated from source at release time, so this ships with the next release. Closing as integrated.