Release v0.1.1 — Codex tool-call count fix, one docs roadmap, pinned lint

.github/dependabot.yml

@@ -1,13 +1,35 @@
 # Keeps GitHub Actions and Python (uv) dependencies fresh. The github-actions
 # updates also handle version drift on the Actions pinned in CI, so we don't
 # hand-pin them to commit SHAs.
+#
+# target-branch is set on every entry because Dependabot otherwise opens against the
+# default branch (main), while CONTRIBUTING requires PRs to be based on dev. Without
+# it, a merged bump lands on main only and dev's CI keeps testing the old version.
+#
+# Version updates are grouped and monthly: one solo maintainer triaging a separate PR
+# per dependency every week is a treadmill, and five open bumps is what that produced.
+# This caps it at two PRs a month. Security advisories are unaffected — Dependabot
+# raises those as they land, outside this schedule and outside the grouping.
+#
+# One group per ecosystem, matched on patterns alone. Splitting runtime from dev tools
+# would need `dependency-type`, which Dependabot supports for pip but not uv, and a
+# group matching nothing falls back to one PR per dependency — the very sprawl this
+# is meant to remove.
 version: 2
 updates:
   - package-ecosystem: "github-actions"
     directory: "/"
+    target-branch: "dev"
     schedule:
-      interval: "weekly"
+      interval: "monthly"
+    groups:
+      github-actions:
+        patterns: ["*"]
   - package-ecosystem: "uv"
     directory: "/"
+    target-branch: "dev"
     schedule:
-      interval: "weekly"
+      interval: "monthly"
+    groups:
+      python-dependencies:
+        patterns: ["*"]

CHANGELOG.md

