docs: update the v1.2.2 release notes

README.md

@@ -18,7 +18,7 @@ That gating follows slothlet's own rule about **who is calling**: a call made by
 
 ### Latest: v1.2.2 (October 2026)
 
-- **Dev-tooling dependency bump ([#72](https://github.com/CLDMV/slothlet-vine/pull/72))** — `@cldmv/fix-headers` moves from 2.1.1 to 2.1.4, the tool that maintains the repository's file headers. It produced no header changes here, so only `package.json` and the lockfile changed. No runtime source changed and the peer ranges are the same as in v1.2.1 (`@cldmv/slothlet >=3.22.0`, optional `ws >=8.0.0`); it's a drop-in replacement for v1.2.1.
+- **Dev-tooling dependency bump ([#72](https://github.com/CLDMV/slothlet-vine/pull/72), [#75](https://github.com/CLDMV/slothlet-vine/pull/75))** — `@cldmv/fix-headers` moves from 2.1.1 to 2.2.0, so `@Last modified by` now follows content edits only and a header-only rewrite keeps the recorded editor, and `@cldmv/configs` moves from 1.2.0 to 1.2.4, whose shared config no longer forces the author fields. Neither changed any file header here. No runtime source changed and the peer ranges are the same as in v1.2.1 (`@cldmv/slothlet >=3.22.0`, optional `ws >=8.0.0`); it's a drop-in replacement for v1.2.1.
 - [View full v1.2.2 Changelog](https://github.com/CLDMV/slothlet-vine/blob/master/docs/changelog/v1/v1.2.2.md)
 
 ### Recent Releases

docs/changelog/v1/v1.2.2.md

@@ -8,22 +8,27 @@
 
 ## Overview
 
-A single dev-tooling dependency patch. `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test and config files, moves from 2.1.1 to 2.1.4. No runtime source changed: the forwarding core, wire protocol, channel principal, `around`, event forwarding and every transport are exactly as in v1.2.1, and both peer ranges are unchanged (`@cldmv/slothlet >=3.22.0`, optional `ws >=8.0.0`).
+A dev-tooling dependency patch. The tools that maintain the comment headers at the top of the repository's source, test and config files move to their current releases: `@cldmv/fix-headers` from 2.1.1 to 2.2.0, and `@cldmv/configs`, the package that supplies the shared fix-headers configuration, from 1.2.0 to 1.2.4. No runtime source changed: the forwarding core, wire protocol, channel principal, `around`, event forwarding and every transport are exactly as in v1.2.1, and both peer ranges are unchanged (`@cldmv/slothlet >=3.22.0`, optional `ws >=8.0.0`).
 
-The bump was made with a header restamp in mind, but fix-headers 2.1.4 produced no header changes in this repository, so the only files touched are `package.json` and `package-lock.json`.
+The bumps were made with a header restamp in mind, but neither produced any header change in this repository: running `npm run fix:headers` against this release rewrites 0 files, so the only files touched are `package.json` and `package-lock.json`.
 
 ---
 
 ## 🔧 Dependencies
 
-- **`@cldmv/fix-headers` `2.1.1` → `2.1.4`** ([#72](https://github.com/CLDMV/slothlet-vine/pull/72)), dev dependency. The 2.1.x line no longer stamps a header into files that have no usable comment syntax (strict JSON such as `package.json`, and Markdown unless explicitly forced), never walks into `node_modules` or other dependency folders, and processes every repeated `--input` value instead of only the last. It only runs through the `fix:headers` script; nothing in the published package depends on it.
+Both are dev dependencies. The lockfile changes are limited to these two packages and the package's own version.
+
+- **`@cldmv/fix-headers` `^2.1.1` → `^2.2.0`** (resolved 2.1.1 → 2.2.0; [#72](https://github.com/CLDMV/slothlet-vine/pull/72) moved it to 2.1.4 and [#75](https://github.com/CLDMV/slothlet-vine/pull/75) to 2.2.0). The 2.1.4 release no longer stamps a header into files that have no usable comment syntax (strict JSON such as `package.json`, and Markdown unless explicitly forced), never walks into `node_modules` or other dependency folders, and processes every repeated `--input` value instead of only the last. The 2.2.0 release changes what `@Last modified by` means: it now names whoever last edited a file's content, so a run that only rewrites a header (a date format conversion, a corrected `@Project`, new spacing) keeps the recorded editor instead of claiming the file for whoever ran the tool. The 2.1.2 and 2.1.3 releases in between were repository-maintenance releases with no change to the tool. It only runs through the `fix:headers` script; nothing in the published package depends on it.
+- **`@cldmv/configs` `^1.2.0` → `^1.2.4`** ([#75](https://github.com/CLDMV/slothlet-vine/pull/75)). `.configs/fix-headers.json` extends `@cldmv/configs/fix-headers.json`, and from 1.2.4 that shared config sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to `false` (both were `true` in 1.2.0). Together with fix-headers 2.2.0, a `fix:headers` run no longer overwrites `@Author` or `@Last modified by` on every file.
 
 ## 📚 Documentation
 
 - **NEW:** [docs/changelog/v1/v1.2.2.md](./v1.2.2.md): this changelog.
+- README **What's New**: v1.2.2 is the new Latest, and v1.2.1 moves into Recent Releases.
 
 ---
 
 ## Upgrade notes
 
 - No breaking changes, and no runtime code changed. It's a drop-in replacement for v1.2.1.
+- For contributors: fix-headers 2.2.0 decides whether a file's content was edited by comparing the working tree with git `HEAD`, so run `npm run fix:headers` before committing, not after.