v1.4.5

Full Changelog: v1.4.4...v1.4.5

v1.4.4

Full Changelog: v1.4.3...v1.4.4

v1.4.3

Full Changelog: v1.4.2...v1.4.3

v1.4.2

Full Changelog: v1.4.0...v1.4.2

v1.4.0

Full Changelog: v1.3.1...v1.4.0

v1.3.1

Full Changelog: v1.3.0...v1.3.1

v1.3.0

Full Changelog: v1.2.9...v1.3.0

v1.2.9

Full Changelog: v1.2.8...v1.2.9

v1.2.8

Full Changelog: v1.2.7...v1.2.8

v1.2.7

What's Fixed

Prefix bundle not delivered to LLM after successful Generate

Even after the Generate button succeeded (fixed in v1.2.5), the LLM continued to see the fallback text:

The prefix currently contains nothing yet … "Bundle not yet compiled — run Settings → Prefix Cache → Generate"

Root cause: Two project_id fallback strings were mismatched.

• regenerate_prefix writes the bundle with project_id = "default" (the fallback used everywhere in the WebUI layer when caller.project_id is None).
• ThreadBackedLoopContextPort::load_loop_context (Kohai) and the Sempai path in loop_driver_host were using "_default" as the fallback when run_context.scope.project_id is None.

The WHERE project_id = $4 clause in get_system_bundle never matched, so the stored bundle was never returned — only the minimal fallback string.

Fix: Changed both .unwrap_or("_default") occurrences to .unwrap_or("default") in:

• crates/brassclaw_loop_support/src/lib.rs (Kohai context load)
• crates/brassclaw_reborn/src/loop_driver_host.rs (Sempai prompt build)

Full Changelog: v1.2.6...v1.2.7