FABULA v0.218.0 — the example config loads
A fresh install could not start on the config this project ships as its own example. Both halves are repaired — for new installs and for every config already copied.
0.218.0 — 2026-08-12
-
A fresh install no longer dies on a config this project itself handed out. The shipped example carried four keys the strict loader refuses: three pseudo-comments (
_comment_*— prose written as KEYS in a file that is actually parsed as JSONC, where real//comments are legal) andenhance— a genuine setting of the Enhance-prompt button, which its route reads from the same file directly, bypassing the schema. One reader required the key, the other forbade it — and setup copied that example to every new user. Machines with an older config never crashed, so the defect lived unseen until a second machine. -
Fixed for everyone, not only for new installs:
enhanceis declared in the schema (the feature is real — deleting it would treat the symptom), the example carries real comments, and the loader TOLERATES top-level pseudo-comment keys with a log warning — because setup never overwrites an existing config, so anyone who copied the example in a bad week would carry those keys forever. Below top level an underscore is data (enhance._defaultis a live contract) and is not stripped. The example now passes the REAL schema in tests — not an allowlist of keys, which would have to be kept in step by hand, the very failure that produced this defect.
Also in this push: two hand-made rotation-log copies are removed from the tree, the ignore rule now covers rotated logs (*.log.*), and the public-hygiene gate refuses any tracked file containing the home directory of the machine it runs on.