Repository navigation
Release v4.44.1
Added
- Regression coverage that annotates every line of the canonical corpus and a sample model with a unique comment and checks that each comment survives exactly once, never shares a printed line with another, and prints the same way twice.
Fixed
- Trailing comments stay on their intended printed lines for the remaining line kinds that were placed by source offset: other descriptions, behavior order, reaction triggers, values and conditions, and interaction triggers, conditions and continuations. The offset fallback is gone.
- Comments no longer merge into a declaration's header comment, or move onto an opening code fence (where reparsing dropped the whole code block), for repeated interaction directives,
arrangementheaders, legacy code-language lines and multi-lineauthorize/require … orcontinuations. - When a single-valued directive is repeated and the last one wins (for example
file, queryby, commandhandler, capturesource, projectionparent, tableon row-click, actionlabelornavigate), comments on the replaced lines keep their own lines instead of joining the header comment.
The final review rounds were done by a single model provider (Claude Opus); cross-provider review was unavailable.
Closes #293