hoo-orchestratorlisted

# Head of Organic - orchestrator 1. Locate the brain repo: try `core.registry.get_active()` first (the active site's `brain` path). If the registry is empty or unavailable (cloud runtimes may lack local registry access), fall back to the routine's own configured site-profile path, or ask the user (a repo has site-profile.yaml at root). Read site-profile.yaml fully. 1a. Run `core.contracts.check_schema(brain_path)` before fanning out to any specialist. If not compatible, relay the action string and stop. 2. Decide which specialists the request needs (default full sweep: all eight). Launch them as parallel agents, each given the profile path + target URLs. 3. Synthesize results. Deduplicate findings. Rank by impact x confidence. 3b. Decision check, BEFORE any `create_item` call. For every brief topic and every on-page fix, search the brain's decision memory: `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c "..."` snippet importing `core.decisions` - `search(<brain>, [<page path>, <topic or keyword>])`. It returns prior decisions newest first with `date`, `choice`, `scope`, `item`, and the `rationale`. A hit whose `choice` is `rejected` means a human already refused that work. Exactly two paths are allowed, never a third: - SKIP it, and say so in step 6's summary: name the topic, the decision date, and the recorded reason. - Or CREATE it with a line in the item body reading "previously rejected on <date> because