No stories found error in Storybook core server when story glob matches no files

When Storybook’s dev server starts with a story glob that matches no files, it reports the “No stories found” condition and shows an empty state in the manager UI.

The goal is to define a stable default behavior for handling duplicate story IDs or titles that may arise from multiple config entries or addon‑provided stories, ensuring consistent ordering without unintended write duplication during retries.

Current behavior varies with the builder and storyStore version, and no official policy has been settled, leaving the order implementation‑dependent.

What criteria should Storybook apply to deduplicate stories that share the same ID or title? Should the default sort follow file‑path order, story name, or the order of configuration entries? How should the chosen policy be communicated to developers through logs or the manager UI?