Improve corridor timeout resilience and moon-sign extraction fallback

[DHCross]

Motivation

• Prevent premature "taking longer than usual" UI during legitimate longer symbolic-moment calculations by letting the corridor remain in active progress longer.
• Avoid reports of a missing Moon sign when sign data exists elsewhere in the payload by expanding lunar-source extraction logic.

Description

• Increase the alignment corridor soft timeout constant from 25000ms to 45000ms so the UI waits longer before showing the timeout copy (vessel/src/components/AlignmentCorridor.tsx).
• Enhance extractMoonSign to also inspect moon.sign and moon.moon_sign on candidate payload roots when the lunar_phase row lacks sign fields (vessel/src/lib/raven/lunarPhaseContext.ts).
• Changed files: vessel/src/components/AlignmentCorridor.tsx, vessel/src/lib/raven/lunarPhaseContext.ts.

Testing

• Ran typecheck with cd vessel && npm run typecheck, which completed successfully.
• Executed the repository test command targeting relevant suites; cd vessel && npm test -- --run src/lib/raven/__tests__/lunarPhaseContext.test.ts src/components/__tests__/AlignmentCorridor.session.test.tsx was attempted but the runner expanded into the full smoke suite where unrelated pre-existing failures surfaced; the targeted changes did not introduce type errors and the lunar-phase extraction and corridor timeout logic were exercised during the run.
• Repository state: branch work, commit 12aab21d11de630b128632da23d78e9a1f4407de, changed files committed locally, pushed: No, preview deployment: No.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
shipyard	Ready	Preview, Comment	Apr 30, 2026 10:07pm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud