docs: update the v1.0.10 release notes

README.md

@@ -8,7 +8,7 @@ Use it as a local utility or run it on a remote VM to expose WoL via an HTTP API
 
 ### Latest: v1.0.10 (October 2026)
 
-- **Dev-tooling dependency bump ([#35](https://github.com/CLDMV/wol-proxy/pull/35))** — `@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. The Express server and `postinstall.js` are unchanged; it's a drop-in replacement for the previous version.
+- **Dev-tooling dependency bumps ([#35](https://github.com/CLDMV/wol-proxy/pull/35), [#38](https://github.com/CLDMV/wol-proxy/pull/38), [#40](https://github.com/CLDMV/wol-proxy/pull/40))** — `@cldmv/fix-headers` moves to 2.2.0, `@cldmv/configs` to 1.2.4 and `@cldmv/vitest-runner` to 1.5.3. No file headers changed and no runtime code changed: the Express server and `postinstall.js` are as in the previous version, so it's a drop-in replacement.
 - [View full v1.0.10 Changelog](https://github.com/CLDMV/wol-proxy/blob/master/docs/changelog/v1/v1.0.10.md)
 
 ### Recent Releases

docs/changelog/v1/v1.0.10.md

@@ -8,16 +8,19 @@
 
 ## Overview
 
-A single dev-tooling dependency patch. `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test, config and workflow files, moves from 2.1.1 to 2.1.4. No runtime code changed: `index.js`, `postinstall.js` and `wol-proxy.service` are exactly as in v1.0.9, and the runtime dependency ranges (`express` ^5.1.0, `wake_on_lan` ^1.0.0) and their lockfile entries are unchanged.
+A dev-tooling dependency release. Three development dependencies move forward: `@cldmv/fix-headers`, which maintains the comment headers at the top of the repository's source, test, config and workflow files (2.1.1 to 2.2.0), `@cldmv/configs`, the shared lint, format and header configuration (1.2.0 to 1.2.4), and `@cldmv/vitest-runner`, the test runner (1.2.0 to 1.5.3).
 
-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`.
+No runtime code changed: `index.js`, `postinstall.js` and `wol-proxy.service` are exactly as in v1.0.9, and the runtime dependency ranges (`express` `^5.1.0`, `wake_on_lan` `^1.0.0`) and their lockfile entries are unchanged. The only other lockfile movement is `chalk` 5.6.2 to 6.0.1, a dev-only dependency of the test runner. No file headers were restamped by either fix-headers step, so the files touched are `package.json`, `package-lock.json` and the documentation.
 
 ---
 
 ## 🔧 Dependencies
 
-- **`@cldmv/fix-headers` `2.1.1` → `2.1.4`** ([#35](https://github.com/CLDMV/wol-proxy/pull/35)), 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 that ships depends on it.
-- **`@cldmv/vitest-runner` `1.2.0` → `1.5.3`** ([#38](https://github.com/CLDMV/wol-proxy/pull/38)), dev dependency (the test runner). This restores the bump from [#30](https://github.com/CLDMV/wol-proxy/pull/30), which merged into `next` just after the previous release and was dropped by the post-release reset of `next` ([CLDMV/.github#360](https://github.com/CLDMV/.github/issues/360)); it is reinstalled at the latest version instead of the original 1.5.1. Test tooling only; nothing that ships depends on it.
+All dev-only; nothing that ships depends on them.
+
+- **`@cldmv/fix-headers` `^2.1.1` → `^2.2.0`** (locked 2.1.1 to 2.2.0), in two steps: 2.1.4 ([#35](https://github.com/CLDMV/wol-proxy/pull/35)) and 2.2.0 ([#40](https://github.com/CLDMV/wol-proxy/pull/40)). 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. From 2.2.0 the `@Last modified by` tag follows content edits only, so a header-only rewrite keeps the recorded editor. It only runs through the `fix:headers` script. Neither step changed any header in this repository.
+- **`@cldmv/configs` `^1.2.0` → `^1.2.4`** (locked 1.2.0 to 1.2.4) ([#40](https://github.com/CLDMV/wol-proxy/pull/40)). Version 1.2.4 sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to `false`, so `@Author` is never rewritten and `@Last modified by` changes only on real content edits. Re-running `fix:headers` under the new config restamped no files.
+- **`@cldmv/vitest-runner` `^1.2.0` → `^1.5.3`** (locked 1.2.0 to 1.5.3) ([#38](https://github.com/CLDMV/wol-proxy/pull/38)). This restores the bump from [#30](https://github.com/CLDMV/wol-proxy/pull/30), which merged into `next` just after the previous release and was dropped by the post-release reset of `next` ([CLDMV/.github#360](https://github.com/CLDMV/.github/issues/360)); it is reinstalled at the latest version instead of the original 1.5.1. The runner's own `chalk` dependency moves from `^5.4.1` to `^6.0.1` (locked 5.6.2 to 6.0.1), which requires Node 22 or newer; the CI matrix already starts at 22.12.0.
 
 ## 📚 Documentation