Release v4.234.1

Fixed

• Proposing and applying a change through the Screenplay MCP server is faster on large models: a proposal reuses the syntax index and reference layout it has already built for each revision, and applying it reuses the proposal's workspaces instead of rebuilding them for the recovery journal. On a 260-file model, a propose uses roughly a quarter to a third less CPU time and an apply about seven times less. (#978)