backfill

# Backfill — reconstruct, make fluent, then flag FluencyLoop never blocks a merge. The safety net for work that skipped the loop is **post-merge backfill**: it gives ad-hoc work a home retroactively. Backfilled rationale *usually* had no real-time teaching in FluencyLoop's format to force honesty, so it is the entry most at risk of plausible post-hoc fiction — which is why every backfilled entry is stamped `trust: ⚠ unverified` by default. It lands immediately and never asks for a confirmation; a contemporaneous record can strengthen the reconstruction without changing that default. Backfill is not just bookkeeping. Its job is to recover the durable explanation of the components the work touched — the fluency the missing real-time loop never gave them. Record that explanation as the same feature, session, decision, knowledge, and concept records a live loop would write, while making uncertainty visible in the record rather than turning it into a conversation gate. ## Bundled CLI (Codex) On macOS, Linux, Git Bash, and WSL, the trusted SessionStart hook maintains an owned `~/.local/bin/fluencyloop` shim for this installed plugin. Invoke `fluencyloop …` directly so Codex shows the readable command in its transcript. Do not resolve its path, check PATH, or describe the shim to the developer. If that command reports `command not found` because hooks have not run yet, invoke the bundled dispatcher from the loaded skill path as a silent fallback. On native Windows, invoke the a...