[clauderic]

What are you adding in this PR?

A theme without an assets folder never gets a theme graph in the language server.

• getWebComponentMap reads assets/ without checking that it exists. For a theme without one, it rejects, and so does building the graph.
• ThemeGraphManager caches the graph as a promise. Its rebuild on file changes awaits the cached promise before replacing it, so it rejects too and the graph is never rebuilt. Creating the folder doesn't help; only restarting the server does.
• Until then, references and dependencies come back empty. OrphanedSnippet and ValidScopedCSSClass get the error when they ask the graph for references.

Now a missing assets folder means no web components. Other errors, like an assets folder that can't be read, still reject. The check uses theme-graph's existing exists helper, which is a stat.

What's next? Any followup issues?

• Rebuild a theme graph that failed to build #1349, stacked on this, fixes the rebuild: any other error while building the graph left the language server without a graph until it restarted.
• Add executable check specs #1347, at the top of the stack, has graph specs that include a theme without an assets folder.

Tophatting

• npx vitest run packages/theme-graph/src/getWebComponentMap.spec.ts. Without the fix it fails with Directory not found: file:///assets.

Before you deploy

• I included a patch bump changeset
• My feature is backward compatible

🤖 Generated with Claude Code