pi-soly 1.3.0 → 1.4.0

package/README.md

@@ -4,7 +4,7 @@
 
 **The project management framework for [pi-coding-agent](https://github.com/nicobailon/pi-coding-agent).**
 
-Plans · State · Subagents · Multi-question picker · Rotor switcher · Live task list.
+Plans · State · Subagents · Multi-question picker · Live task list.
 
 One `npm install`. Zero config. Pure magic.
 
@@ -30,7 +30,7 @@ That's it. Restart pi, and you have:
 
 - **A complete project management engine** — plans, state, subagent-driven execution
 - **A multi-question picker** — `ask_pro` tool for the LLM
-- **A rotor switcher** — `Ctrl+Tab` to cycle, footer pill always visible
+- **Live task list + notifications** — see nudge + deprecation warnings as framed Box widgets
 - **A live task list** — `todo_update` tool renders in the footer
 - **7 soly agents** installed on first run
 
@@ -43,7 +43,7 @@ That's it. Restart pi, and you have:
 | Write your own planning workflow | `/plan`, `/execute`, `/resume`, `/inspect` — ready |
 | Manually dispatch subagents | `useSolyWorkerSubagents: true` — automatic routing |
 | 3 different packages for pickers/tasks/agents | One package, one config, one install |
-| Rotor name as free text in slash commands | Footer pill + `Ctrl+Tab` + `/rotor` picker |
+| Mode selection (oracle/scout/reviewer) | LLM picks via `subagent(...)` based on task brief |
 | Re-invent the state machine | `.soly/STATE.md` + auto-managed phases |
 
 ---
@@ -94,30 +94,6 @@ ask_pro({
 })
 ```
 
-### 🎛 Rotor Switcher
-
-Footer pill that's always there. `Ctrl+Tab` to cycle. No popup, no friction.
-
-```
-[model]  · ⚡ worker    · todos 2/5: write tests   ← footer, always visible
-[model]  ▶ 🐢 oracle    · todos 2/5: write tests   ← after one Ctrl+Tab
-[model]  · 🔍 scout     · todos 2/5: write tests   ← after two
-```
-
-Agents:
-- `worker` — default, full read+write
-- `oracle` — read-only decision advisor
-- `scout` — codebase reconnaissance
-- `researcher` — external docs, ecosystem
-- `planner` — architecture and decomposition
-- `context-builder` — hands off context to other agents
-- `reviewer` — adversarial code review, read-only
-- `delegate` — chains agents together
-
-### 📝 Live Task List
-
-`todo_update` tool — renders in the footer as `todos 2/5: current action`.
-
 The LLM can update its own task list mid-turn. You watch progress without re-asking.
 
 ```ts
@@ -171,11 +147,11 @@ todo_update({
                          ▼
                 ┌──────────────────┐
                 │  switch/         │
-                │  rotor switcher  │
+                │  (no rotors —    │
                 │                  │
                 │  Ctrl+Tab        │
                 │  footer pill     │
-                │  /rotor picker   │
+                │   removed 1.4)   │
                 └────────┬─────────┘
                          │
                          ▼
@@ -196,7 +172,7 @@ todo_update({
 
 ## 📚 Documentation
 
-- **Slash commands** — `/plan`, `/execute`, `/resume`, `/inspect`, `/discuss <N>`, `/quick <task>`, `/rotor`
+- **Slash commands** — `/plan`, `/execute`, `/resume`, `/inspect`, `/discuss <N>`, `/quick <task>`
 - **Tools** — `ask_pro(question[])` and `todo_update(todo[])`
 - **Events** — `session_start`, `before_agent_start`, `message_end`, `tool_call`, `tool_result`
 - **State files** — `.soly/STATE.md`, `.soly/ROADMAP.md`, `.soly/phases/<N>-<slug>/<N>-PLAN.md`

package/commands.ts

@@ -418,8 +418,8 @@ What must the LLM do?
 			};
 			const subcommands: Record<string, SolySub> = {
 				// `agent` subcommand REMOVED — moved to the separate `pi-switch`
-				// extension as the `/rotor` slash command (footer pill + Ctrl+Tab).
-				// Soly no longer owns the rotor switcher UI.
+				// extension (rotor switcher removed in 1.4.0).
+				// Soly no longer owns a rotor switcher.
 				config: {
 					description: "show merged config (per-project + global + defaults); edit .soly/config.json or ~/.soly/config.json",
 					run: () => {

package/index.ts

@@ -66,7 +66,7 @@ import { loadIntentDocs, buildIntentSection, loadInlineIntentBodies, type Intent
 
 // Built-in sub-features (merged from former pi-asked, pi-agented packages):
 import piAskExtension from "./ask/index.ts";
-import piSwitchExtension from "./switch/index.ts";
+
 
 export default function solyExtension(pi: ExtensionAPI) {
 	// ============================================================================
@@ -82,19 +82,7 @@ export default function solyExtension(pi: ExtensionAPI) {
 	let sessionCwd = "";
 
 	// ============================================================================
-	// Rotor switcher (Shift+Tab cycles through available rotors)
-	// ============================================================================
-
 	// ============================================================================
-	// Rotor switcher: REMOVED. The rotor cycler is now owned by the
-	// separate `pi-switch` extension (footer pill + Ctrl+Tab + /rotor slash).
-	// Soly no longer ships a subagent (removed in 1.3.0). The LLM does plan
-	// execution directly using slash commands + the soly-framework skill.
-	// Workflows read the current rotor from globalThis.__PI_SWITCH_ROTOR__
-	// (set by pi-switch).
-	// ============================================================================
-
-	// Config (per-project + global + defaults). Refreshed on session_start
 	// and on each session_start (the LLM can call /soly config to view).
 	let activeConfig: SolyConfig = DEFAULT_CONFIG;
 	const getActiveConfig = (): SolyConfig => activeConfig;
@@ -262,7 +250,6 @@ export default function solyExtension(pi: ExtensionAPI) {
 		const hint = buildNextHint(state);
 		const hintGroup = hint ? `${"\x1b[2m"}${hint}${"\x1b[0m"}` : "";
 
-		// Agent badge — owned by pi-switch extension (header bar + status line).
 		// Soly doesn't render the agent badge itself.
 		const agentGroup = "";
 
@@ -325,18 +312,6 @@ export default function solyExtension(pi: ExtensionAPI) {
 		getConfig: getActiveConfig,
 	});
 
-	// ============================================================================
-	// Agent switcher: Ctrl+Shift+A cycles through available subagents.
-	// (Shift+Tab is taken by pi's thinking-level cycler; Ctrl+Shift+A is unused
-	// and mnemonic for "A"gent.)
-	// ============================================================================
-	// Agent switcher REMOVED — moved to the separate `pi-switch` extension.
-	// Soly no longer owns Ctrl+Tab, the footer pill, or /rotor slash.
-	// The current agent is read by soly workflows from
-	// globalThis.__PI_SWITCH_AGENT__ (set by pi-switch), with a fallback
-	// to "worker" if pi-switch isn't installed.
-	// ============================================================================
-
 	registerWorkflows(pi, {
 		getState: () => state,
 		getInteractiveRules: () =>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-soly",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "description": "Project management framework for pi-coding-agent. Workflows, planning, multi-question picker, agent switcher, live task list — one npm install, zero config.",
   "type": "module",
   "main": "index.ts",
@@ -40,7 +40,6 @@
     "agents-install.ts",
     "ask",
     "skills",
-    "switch",
     "workflows",
     "workflows-data"
   ],

package/skills/soly-framework/SKILL.md

@@ -1,11 +1,6 @@
----
-name: soly-framework
-description: Use when the user asks how to do anything with the soly framework for pi — start a new project, plan or execute a phase, pause and resume sessions, add rules, add intent docs, write PLAN.md or SUMMARY.md, troubleshoot issues. Triggers on "how do I", "what's the command for", "soly help", "soly framework", and any practical question about using the soly extension. NOT loaded for generic code questions — only when the user is working with the soly workflow.
----
-
 # soly framework
 
-The **soly** extension adds project-management workflow to [pi-coding-agent](https://github.com/nicobailon/pi-coding-agent): intent docs, ROADMAP/STATE/PHASE state machine, and subagent-driven plan execution. This skill is your complete reference for using it.
+The **soly** extension adds project-management workflow to [pi-coding-agent](https://github.com/nicobailon/pi-coding-agent): intent docs, ROADMAP/STATE/PHASE state machine, and LLM-driven plan execution. This skill is your complete reference for using it.
 
 ## Quick start (read first if new)
 
@@ -22,7 +17,7 @@ The **soly** extension adds project-management workflow to [pi-coding-agent](htt
 - A **task** is the smallest unit. Has type, description, verify, accept.
 - **Close-out**: production code commits → `SUMMARY.md` → `STATE.md` updated → ROADMAP check.
 
-## Slash commands (interactive mode)
+## Quick reference — slash commands
 
 | Command | What it does |
 |---|---|
@@ -35,10 +30,21 @@ The **soly** extension adds project-management workflow to [pi-coding-agent](htt
 | `/quick <task>` | One-shot task that doesn't need a full plan — direct dispatch |
 | `/soly` | Project state inspection (alias for `/inspect`) |
 | `/why` | Show what context the LLM's last turn was based on |
-| `/rotor [name]` | Switch the current rotor (or open picker) |
+| `/soly-init` | Scaffold a new soly project (interactive template picker) |
+| `/soly-migrate` | Move legacy `.soly/` to `.agents/` (atomic) |
+| `/soly-status` | Comprehensive one-screen report |
+| `/soly-log [N]` | Show last N notifications from the log |
 
 `/soly <verb>` plain-text aliases also work for some verbs (legacy compat).
 
+## No rotors (removed in 1.4.0)
+
+As of 1.4.0, soly no longer ships rotors. No `/rotor` command, no `Ctrl+Tab` cycle, no footer pill. The LLM picks the right subagent based on the task brief — use `subagent(...)` with `agent: "worker"` for implementation, `"oracle"` for decisions, `"scout"` for recon, `"reviewer"` for adversarial review.
+
+**Why drop them?** Rotors were a UX shortcut (Ctrl+Tab) that pi itself doesn't support well. pi has its own subagent system (`worker`, `oracle`, `scout`, `reviewer`); wrapping it in a "cycle" was over-engineering. The LLM in the main session is the executor; pi's subagents are helpers, not cycle modes.
+
+**For soly work**, the LLM does the work itself — it reads PLAN.md, runs commands, commits, writes SUMMARY.md. It does NOT spawn a soly subagent. Use `subagent(...)` only for read-only research (e.g. `agent: "scout"` for "find all files using X").
+
 ## File structure
 
 ```
@@ -69,26 +75,19 @@ The **soly** extension adds project-management workflow to [pi-coding-agent](htt
 │   └── .continue-here.md          # pause resume marker
 ├── .agents/                       # vendor-neutral agent config (per project)
 │   ├── rules/                     # agent rules (loaded with priority 3, after .soly/rules/)
-│   │   ├── code-style.md
-│   │   └── testing.md
 │   ├── skills/                    # project-scoped skills (pi auto-discovers)
 │   │   └── my-skill/
 │   │       └── SKILL.md
 │   ├── docs/                      # agent-specific docs (intent-style)
-│   │   └── architecture.md
 │   └── agents/                    # project-specific agent definitions
-│       ├── project-reviewer.md
-│       └── data-scientist.md
 ```
 
-**Two parallel conventions (migration in progress):** `.soly/` is the legacy soly state. `.agents/` is the new vendor-neutral home. The two work side-by-side:
+**Two parallel conventions:** `.soly/` is soly-specific state. `.agents/` is vendor-neutral agent config. The two coexist:
 
-- **Use `.agents/`** for new projects (recommended)
-- **Use `.soly/`** for legacy projects (still works, will show a deprecation warning)
+- **Use `.soly/`** for soly workflow artifacts (PLAN.md, SUMMARY.md, etc.)
+- **Use `.agents/`** for things other AI tools should also see (rules, skills, agents)
 - **Use `AGENTS.md`** for top-level project-wide agent conventions
 
-To migrate: `mv .soly .agents` — soly picks up the new location automatically. No data loss.
-
 ## Frontmatter conventions
 
 ### PLAN.md frontmatter (required)
@@ -200,23 +199,6 @@ The only legal sequence for finishing a plan:
 
 Once production commits exist, returning without a committed `SUMMARY.md` is an **illegal partial-plan state** — the next `/execute` will detect it and refuse to start.
 
-## Cycle rotors (4 built-in)
-
-| Rotor | Writes | Use for |
-|---|---|---|
-| `worker` | ✅ | Generic implementation, full tools |
-| `oracle` | ❌ | Decision-consistency, no file edits |
-| `scout` | ❌ | Codebase recon, read-only |
-| `reviewer` | ❌ | Adversarial code review |
-
-Switch with `/rotor <name>` or `Ctrl+Tab` (cycles through). Footer pill shows current: `· ⚡ worker` / `▶ 🐢 oracle`.
-
-**Why "rotors"?** Because they *rotate* — `Ctrl+Tab` cycles through them. The word emphasizes the cycling behavior. As of 1.3.0 there are no soly subagents — only the cycle rotors.
-
-## Subagent: none (as of 1.3.0)
-
-**Soly no longer ships a subagent.** You (the LLM) execute plans directly in the main session using the slash commands above. If you need help, use pi's built-in cycle agents (\`worker\`, \`oracle\`, \`scout\`, \`reviewer\`) or the user's custom agents in \`~/.agents/\`. Don't spawn \`soly-manager\` / \`soly-worker\` / etc. — they don't exist.
-
 ## Tools the LLM can call
 
 | Tool | Purpose |
@@ -234,51 +216,6 @@ Switch with `/rotor <name>` or `Ctrl+Tab` (cycles through). Footer pill shows cu
 | `ask_pro(questions)` | Multi-question picker (tabbed, single/multi-select, ⭐, Other…) |
 | `todo_update(todos)` | Update task list rendered in footer |
 
-## Add a new rule (most common task)
-
-Three places, in priority order:
-
-1. **Project rule** — `~/.pi/agent/agents/soly/rules/<name>.md` (version-controlled, shared with team)
-2. **User rule** — `~/.soly/rules/<name>.md` (per-user, not committed)
-3. **Phase rule** — `<phase-dir>/<plan>.md.rules/<name>.md` (active only for that plan)
-
-Use `/rulewizard` slash command to scaffold a new rule with the right frontmatter.
-
-A rule file looks like:
-
-```markdown
----
-applyTo: "src/**/*.ts"
-priority: 50
----
-
-# TypeScript style
-
-- Strict mode required
-- Never use `any`
-- Prefer `type` over `interface`
-```
-
-## Add a new intent doc
-
-Create a file in `.soly/docs/`:
-
-```markdown
-# Architecture
-
-## Goal
-
-Build a CLI tool that...
-
-## Non-obvious constraints
-
-- Must work offline (no network calls)
-- Must be a single static binary
-- Must integrate with the existing `~/.config/x` schema
-```
-
-Intent docs are 0-point — written BEFORE any plan, by humans. They define the "why", not the "how".
-
 ## Common workflows
 
 ### Start a new project
@@ -287,11 +224,11 @@ Intent docs are 0-point — written BEFORE any plan, by humans. They define the
 2. Write 1-3 intent docs in `.soly/docs/`
 3. Optionally write `AGENTS.md` (or `agents.md`) at project root with project conventions
 4. Create `ROADMAP.md` with phase table
-5. `/plan 1` to start phase 1
+5. `/plan 1` to start the first phase
 
 ### Add project-specific agents
 
-Drop a markdown file in `.agents/<name>.md` (project) or `~/.agents/<name>.md` (user):
+Drop a markdown file in `.agents/agents/<name>.md` (project) or `~/.agents/agents/<name>.md` (user):
 
 ```markdown
 ---
@@ -310,7 +247,7 @@ You are a data scientist. ...
 3. `~/.agents/` — user vendor-neutral (preferred)
 4. `~/.pi/agent/agents/` — user pi native (legacy)
 
-`Ctrl+Tab` to see them in the cycle.
+`Ctrl+Tab` to see them in the cycle. (Removed in 1.4.0 — use `subagent(...)` directly.)
 
 ### Add a feature to an existing phase
 
@@ -332,24 +269,14 @@ If `/execute` complains about illegal partial state:
 3. If yes, finish close-out: update `STATE.md` + `ROADMAP.md`
 4. If no, either commit the SUMMARY or revert the production commits
 
-## Where to look for answers
+## When in doubt
 
-- **"What command does X"** → this skill, Slash commands section
-- **"What does PLAN.md look like"** → this skill, Frontmatter section
-- **"How to add a rule"** → this skill, Add a new rule section
-- **"Why did the LLM do Y"** → `/why`
-- **"What context is loaded"** → `soly_read(artifact: "state")` + `soly_doc_search(...)`
-- **"What was the recent conversation"** → `soly_scratchpad()`
+Call `soly_read(artifact: "state")` and `soly_read(artifact: "roadmap")` first. The system prompt has the layers, but `soly_read` gives you full content. Then check `soly_doc_search` for any other relevant docs.
 
 ## Don'ts
 
 - ❌ Edit `.soly/rules/` files you didn't write — those are project invariants
 - ❌ Skip the SUMMARY — illegal partial state
-- ❌ Spawn `soly-manager` / `soly-worker` / etc. — there are no soly subagents (removed in 1.3.0). Use pi's built-in subagents via the parent LLM's \`subagent(...)\` call.
-- ❌ Write rules in code comments — use `.soly/rules/*.md` or `.agents/rules/*.md` files
+- ❌ Spawn `soly-manager` / `soly-worker` / etc. — there are no soly subagents (removed in 1.3.0). Use pi's built-in subagents via the parent LLM's `subagent(...)` call.
 - ❌ Edit `.soly/phases/*/PLAN.md` after `status: in_progress` — create a new plan
-- ❌ Put intent docs anywhere other than `.soly/docs/` (or `.agents/docs/` for vendor-neutral)
-
-## When in doubt
-
-Call `soly_read(artifact: "state")` and `soly_read(artifact: "roadmap")` first. The system prompt has the layers, but `soly_read` gives you full content. Then check `soly_doc_search` for any other relevant docs.
+- ❌ Put intent docs anywhere other than `.soly/docs/`

package/switch/README.md

@@ -1,104 +0,0 @@
-# pi-switch — generic subagent switcher for pi
-
-A tiny pi extension that gives you a **persistent indicator of the current subagent** (footer pill) and lets you **cycle / set / create** agents. Generic — works with any agent in `~/.pi/agent/agents/`.
-
-## Features
-
-- **Footer pill** — always shows current agent with emoji + description
-- **Ctrl+Tab** to cycle to next agent (Shift+Tab is taken by pi's thinking-level cycler)
-- **F2** as fallback for terminals that don't pass Ctrl+Tab through
-- **`/agent`** slash command to show current + available
-- **`/agent <name>`** to set explicitly
-- **`/agent create <name>`** to scaffold a new user agent
-- **`/agent doctor`** to diagnose
-- **`/agent recommend <task>`** to suggest the right agent for a task
-- **Task → agent heuristics** baked into the system prompt so the LLM picks the right agent for the task
-- Persists to `.soly/agent` (if soly project) or `~/.pi-switch/agent` (standalone)
-- Reads user agents from `~/.pi/agent/agents/*.md` on every cycle — drop a file and Ctrl+Tab to see it
-- Silent switch — only the pill updates, chat stays clean
-
-## How agents work
-
-Agents are markdown files with YAML frontmatter. pi-subagents (and pi-switch) discover them from these locations:
-
-| Path | Type | Editable |
-|---|---|---|
-| `~/.pi/agent/npm/node_modules/pi-subagents/agents/*.md` | built-in (worker, oracle, scout, reviewer) | ❌ |
-| `~/.pi/agent/agents/*.md` | user-defined | ✅ |
-| `~/.pi/agent/extensions/pi-soly/agents/*.md` (auto-installed if `useSolyWorkerSubagents: true` in `.soly/config.json`) | (removed in 1.3.0 — soly no longer ships a subagent) | — |
-
-### Frontmatter schema
-
-```markdown
----
-name: my-reviewer              # required, unique, [a-zA-Z0-9_-]{1,64}
-description: One-liner shown in picker
-thinking: medium               # off | minimal | low | medium | high | xhigh
-systemPromptMode: replace      # replace | append
-inheritProjectContext: true
-inheritSkills: false
-tools: read, grep, find, ls, bash, edit, write
-defaultContext: fork           # fresh | fork
----
-
-You are `my-reviewer`. The system prompt goes here.
-```
-
-## Create a new agent
-
-### Option A: manually
-Drop a markdown file in `~/.pi/agent/agents/<name>.md` (see schema above). Press `Ctrl+Tab` in pi — it joins the cycle.
-
-### Option B: via slash command
-```
-/agent create my-debugger
-```
-You'll be prompted for a one-liner description. Then edit the file to specialize the system prompt.
-
-## Test agents
-
-| Action | How |
-|---|---|
-| See current + available | `/agent` |
-| Cycle | `Ctrl+Tab` (or `F2`) |
-| Set explicitly | `(n/a — no soly subagent since 1.3.0)` |
-| Diagnose | `/agent doctor` |
-| Recommend for a task | `/agent recommend investigate React Server Components` |
-
-The LLM can also auto-pick — see "Task → agent" below.
-
-## Task → agent heuristics
-
-The LLM's system prompt includes a table mapping task keywords to agents. When the user request matches, the LLM should call `/agent <name>` first, then `subagent({ agent: <name>, ... })`.
-
-| Keywords | Agent | Why |
-|---|---|---|
-| scout, scan, map, where is, locate, skim | 🔍 scout | codebase recon |
-| review, audit, check, adversarial, critique, qa | 👀 reviewer | adversarial review |
-| oracle, decision, tradeoff, which approach, drift | 🔮 oracle | decision consistency |
-| implement, build, write code, add feature, debug, fix, test, refactor, document, plan, validate | ⚡ worker | do it yourself using slash commands |
-| (anything else) | ⚡ worker | generic implementation |
-
-Same keywords in Russian work (изучи, баг, тест, etc.).
-
-## Integration with other extensions
-
-- **pi-soly** reads `globalThis.__PI_SWITCH_AGENT__` to know which cycle agent is active. Falls back to `"worker"` if pi-switch isn't loaded.
-- **pi-soly no longer ships a subagent** (removed in 1.3.0). The LLM in the main session executes plans directly using the slash commands + the `soly-framework` skill.
-
-## Files
-
-- `core.ts` — agent metadata, discovery, cycling, persistence
-- `prompt.ts` — system-prompt section + task→agent heuristics + `recommendAgent`
-- `index.ts` — footer pill, Ctrl+Tab / F2, `/agent` slash command, `/agent create`/`/agent doctor`/`/agent recommend`
-- `tests/core.test.ts` — tests for core logic
-- `tests/prompt.test.ts` — tests for prompt + recommendAgent
-- `tests/index.test.ts` — tests for slash command parsing
-
-## Development
-
-```bash
-cd packages/pi-soly/switch
-bun test          # switch tests
-bun run typecheck # tsc --noEmit
-```