Codex/fix raven status legacy stack

[Arunkumar-Annamalai]

Summary

Fixes raven_status crashing when .raven/manifest.json uses the legacy flat manifest shape.

Before this change, Raven assumed manifest["stack"] was always an object and called .get("language") / .get("cloud") on it. In projects where the manifest used the older format like:

{
  "stack": "react",
  "cloud": "none"
}

raven_status failed with:

'str' object has no attribute 'get'

This update makes Raven compatible with both manifest formats:

• legacy flat format: "stack": "react", "cloud": "none"
• nested format: "stack": { "language": "react", "cloud": "none" }

What changed

• Added a normalize_stack() helper to normalize manifest data before reading stack fields
• Updated raven_status to use normalized language and cloud values
• Applied the same fix to both Raven server entrypoints so Codex and script-based flows behave consistently

Files changed

• mcp/server.py
• scripts/server.py

Verification

• Ran mcp/server.py directly against a legacy flat manifest
• Ran scripts/server.py directly against a legacy flat manifest
• Confirmed raven_status now returns success instead of crashing

Result

raven_status now works for both old and new Raven manifest schemas without requiring existing projects to migrate their manifest immediately.