Merge upstream dev into PR branch

# Conflicts:
#	docs/install-for-codex.md
#	hooks/loop-codex-stop-hook.sh
#	scripts/bitlesson-select.sh
#	scripts/install-codex-hooks.sh
#	tests/test-bitlesson-select-routing.sh
#	tests/test-codex-hook-install.sh
#	tests/test-disable-nested-codex-hooks.sh

Author: Inference1

.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
       "name": "humanize",
       "source": "./",
       "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-      "version": "1.16.0"
+      "version": "1.17.0"
     }
   ]
 }

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "humanize",
   "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-  "version": "1.16.0",
+  "version": "1.17.0",
   "author": {
     "name": "PolyArch"
   },

.claude/CLAUDE.md

@@ -7,3 +7,5 @@ This is a Claude Code plugin that provides iterative development with Codex revi
 - Version number must be in format of `X.Y.Z` where X/Y/Z is numeric number. Version MUST NOT include anything other than `X.Y.Z`. For example, a good version is `9.732.42`; Bad version examples (MUST NOT USE): `3.22.7-alpha` (extra "-alpha" string), `9.77.2 (2026-01-07)` (useless date/timestamp).
 - The plan template in `commands/gen-plan.md` (Phase 5 Plan Structure section) and `prompt-template/plan/gen-plan-template.md` are intentionally kept in sync. When modifying either file, ensure both are updated to maintain consistency.
 - Conversely, changes to `prompt-template/plan/gen-plan-template.md` must also be reflected in the Plan Structure section of `commands/gen-plan.md`.
+- The directions.json schema v1 is defined in two places that must stay in sync: the jq validation expression in `scripts/validate-directions-json.sh` and the schema documentation in `commands/gen-idea.md` (Step 4.5). When adding, removing, or renaming a field in either place, update the other.
+- Worker constraints (hard caps, isolation rules, no-push rule, sentinel format) are documented in four places that must stay in sync: `commands/explore-idea.md` (coordinator phases), `prompt-template/explore/worker-prompt.md` (worker instructions), `scripts/validate-explore-idea-io.sh` (cap enforcement), and `docs/usage.md` (user-facing option docs). Any change to a cap value or constraint must be reflected in all four.

.gitignore

@@ -4,6 +4,10 @@ temp
 # Local Claude client settings
 /.claude/settings.json
 /.claude/scheduled_tasks.lock
+/.claude/worktrees/
+
+# Local Codex CLI marker (empty file occasionally left behind in worktree)
+/.codex
 
 # Humanize state directories (runtime-generated, project-local)
 .humanize/

README.md

@@ -1,6 +1,6 @@
 # Humanize
 
-**Current Version: 1.16.0**
+**Current Version: 1.17.0**
 
 > Derived from the [GAAC (GitHub-as-a-Context)](https://github.com/SihaoLiu/gaac) project.
 
@@ -15,6 +15,7 @@ A Claude Code plugin that provides iterative development with independent AI rev
 - **Iteration over Perfection** -- Instead of expecting perfect output in one shot, Humanize leverages continuous feedback loops where issues are caught early and refined incrementally.
 - **One Build + One Review** -- Claude implements, Codex independently reviews. No blind spots.
 - **Ralph Loop with Swarm Mode** -- Iterative refinement continues until all acceptance criteria are met. Optionally parallelize with Agent Teams.
+- **Capability Anchors** -- Generated plans include a feature/capability map, and RLCR rounds keep Claude and Codex anchored to the relevant capability node.
 - **Begin with the End in Mind** -- Before the loop starts, Humanize verifies that *you* understand the plan you are about to execute. The human must remain the architect. ([Details](docs/usage.md#begin-with-the-end-in-mind))
 
 ## How It Works
@@ -45,37 +46,53 @@ Requires [codex CLI](https://github.com/openai/codex) for review. See the full [
    ```bash
    /humanize:gen-idea "add undo/redo to the editor"
    ```
-   Output goes to `.humanize/ideas/<slug>-<timestamp>.md` by default. Pass a `.md` path to expand existing rough notes. `--n` controls how many parallel directions explore the idea (default 6).
+   Output goes to `.humanize/ideas/<slug>-<timestamp>.md` and a companion `directions.json` artifact. Pass a `.md` path to expand existing rough notes. `--n` controls how many parallel directions explore the idea (default 6).
 
-2. **Generate a plan** from your draft:
+2. **Explore directions as parallel prototypes** (optional — skip if you want to go straight to planning):
    ```bash
-   /humanize:gen-plan --input draft.md --output docs/plan.md
+   /humanize:explore-idea .humanize/ideas/<slug>-<timestamp>.directions.json
    ```
+   Dispatches bounded parallel prototype workers (one per direction), each running in an isolated git worktree. After all workers complete, writes `.humanize/explore/<run-id>/explore-report.md` for audit/ranking details and `.humanize/explore/<run-id>/final-idea.md` as the plan-ready synthesis. Worker worktrees are optional prototype fast paths; the default follow-up is to generate a clean plan from `final-idea.md`.
 
-3. **Refine an annotated plan** before implementation when reviewers add comments (`CMT:` ... `ENDCMT`, `<cmt>` ... `</cmt>`, or `<comment>` ... `</comment>`):
+3. **Generate a plan** from your draft or explored final idea:
+   ```bash
+   /humanize:gen-plan --input .humanize/explore/<run-id>/final-idea.md --output docs/plan.md
+   ```
+   Add `--coach` to run mandatory short-answer stage quizzes after each planning stage. Normal plan decision questions stay separate; quiz mismatches are treated as design drift, AI design correction, or background gaps before the agent expands the next planning layer.
+   Generated plans include a `Feature Map / Capability Map` before the task breakdown so each task carries its global capability context.
+
+4. **Refine an annotated plan** before implementation when reviewers add comments (`CMT:` ... `ENDCMT`, `<cmt>` ... `</cmt>`, or `<comment>` ... `</comment>`):
    ```bash
    /humanize:refine-plan --input docs/plan.md
    ```
 
-4. **Run the loop**:
+5. **Run the loop**:
    ```bash
    /humanize:start-rlcr-loop docs/plan.md
    ```
+   When the plan has a capability map, RLCR records a `Capability Anchor` in each round contract and Goal Tracker active task so Claude coding and Codex review stay aligned with the map.
 
-5. **Consult Gemini** for deep web research (requires Gemini CLI):
+6. **Consult Gemini** for deep web research (requires Gemini CLI):
    ```bash
    /humanize:ask-gemini What are the latest best practices for X?
    ```
 
-6. **Monitor progress (in another terminal, not inside Claude Code)**:
+7. **Monitor progress (in another terminal, not inside Claude Code)**:
    ```bash
    source <path/to/humanize>/scripts/humanize.sh # Or just add it into your .bashec or .zshrc
    humanize monitor rlcr       # RLCR loop
    humanize monitor skill      # All skill invocations (codex + gemini)
    humanize monitor codex      # Codex invocations only
    humanize monitor gemini     # Gemini invocations only
+   humanize monitor web        # Browser dashboard for the current project
    ```
 
+   The `humanize monitor web` subcommand launches a per-project browser dashboard
+   that layers on top of the same data sources the terminal monitors read. It runs
+   in the foreground by default; pass `--daemon` for the background tmux launcher
+   and `--host` / `--port` / `--auth-token` to configure remote access. See the
+   upgrade note: `/humanize:viz` has been removed in favour of `humanize monitor web`.
+
 ## Monitor Dashboard
 
 <p align="center">