v1.0.8 - Peer Federation Fixes & Engine Observability

v1.0.8 — Peer Federation Fixes & Engine Observability

🔗 Peer Federation (Now actually works)

• Fixed encrypted peering: Configuring a peer secret no longer breaks local MCP tool calls. Loopback connections (127.0.0.1/::1) now bypass encryption enforcement — only remote peers go through the encrypt/decrypt path.
• Auto-bind 0.0.0.0: The engine automatically listens on all interfaces when peers.enabled = true, so remote peers can actually connect. Previously it was hardcoded to 127.0.0.1.
• New config option server.listen_address: Explicit override for the bind address if you need a specific interface.
• Prevent search loops: Incoming peer searches no longer fan out back to other peers, preventing infinite A→B→A cycles.
• Dev helper scripts/search-via-peers.py: Sends encrypted searches directly to peers for testing connectivity and result quality without mixing in local results.

🔍 Search Fix

• FTS5 column name collision: Search terms were being misinterpreted as FTS5 column references. All tokens are now properly quoted in the MATCH query.

🪵 Engine Observability

• Timestamped logging: All engine output now uses [YYYY-MM-DD HH:MM:SS] [kiro-ception] format.
• Default log file: Engine logs to ~/.cache/kiro-ception/engine.log by default.
• Remote request logging: Incoming peer requests are logged with client IP and content type.
• Crash handler: Last-resort exception handler writes tracebacks to the log file even on unexpected crashes.

🧪 Test Fix

• Fixed a Hypothesis property test false positive where generated stderr content coincidentally matched a file path in the summary.

Upgrade

No config changes required. Existing peer configurations will start working immediately after upgrade — just ensure both machines are on v1.0.8.

# If installed via uv tool
uv tool upgrade kiro-ception
# if cloned
git pull && uv sync  # then restart kiro to pick up the latest, or remove/reinstall the power