From 05e977814f8c73ca66d33ff4ecf95bb914603b87 Mon Sep 17 00:00:00 2001
From: cndgrr <59120057+cndgrr@users.noreply.github.com>
Date: Tue, 4 Aug 2026 21:40:41 +0000
Subject: [PATCH] README: point the two new anchors at the lines that carry the
 claim

version_is_dev's range started one line in, past the signature comment
that states the -dev-only rule; and the npm range stopped at L112,
before the npm pkg set / npm install --package-lock-only lines it was
cited for. L68-L76 and L114-L115.
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 2560c51..2664ba4 100644
--- a/README.md
+++ b/README.md
@@ -514,7 +514,7 @@ in this catalog whose remedy is a manual bump, not a re-run.
 Two senses of *bare* meet here, and the gap between them is the **rc release
 path** — the one door an operator actually walks through. decide calls a
 version bare when it is not `-dev`
-([version_is_dev](lib/version.sh#L69-L76) matches that suffix and nothing
+([version_is_dev](lib/version.sh#L68-L76) matches that suffix and nothing
 else), so row 6 admits a transition to `1.2.3-rc1`, and a labeled rc ceremony
 is designed to ship ([lib/decide.sh](lib/decide.sh#L108-L110)).
 `version_next_dev` means `^[0-9]+\.[0-9]+\.[0-9]+$`. An rc sits between the
@@ -532,7 +532,7 @@ rows 1–2 send `-dev` to a no-op, and the tag door never bumps.
 
 [L106](lib/version.sh#L106): the package-json backend needs npm to write —
 `npm pkg set version=` plus a lockfile-only `npm install`
-([L102–L112](lib/version.sh#L102-L112)), never `npm version`, which would tag
+([L114–L115](lib/version.sh#L114-L115)), never `npm version`, which would tag
 — and the runner has none. The read path fails the
 same way one step earlier (`node is required…`, above), so a run reaching
 *this* message got past the read — set up node/npm in the caller.