chore(release): v0.1.25 — Now horizon (N1, N2, N3, N4) + P0 wave

[NagyVikt]

Summary

Cuts v0.1.25. Docs + version-bump only. No code changes. No npm publish.

Bumps package.json and package-lock.json from 0.1.24 to 0.1.25 and extends releases/v0.1.25.md to cover every theme that landed on main since v0.1.24.

Themes shipped in 0.1.25

Theme	PR	Title
P0 wave	#26	docs(future) + feat: 18k-line improvement protocol + P0 wave implementation
N4 — lazy path resolvers	#27	refactor(paths): replace eager constants with lazy getters
N3 — error taxonomy + --json	#28	feat(errors): AuthmuxError taxonomy + --json on 5 core commands
N1 — durability	#29	feat(durability): atomic writes + registry lock
N2 — account-service split	#30	refactor(accounts): split account-service.ts into 12 focused modules

P0 wave content from #26 covers: secure-fs perms (0600/0700 via secureWriteFile), init-hook update prompt flipped to [y/N] default-no, kiro switch ENOENT fix, CI test matrix (Ubuntu/macOS/Windows × Node 18/20/22), and registry proxy-source round-trip fix.

Release-notes shape

Follows the canonical 7-section order from docs/future/17-ROADMAP.md §"Release-notes shape": Added → Changed → Fixed → Deprecated → Removed → Security → Migration. The prior Durability section from #29's partial notes is preserved under a new ## Theme deep-dives appendix so the canonical 7-section shape stays intact.

• Deprecated lists the six bare paths.ts constants (codexDir, accountsDir, authPath, currentNamePath, registryPath, sessionMapPath) with removal scheduled for v0.2.0.
• Removed is - None.
• Security documents 0600/0700 perms, atomic mode-before-rename, and the default-no update prompt.

Verification

npm run build                                           # clean
npm test                                                # 129/129 pass
node -e "console.log(require('./package.json').version)"      # 0.1.25
node -e "console.log(require('./package-lock.json').version)" # 0.1.25

Not in this PR

• npm publish. The previous publish attempt failed with tsc: not found. Publishing is a separate maintainer decision.
• Code changes. This PR is docs + version only.

Test plan

• npm run build clean
• npm test 129/129 pass
• package.json version reads 0.1.25
• package-lock.json top-level + packages[""] version both 0.1.25
• releases/v0.1.25.md has all 7 canonical sections in order
• CI matrix green (Ubuntu/macOS/Windows × Node 18/20/22)
• Maintainer decides whether to npm publish separately