[v0.5] Reviewer Response Matrix

[JUhalt]

Goal

Turn reviewer/editor feedback into a structured, trackable revision workflow.

Scope

• Reviewer/editor identity or label.
• Individual comment/action item.
• Status such as unresolved, in progress, addressed, or not applicable.
• Draft response text.
• Manuscript location/page/section reference.
• Notes and links to the relevant editorial decision/revision round.
• Exportable response-to-reviewers draft.

Acceptance

• Matrix items remain linked to the correct submission and decision round.
• Users can complete the matrix entirely without AI assistance.
• Export produces editable human-readable output without changing matrix data.
• Multiple reviewers and multiple revision rounds remain distinct.
• Persistence, ordering, and export are regression-tested.

[JUhalt]

Development started on the first usable v0.5 increment after v0.4.0 release closure.

• Manual matrix within an existing journal submission, with explicit decision and revision-round references.
• Reviewer/comment/action/status, response drafts, manuscript locations, and notes.
• Status filtering, stored ordering, and editable Markdown export.
• Child-dialog save/cancel boundaries and conservative Schema 5 to 6 persistence so older applications cannot silently discard reviewer responses when opening a newer library.
• Regression coverage for references, save/load, ordering, clone/cancel behavior, migration failure safety, and nonmutating export.

The narrow/high-DPI shelf follow-up #37 is being brought forward in parallel at the user's request. These are development changes, not a v0.5 release or completed certification. Implementation PRs and observed checks will be linked here when ready.