[efiten]

Release notes for v3.15.0: docs/release-notes/v3.15.0.md and the CHANGELOG.md entry. The release workflow uses the notes file as the GitHub release body.

What is in it

• 77 commits since v3.14.0 (76 merged pull requests plus this one): 27 fix, 23 perf, 19 feat, 3 test, 2 ci, 2 docs, 1 chore. Nineteen feats, so minor.
• "Read this before upgrading" first. It covers:
  • the liveness change (fix(liveness): count only evidence that can be the node alone (#2260) #2261, feat(notify): adaptive offline threshold and certain node analytics (#2260) #2262);
  • the users.db v6 migration and what it means for a rollback (feat(users): companion linking store (schema v6, device sessions, link challenges) #2174);
  • the backfill at every ingestor start (feat(#2107): backfill unresolved channel/scope rows when the key set grows #2133) and the 24 h planner-statistics refresh (perf(ingestor): refresh planner statistics 24h after the last refresh, not after every start #2158);
  • the caches that trade freshness for latency (perf(server): share /api/nodes responses for identical queries for 15 s #2165, perf(neighbors): rebuild the neighbor graph only in the background (#2221) #2222, fix(server): no SQL while holding PacketStore.mu #2147, perf(server): battery history via the primary key, cached /api/perf row counts #2156);
  • changes in hop names and region placement (fix(hops): narrow only the directly heard hop to the observer region (#2098) #2188, fix(nodes): place nodes in regions by zero-hop home regions (#1879) #2190, fix(nodes): read the transport-direct path byte at offset 5 (#2225) #2234, 1-Byte Hop Path Inference for Packet and Map Analysis #2245, fix(observers): an observer's own transmissions are not receptions (#667) #2220);
  • the role thresholds on favorites (fix(health): judge favorites and home status cards by the node's role #2215);
  • the geo-filter save on a single-file mount (fix(config): write the geo filter through a symlinked config.json #2137);
  • the /api/stats polling in hidden tabs (perf(frontend): throttle nav stats to one refresh per 15 s, none in hidden tabs #2162).
• Features, fixes, performance, then tests/CI/docs.
• 29 issues closed, taken from each pull request's closingIssuesReferences.
• Contributors: pull request authors and issue reporters with counts. The commit co-author trailers only name the pull request's own author or tooling.

How it was checked

• I read every pull request body. Every number in the notes comes from a pull request body.
• I checked the config keys and defaults against config.example.json on 2bb000f2.
• I checked the UNASKED and opt-in claims for fix(docker): run the Go services as an unprivileged user #2125, feat(#2107): backfill unresolved channel/scope rows when the key set grows #2133, fix(docker): read .env last, and restore RUN_AS_UID/GID from positional parameters #2235 and feat(nodes): name and show repeaters known only from the name they reported (#2238) #2239 against the source.
• For the other pull requests I relied on their bodies and did not open the diffs.

Not covered

• The uncertain count is a single count on one staging instance on the day of the change (1,682 repeaters and rooms). It is not a before/after comparison.
• feat(#2107): backfill unresolved channel/scope rows when the key set grows #2133 gives no measured cost for its backfill on a large database, and the notes say so.

After merge

Tag v3.15.0 on the merge commit once its :edge image exists. Then check in the registry that v3.15.0, v3.15, v3 and latest share one digest, and that the release has the notes as its body and both corescope-decrypt binaries.