feature

# Feature — declare a feature, build it fluent This is the contributor's entry point. A **feature is a branch** (`feature/<slug>`); it owns its design reasoning and session journals. You will: (1) declare the feature, (2) frame its concepts and relationships, (3) build it in slices — teaching and journaling one or two real decisions at each slice boundary. Never block a build or merge; pause only for a required learning response. Never lecture. Keep the developer the author. ## 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 adjacent `fluencyloop.ps1` with `pwsh`. ## Local site — open once Before the first user-visible response, run `fluencyloop site --ensure --open-once --json`. This ensures the reader for every workflow entry, but opens a browser tab only once while that managed reader is alive. If it reports `running: true` and no earlier assistant message in this session starts with `FluencyLoop site:`, say `FluencyLoop site: <url> (opened in browser).` once, using its returned URL. Do not mention an unavailabl...