Release v4.144.0

Summary

Record open questions, tasks and review notes against model elements. Notes live in a committed .screenplay/notes.json beside the model, follow elements through rename and move, and never change the executable model or any revision. See the new model notes page.

Added

• Model notes: question, task and note entries anchored to a model element's semantic ID or the application, with an open or resolved state, free-text author, and references to external decisions such as D123. A question can be resolved by a specification, a description, a decision, an external decision, or dismissed. Notes on an element without its own identity attach to its owning slice, feature, module or the application (#391)
• MCP tools list-model-notes (filter by anchor, scope, kind, state or reference; view: "findings" returns one model-note.open-question finding per open question) and propose-model-notes (add, edit, resolve, reopen, reanchor and remove), reviewed with read-proposal view: "notes" and written by apply under the same recovery journal as the model (#391)
• Source, AST, rename, move and property proposals report orphanedNotes when they would retire an element that notes are anchored to. Orphaned notes are kept and listed until they are re-anchored or resolved (#391)
• screenplay check --open-questions report|fail lists open questions and, with fail, exits 1 while any remain in the checked scope (#391)
• The notes file format is published as notes-v1.schema.json (#391)

Changed

• open-workspace and workspace-state report the notes revision and whether the notes file is readable. A malformed or conflicted notes file never blocks opening a model; note tools refuse to write until it is fixed (#391)
• Recovery journals that include notes are written as version 2, which older servers refuse instead of rolling back without the notes file (#391)