Prepare release 1.7.0

[jgfoster]

Prepares release 1.7.0: npm version 1.7.0 bumps package.json and package-lock.json, and [Unreleased] is promoted to ## [1.7.0] - 2026-10-15 with fresh link definitions. If the release goes out on a later day, change the date before merging.

Merge #138 first. This changelog describes its Grail, and the CI run on this PR's merge commit is where the release's packages come from.

Along the way it tidies the changelog:

• Moves Record which editor GemDB runs in on every telemetry event #109's entry ("Usage data now records which editor GemDB runs in") out of the released 1.6.0 section. Record which editor GemDB runs in on every telemetry event #109 branched before the 1.6.0 promotion and merged a day after the release, so git placed its entry inside ## [1.6.0]. Neither the v1.6.0 tag nor its GitHub Release notes carry it. It now sits under [Unreleased] → Changed.
• Merges three ### Fixed headings into one. Run one bring-up at a time within a window #117, Start the stone and session listener once, across processes #118 and Keep topaz's own output off the terminal during a gemdb run #132 each added their own.
• Adds two entries:
  • Apply RemoveIPC=no at once, and report it only once it is in effect #121: on Linux, Survives logout takes effect at once instead of at the next restart (Fixed).
  • Bump the Grail pin to main as of 2026-10-15, and build unicodedata at install #138: "A newer Python runtime", for the Grail pin bump (Changed). It describes Bump the Grail pin to main as of 2026-10-15, and build unicodedata at install #138, so merge Bump the Grail pin to main as of 2026-10-15, and build unicodedata at install #138 first.
• Rewraps [Unreleased] at 100 columns. Only the line breaks change, not the wording.

Swept and left out:

• Drop the claim that gemdb file.py leaves the script's directory off sys.path #129 is a docs correction.
• include analytics pixel from scarf #130 adds a Scarf analytics pixel to the README. It's left out pending a decision, discussed with the maintainer.

npm run release:notes 1.7.0 prints the section cleanly, Prettier passes, and no line in the new section exceeds 100 columns.

After merge: wait for CI to go green on the merge commit, then dispatch Actions → Release with 1.7.0, dry-run first.

🤖 Generated with Claude Code