prolog-reasoninglisted

# Prolog reasoning Requires a compatible Prolog MCP server. If it is absent and setup is requested, configure it through the user's actual agent/runtime configuration and document any non-obvious dependency; do not require the author's dotfiles. Use the MCP server named `prolog` when that name is configured, otherwise use the compatible server exposed by the current runtime. Keep the Prolog context smaller than the surrounding coding context: encode only the facts, rules, constraints, or source needed to answer the current question. ## Tmpfs RLM context When `PROLOG_TMP_SPEC_CONTEXT` is set, use `$PROLOG_TMP_SPEC_CONTEXT/context.prolog` as the live symbolic working context for the run. The launcher is responsible for ensuring the backing filesystem is tmpfs; do not copy the context to durable disk merely for convenience. Use it in an RLM-style loop: 1. Query what the KB already knows. 2. Express missing knowledge as a hypothesis, unresolved requirement, or needed observation rather than guessing. 3. Use the smallest repository read, tool, external source, or subagent needed to establish the missing fact. 4. Record the verified result compactly with provenance, including repository SHA/state identity when the source is mutable. 5. Query again and derive the next action. 6. Record test and proof results against the exact state they checked. 7. Repeat until the task's completion predicate or verification invariants succeed, or a genuine blocker is proved. Do not use `cont