@@ -4,6 +4,20 @@ All notable changes to Curator are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.1] — 2026-07-28
+
+### Fixed
+- **Codex tool-call counts in the activity block.** One Codex command emits several
+  lifecycle events (`item.started`, then `item.completed`) for the same call, and the
+  coalesced `⏺ label ×N` block counted each of them — reading about 2× high. Events are now
+  folded by item id, so one logical call counts once. Claude Code (one event per call) and
+  the ledger are unchanged. ([#26](https://github.com/JasonZQH/CURATOR/issues/26))
+
+### Changed
+- **Docs numbering unified.** The "Phase 0/1/2/3" and "V1.1–V1.6" ladders are folded into
+  the single `v0.1.x` roadmap; the affected design docs carry a mapping banner and the new
+  `pi · Curator · Orca architecture` doc is linked from every page as the canonical roadmap.
+
 ## [0.1.0] — Phase 0
 
 First public release. Local, single-writer, sequential — the evidence-driven base the V1
@@ -40,4 +54,5 @@ Serial single-writer (local `flock`, no cross-host coordination); the decisions/
 — not the provider transcript — are the system of record; macOS primary, Linux in CI, Windows
 via WSL2 only.
 
+[0.1.1]: https://github.com/JasonZQH/CURATOR/releases/tag/v0.1.1
 [0.1.0]: https://github.com/JasonZQH/CURATOR/releases/tag/v0.1.0

README.md

@@ -70,11 +70,11 @@ curl -fsSL https://raw.githubusercontent.com/JasonZQH/CURATOR/main/install.sh |
 Or with pipx / uv:
 
 ```bash
-pipx install "git+https://github.com/JasonZQH/CURATOR.git@v0.1.0"
-uvx --from "git+https://github.com/JasonZQH/CURATOR.git@v0.1.0" curator
+pipx install "git+https://github.com/JasonZQH/CURATOR.git@v0.1.1"
+uvx --from "git+https://github.com/JasonZQH/CURATOR.git@v0.1.1" curator
 ```
 
-> Pin a released tag (`@v0.1.0`) for a reproducible install, or drop it to track `main`.
+> Pin a released tag (`@v0.1.1`) for a reproducible install, or drop it to track `main`.
 > On Windows, run inside WSL2.
 
 **Open it** — from any project directory:
@@ -106,7 +106,8 @@ Small requests start immediately; `/gate on` reviews the goal proposal first.
 
 | Version | Status | What it is |
 |---|---|---|
-| **v0.1.0** | Current | Phase 0 — local · single-writer · sequential. `Goal → writer → deterministic verifier → fresh-context reviewer → human confirm`, on a durable SQLite ledger. Opt-in `/resume stash` for the clean-tree guard. |
+| **v0.1.1** | Current | Patch on Phase 0. A Codex tool call is counted once rather than once per lifecycle event, so the activity block no longer reads ~2× high. Docs numbering folded onto a single `v0.1.x` roadmap. |
+| v0.1.0 | Previous | Phase 0 — local · single-writer · sequential. `Goal → writer → deterministic verifier → fresh-context reviewer → human confirm`, on a durable SQLite ledger. Opt-in `/resume stash` for the clean-tree guard. |
 
 v0.1.0 highlights: full-screen first-run trust & setup, keyboard-selectable slash commands and
 proposal actions, PM/Engineer/Reviewer seat labels, persistent history with Tab completion and

docs/future-optimizations.html

@@ -227,10 +227,11 @@ <h2>Keep the path, not the framework</h2>
       <a href="runtime-workspace-ui.html"><span class="di-title">Runtime workspace UI</span><span class="di-desc">The workbench today, the Control Desk target.</span></a>
       <a href="shell-adapter-boundary.html"><span class="di-title">Shell adapter boundary</span><span class="di-desc">What shell may do vs the Python control plane.</span></a>
       <a class="current" href="future-optimizations.html"><span class="di-title">Future optimizations</span><span class="di-desc">The evidence-driven runtime kernel backlog.</span></a>
-      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates and the V1.1–V1.6 ladder.</span></a>
+      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates; its V1.1–V1.6 ladder is now the v0.1.x roadmap.</span></a>
       <a href="v0-alpha-implementation-status.html"><span class="di-title">Implementation status</span><span class="di-desc">What PR1–PR5 actually landed.</span></a>
       <a href="release-notes-v0.1.0.html"><span class="di-title">v0.1.0 release notes</span><span class="di-desc">What ships, and the known limits.</span></a>
       <a href="orca-parallel-orchestration-and-task-memory.html"><span class="di-title">Parallel orchestration &amp; task memory</span><span class="di-desc">Orca's parallelism as evidence-backed state.</span></a>
+      <a href="pi-orca-curator-architecture.html"><span class="di-title">pi · Curator · Orca architecture</span><span class="di-desc">The canonical v0.1.x → v0.2.0 roadmap.</span></a>
     </nav>
     <div class="foot-meta"><span class="chip live">Phase 0</span> local · single-writer · sequential — the V1 blueprint is a migration target, not current capability.</div>
   </footer>

docs/orca-parallel-orchestration-and-task-memory.html

@@ -29,6 +29,13 @@ <h1>并行编排与任务记忆</h1>
       </p>
     </div>
 
+    <div class="callout">
+      <strong>编号已合并。</strong>本文的 <b>V1.1–V1.6</b>（以及早期的「阶段 0/1/2/3」）已并入单一的
+      <b>v0.1.x</b> 编号；正文按原样保留为历史记录。对照：V1.1 → v0.1.4·5 · V1.2 → v0.1.6·7·8 ·
+      V1.3 → v0.1.9 · V1.4 → v0.1.11 · V1.5 → v0.1.7 · V1.6 → v0.1.12·13·14。当前规范路线图见
+      <a href="pi-orca-curator-architecture.html">pi · Curator · Orca 三层架构</a>。
+    </div>
+
     <div class="callout">
       <strong>状态：</strong>提议，作为 Curator V1 并行编排与任务记忆的设计输入。
       <div style="margin-top:10px">
@@ -303,10 +310,11 @@ <h3>明确延后</h3>
       <a href="runtime-workspace-ui.html"><span class="di-title">Runtime workspace UI</span><span class="di-desc">The workbench today, the Control Desk target.</span></a>
       <a href="shell-adapter-boundary.html"><span class="di-title">Shell adapter boundary</span><span class="di-desc">What shell may do vs the Python control plane.</span></a>
       <a href="future-optimizations.html"><span class="di-title">Future optimizations</span><span class="di-desc">The evidence-driven runtime kernel backlog.</span></a>
-      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates and the V1.1–V1.6 ladder.</span></a>
+      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates; its V1.1–V1.6 ladder is now the v0.1.x roadmap.</span></a>
       <a href="v0-alpha-implementation-status.html"><span class="di-title">Implementation status</span><span class="di-desc">What PR1–PR5 actually landed.</span></a>
       <a href="release-notes-v0.1.0.html"><span class="di-title">v0.1.0 release notes</span><span class="di-desc">What ships, and the known limits.</span></a>
       <a class="current" href="orca-parallel-orchestration-and-task-memory.html"><span class="di-title">Parallel orchestration &amp; task memory</span><span class="di-desc">Orca's parallelism as evidence-backed state.</span></a>
+      <a href="pi-orca-curator-architecture.html"><span class="di-title">pi · Curator · Orca architecture</span><span class="di-desc">The canonical v0.1.x → v0.2.0 roadmap.</span></a>
     </nav>
     <div class="foot-meta"><span class="chip live">Phase 0</span> local · single-writer · sequential — the V1 blueprint is a migration target, not current capability.</div>
   </footer>

docs/orchestration.html

@@ -174,10 +174,11 @@ <h2>Migration order</h2>
       <a href="runtime-workspace-ui.html"><span class="di-title">Runtime workspace UI</span><span class="di-desc">The workbench today, the Control Desk target.</span></a>
       <a href="shell-adapter-boundary.html"><span class="di-title">Shell adapter boundary</span><span class="di-desc">What shell may do vs the Python control plane.</span></a>
       <a href="future-optimizations.html"><span class="di-title">Future optimizations</span><span class="di-desc">The evidence-driven runtime kernel backlog.</span></a>
-      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates and the V1.1–V1.6 ladder.</span></a>
+      <a href="v0-alpha-release-plan-v3.html"><span class="di-title">v0.1.0 release plan (v3)</span><span class="di-desc">Release gates; its V1.1–V1.6 ladder is now the v0.1.x roadmap.</span></a>
       <a href="v0-alpha-implementation-status.html"><span class="di-title">Implementation status</span><span class="di-desc">What PR1–PR5 actually landed.</span></a>
       <a href="release-notes-v0.1.0.html"><span class="di-title">v0.1.0 release notes</span><span class="di-desc">What ships, and the known limits.</span></a>
       <a href="orca-parallel-orchestration-and-task-memory.html"><span class="di-title">Parallel orchestration &amp; task memory</span><span class="di-desc">Orca's parallelism as evidence-backed state.</span></a>
+      <a href="pi-orca-curator-architecture.html"><span class="di-title">pi · Curator · Orca architecture</span><span class="di-desc">The canonical v0.1.x → v0.2.0 roadmap.</span></a>
     </nav>
     <div class="foot-meta"><span class="chip live">Phase 0</span> local · single-writer · sequential — the V1 blueprint is a migration target, not current capability.</div>
   </footer>