v1.9.0-jf.15.29

WHAT

Pilot fork release for trusted peer public-key backfill.

WHY

Older trusted-peer records could carry an empty public key after restarts. Entmoot route checks then saw peers as trusted in process state but unusable for encrypted routing.

RESULTS

• Local go test ./... passed via the pre-push hook.
• make release produced linux/darwin amd64/arm64 archives and checksums.

CHANGES

• Backfills missing trusted peer public keys from known identity sources.
• Documents the release in CHANGELOG.md.

NEXT STEPS

Install on peers before Entmoot runtime route verification.

v1.9.0-jf.15.28

Pilot fork release v1.9.0-jf.15.28.\n\nIncludes relay TURN routing recovery fixes for strict outbound TURN paths, rendezvous endpoint refresh behavior, async relay TURN resolver invalidation, and live-socket discovery buffering.

v1.9.0-jf.15.27

Full Changelog: v1.9.0-jf.15.26...v1.9.0-jf.15.27

v1.9.0-jf.15.26

Full Changelog: v1.9.0-jf.15.25...v1.9.0-jf.15.26

v1.9.0-jf.15.25

Full Changelog: v1.9.0-jf.15.24...v1.9.0-jf.15.25

v1.9.0-jf.15.24

Release v1.9.0-jf.15.24 of the jerryfane Pilot fork.\n\nAdds reliable pending-handshake IPC notifications for Entmoot onboarding and documents the prior identity lookup IPC release.

v1.9.0-jf.15.23

Full Changelog: v1.9.0-jf.15.22...v1.9.0-jf.15.23

v1.9.0-jf.15.22

Full Changelog: v1.9.0-jf.15.20...v1.9.0-jf.15.22

v1.9.0-jf.15.20

Fix rendezvous publish retry after 429 rate limits and relay-marked peer TURN route selection. See CHANGELOG.md for details.

v1.9.0-jf.15.19

Pilot stream lifecycle fix: passive stream accepts now wait for final ACK before IPC exposure, and stale passive SYN_RECV handshakes are reaped. This targets Entmoot :1004 reconcile EOF / connection-not-found / zero-byte accepted stream failures.