ForgeBook v1.0.3

What's new in 1.0.3

Structured request-trace logging. Every stage of a ForgeBook request now emits one INFO-level line keyed by the invoking player's UUID, so a single request can be reconstructed end-to-end by grepping the server log for that UUID.

No user message content is ever logged — only metadata, lengths, tool names, outcomes, and latencies (SAFE-04 preserved).

Lifecycle coverage

• Chat UI — chat request / chat denied / chat reply / chat error
• /forgebook ask — ask request / ask denied / ask reply / ask error
• /forgebook item —
  • item request (modId, itemId, modURL, held-context hash)
  • rag denied / rag no_doc_url / rag resolved_via_web_search / rag docs_cache_hit
  • rag fetch uuid=… source=cf_api|safe_http … + rag fetch_ok / rag fetch_miss
  • rag reply (tokens + latency) / rag error
• Shared downstream —
  • dispatch start / dispatch reply / dispatch error (tokens + latency)
  • agent iter=N/M outcome=FinalReply|ToolUses|ProviderError tools=[…] + per-tool tool <name> ok
  • anthropic request / anthropic response status=… (retries logged) / anthropic io_error
  • safehttp fetch start / safehttp redirect / safehttp fetch ok (status, bytes, content-type, latency)

Fix

Null-guarded senderUuid in ChatRequestHandler so the authorizer path still logs cleanly when the sender is absent.

Compatibility

• Minecraft 1.20.1 / Forge 47.4.18
• No config changes. No breaking changes.

Full changelog: v1.0.2...v1.0.3