Chalie Dev Log: Core Reliability & Workflow Overhaul

The trait correction logic now allows for overwriting stale values when the confidence is greater than or equal to 80% of the old confidence, fixing issues where corrections were silently discarded.

Chat history reading has been migrated entirely to SQLite using get_paginated_history_durable(), replacing reliance on the volatile in-memory MemoryStore. Silent debug catches for these failures have been promoted to visible errors.

Digest worker responsibilities were heavily refactored, extracting singletons and post-exchange hooks into dedicated modules, and consolidating pipeline logic into helper functions.

The build log process is now fully owned by n8n, which handles the entire pipeline from commit reads to MDX/state writes, reducing GitHub Actions to a simple trigger.

Webhook security was hardened by switching to opaque URL tokens for authentication, eliminating dependency on custom headers stripped by proxies.

The release announcement workflow was modernized by moving LLM calls and delivery logic into n8n, replacing external dependencies like Zapier for local inference.

The system now uses hash-based state files in the build log to reliably track processed commits, preventing reprocessing of the same date window repeatedly.

Compaction and pipeline health checks were improved by aligning thresholds directly with actual token usage rather than fixed entry counts or ceilings.

• Lower confidence threshold allows trait corrections to overwrite stale values.

• Chat history now reads exclusively from SQLite via SQL-level pagination.

• Digest worker singletons and hooks were extracted into dedicated files.

• Build log generation pipeline is centralized and managed by n8n.

• Webhook authentication switched to opaque URL tokens for better reliability.

• Build log state tracking now uses committed hash maps instead of simple commit counts.