dsh-v0.1.2-alpha.1 this exact revision produced an empty manifest

[Ssrrb]

dsh-v0.1.2-alpha.1 serves DSH_BOOT with entries: [] and batches: [],
causing “HTML did not preload @deepseek-ai/dsh-client-modules/client.js”.

[denial123789]

I added an Agent-first runbook for this exact boundary: empty __DSH_BOOT__ manifest triage, released in v0.5.399. It treats entries: [] / batches: [] as a Host-side inventory or build-output problem, preserves the raw HTML, and checks profile, launch revision, resolver errors, and /plugins before browser cache changes.

[173787247]

entries: [] / batches: [] means this is a Host boot-manifest problem, not a flaky browser cache. HTML did not preload …/dsh-client-modules/client.js is the downstream symptom: the page loads modules from __DSH_BOOT__, and an empty manifest fails immediately.

Narrow it in this order (before hard-refreshing the browser):

1. Confirm you are running the revision you think you are: dsh --version, and that the launch command points at the same install (global vs project node_modules).
2. Check the start terminal for plugin / client-modules resolve errors. Fix those first; do not clear cache yet.
3. Open the returned HTML, search for __DSH_BOOT__, and keep a copy of the raw JSON. If it stays empty, restart with a clean profile / no third-party plugins:
   • Clean profile gets a non-empty manifest → some plugin/patch zeroed the inventory.
   • Still empty → more likely this alpha.1 install/build is missing client modules.
4. If the same machine is fine on 0.1.1-rc.2 and only empty on 0.1.2-alpha.1, treat it as a revision/install issue first, not local UI config.

A hard refresh only helps after the Host is already serving a non-empty manifest. If the Host keeps returning [], clearing the browser will not fix it.