RSP 3.1.1

RSP 3.1.1

RSP 3.1.1 hardens structured commit-message delivery so multiline bodies remain correct across tool, shell, and Git boundaries. It includes the complete stable 3.1 workflow described in the 3.1.0 release notes.

Reliable multiline commit messages

• Require actual line breaks or a safely prepared message file for structured multiline commit bodies instead of relying on shell interpretation of \n.
• Inspect the raw committed message after Git succeeds and treat unintended literal \n sequences as a post-commit mismatch.
• Stop and report the mismatch without inferring amend, second-commit, or other history-repair authority.
• Retain a focused Skill contract test for the transport and post-commit observation requirements.

Upgrade

RSP 3.1 requires Node.js 22 or later. Use the stable package, then refresh managed project files and package-owned Skills separately:

npx -y @oevery/rsp@latest update
npx -y @oevery/rsp@latest skills install --dry-run
npx -y @oevery/rsp@latest skills install
npx -y @oevery/rsp@latest doctor

RSP 3.1.0 remains available as a GitHub release but was not published to npm. Version 3.1.1 is the first stable 3.1 package published to the registry. Registry users upgrading from 2.x must follow the 3.0 migration guide, then apply the 3.1 migration guide.

Compatibility and known limitations

• This patch changes the packaged rsp-commit operational contract; it does not add a CLI commit command or make arbitrary shells reinterpret escape sequences.
• Existing Change, archive, configuration, and CLI behavior remains compatible with 3.1.0.
• Push, tag creation, hosted release publication, registry publication, deployment, approval, amend, and other history repair remain separately authorized operations.

Full comparison: v3.1.0...v3.1.1