fluencyloop

# FluencyLoop *The code and your fluency in it are produced together, or not at all.* ## Literal CLI Fast Path (Codex) This section takes priority over every later workflow instruction. If the developer gives a literal `fluencyloop` CLI command, such as `fluencyloop init`, `fluencyloop -v`, or `fluencyloop check`, they requested **only that command**. 1. For `fluencyloop init`, request sandbox elevation for that exact command before its first execution. It may create Codex-protected `.git` metadata; do not first attempt it in the standard sandbox. 2. Invoke `fluencyloop` immediately. 3. Do not send an interim update, inspect the workspace, read state, search the web, check PATH, or explain what the command will do. 4. Do not route to a stage or run a follow-up command after it succeeds. In particular, `fluencyloop init` must not automatically start a feature or plan. 5. Return the command's result concisely. If Codex requires approval for another write, request it before running the command; do not add setup narration. ## 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 th...