Two defensive fixes surfaced by the PR #95 review (PR-Agent), applied on
top of the staging sync:
1. directScene: routeTaggedStream rejecting BEFORE onPlan fires would leave
planPromise unsettled, hanging `await planPromise` — and thus the whole
/api/start and /api/scene request — forever. Add a .catch that settles
the plan with a minimal fallback and resolves routing to a degraded
result, so the pipeline produces a playable fallback scene (graceful
degradation) instead of hanging.
2. prompts/registry: the duplicate-segment-ID guard only ran under
NODE_ENV=development, so a bad merge introducing a duplicate ID would
silently shadow a segment in production. Run the check in all
environments (once at module load; negligible cost).
Kai ki
e31bd16b15