diff --git a/.doc-review-cursor b/.doc-review-cursor
new file mode 100644
index 00000000..2914b545
--- /dev/null
+++ b/.doc-review-cursor
@@ -0,0 +1 @@
+6a72faf83b3aeb35ee44da51898fe8cbce6f5002
diff --git a/doc/PRODUCT.md b/doc/PRODUCT.md
index f835889c..c4e8df23 100644
--- a/doc/PRODUCT.md
+++ b/doc/PRODUCT.md
@@ -54,7 +54,7 @@ I am researching the Facebook ads Granola uses (current task)
 
 Tasks have parentage. Every task exists in service of a parent task, all the way up to the company goal. This is what keeps autonomous agents aligned — they can always answer "why am I doing this?"
 
-More detailed task structure TBD.
+Tasks carry statuses (backlog, todo, in_progress, in_review, done, blocked, cancelled), priorities, project and goal associations, billing codes for cross-team cost attribution, and execution workspace context. See [SPEC.md](./SPEC.md) for the full task model.
 
 ## Principles
 
diff --git a/doc/SPEC.md b/doc/SPEC.md
index 6a7039ca..2522ef13 100644
--- a/doc/SPEC.md
+++ b/doc/SPEC.md
@@ -196,6 +196,7 @@ Agent configuration includes an **adapter** that defines how Paperclip invokes t
 | `codex_local` | Local Codex process | Codex CLI heartbeat worker |
 | `opencode_local` | Local OpenCode process | OpenCode heartbeat worker |
 | `pi_local` | Local Pi process | Pi CLI heartbeat worker |
+| `gemini_local` | Local Gemini process | Gemini CLI heartbeat worker |
 | `cursor` | Cursor API/CLI bridge | Cursor-integrated heartbeat worker |
 | `openclaw_gateway` | OpenClaw gateway API | Managed OpenClaw agent via gateway |
 | `hermes_local` | Local Hermes process | Hermes agent heartbeat worker |
@@ -434,7 +435,7 @@ The core Paperclip system must be extensible. Features like knowledge bases, ext
 - Well-defined API boundaries that plugins can hook into
 - Event system or hooks for reacting to task/Agent lifecycle events
 - **Agent Adapter plugins** — new Adapter types can be registered via the plugin system
-- Plugin-registrable UI components (future)
+- Plugin-registrable UI components (toolbar buttons, pages, slots)
 
 The plugin framework has shipped. Plugins can register new adapter types, hook into lifecycle events, and contribute UI components (e.g. global toolbar buttons). A plugin SDK and CLI commands (`paperclipai plugin`) are available for authoring and installing plugins.