claude-dev-env 1.92.0 → 1.92.1

package/CLAUDE.md

@@ -6,15 +6,7 @@ The user delegates execution to you and expects zero manual steps unless strictl
 
 ## Timeless Documentation (all `.md` files)
 
-Every Markdown file I write or edit describes the system's **current** state only. The test: a reader a year out, with zero prior context, finds every sentence true and complete without knowing what came before. State what **is**, not what changed — git history records change; docs record the contract.
-
-- No historical/transitional language (`previously`, `now uses`, `instead of`, `migrated from`, `used to`, `no longer`, `as of`, `originally`, version-transition narration).
-- No references to the conversation that produced the doc (`as discussed`, `Option A`, `after Round 3`).
-
-Full banned-pattern set + enforcement: `~/.claude/rules/no-historical-clutter.md` (hook `state-description-blocker`) and `~/.claude/rules/self-contained-docs.md`.
-
-## GOTCHAS
-ALWAYS start each session with a /loop 15m populate or update the task list based on remaining todos.
+Docs describe the current state only. Full rule set and enforcement: `~/.claude/rules/no-historical-clutter.md` (hook `state-description-blocker`) and `~/.claude/rules/self-contained-docs.md`.
 
 ## Choosing Edit vs Write
 
@@ -63,8 +55,6 @@ When changing how skills, rules, or hooks install or sync in this repo (for exam
 
 ## Additional Non-overlapping Rules
 
-- **task_scope:** Match every action to what was explicitly requested. When intent is ambiguous, research official docs and present options via AskUserQuestion before making any changes. Proceed with edits only on explicit instruction.
-- **confirm_implementation_forks:** When two or more viable paths would satisfy the goal and the choice changes the deliverable — its scope, completeness, deferred work, dependencies, or a hard-to-reverse contract — stop and ask which path via AskUserQuestion before implementing. A path that defers work or leaves a placeholder creating a follow-up task is itself a fork to surface, not a default to take silently. Phrase the question in plain language with only the detail needed to decide. See [`confirm-implementation-forks`](rules/confirm-implementation-forks.md).
 - **disambiguate_overloaded_terms:** When a word in the request has two different technical meanings — "conflict" (git-merge versus functional/behavioral), "sync" (fast-forward versus commit), and the like — confirm which one is meant via AskUserQuestion before analyzing or acting.
 
 ## Serena (Code Intelligence MCP)
@@ -87,31 +77,3 @@ Before any coding task, call the `initial_instructions` tool to load the Serena
 1. **Serena** — symbol-level navigation (declarations, references, implementations, rename)
 2. **es.exe** — file-system search by name/path/extension/size/date (Everything CLI)
 3. **Grep/Glob** — content and pattern matching
-
-## Everything Search (es.exe CLI)
-
-Search files by name, path, extension, size, or date with the Everything command-line tool `es.exe`. It reads the same live index the desktop app keeps, so results return instantly.
-
-### Invocation and scope tokens
-Run `es.exe` with a scoped query — a project path, an `ext:`/`dm:`/`size:` filter, or a name pattern. The `es_exe_path_rewriter` hook resolves a `{project-name}` placeholder or a bare registry key from `~/.claude/project-paths.json` into its quoted absolute path before the command runs (it allows and rewrites, never blocks).
-
-### Hard limits
-- Scope every search. A bare whole-drive scan or a network-share sweep is out of bounds.
-
-### Fallback order
-1. **es.exe** — file-system search by name/path/extension/size/date
-2. **Debug** — try to find out why es.exe isn't working, and then prompt user for next-steps if you can't self-heal.
-3. **Grep** — file-content search (Grep owns content)
-4. **Glob** — relative-path pattern matching within the current project
-
-### Search syntax quick reference
-- `ext:py` — find by extension (multiple: `ext:ts | ext:js`)
-- `path:src\components` — match against full path
-- `*.config.*` — wildcards
-- `size:>10mb` — size filter
-- `dm:today` / `dm:thisweek` — date modified filter
-- `-n 50` — limit results; `-sort dm` — sort by date modified
-- `foo bar` — AND, `foo | bar` — OR, `!foo` — NOT
-- `"exact phrase"` — literal match
-
-Full operator reference: `skills/everything-search/SKILL.md`.

package/bin/install.mjs

@@ -147,7 +147,7 @@ const INSTALL_GROUPS = {
     core: {
         description: 'Development standards, hooks, agents, commands',
         skills: [
-            'team-advisor', 'team-advisor-refresh',
+            'orchestrator', 'orchestrator-refresh',
             'anthropic-plan', 'everything-search',
             'pr-review-responder',
             'recall', 'remember', 'task-build', 'verified-build'

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "claude-dev-env",
-    "version": "1.92.0",
+    "version": "1.92.1",
     "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
     "type": "module",
     "bin": {

package/rules/CLAUDE.md

@@ -1,3 +1,8 @@
+---
+paths:
+  - "**/rules/**"
+---
+
 # rules
 
 Rule files installed into `~/.claude/rules/` by `bin/install.mjs`. Claude Code loads these as always-on behavioral constraints for every session. Each `.md` file covers one named rule; hook-enforced rules are also backed by a Python hook in `hooks/`.

package/rules/testing.md

@@ -12,8 +12,6 @@ paths:
 
 > **Reference:** TEST_QUALITY.md - Load when writing or reviewing tests.
 
-@~/.claude/docs/TEST_QUALITY.md
-
 ## Complete Mocks for Testability
 
 **Mocks must include all fields the component actually uses.**

package/skills/CLAUDE.md

@@ -26,8 +26,8 @@ Skills install to `~/.claude/skills/<skill-name>/` via `packages/claude-dev-env/
 - `implement` — structured implementation from an existing plan packet
 - `bdd-protocol` — BDD depth: Example Mapping, scenario quality, outside-in layout
 - `verified-build` — build + test loop that gates on a verifier verdict
-- `team-advisor` — turns the session into the advisor-orchestrator: it spawns executor subagents to do the code edits and test runs, and answers a blocked executor with a plan, correction, or stop
-- `team-advisor-refresh` — sub-skill fired by the `/team-advisor` loop to re-assert the executor-advisor discipline mid-run
+- `orchestrator` — turns the session into the advisor-orchestrator: it spawns executor subagents to do the code edits and test runs, and answers a blocked executor with a plan, correction, or stop
+- `orchestrator-refresh` — sub-skill fired by the `/orchestrator` loop to re-assert the executor-advisor discipline mid-run
 
 **PR review and convergence**
 - `autoconverge` — autonomous single-run workflow that drives a PR to ready

package/skills/{team-advisor → orchestrator}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: team-advisor
+name: orchestrator
 description: >-
   Turns the session into the advisor-orchestrator — the user's sole interface,
   to plan
@@ -10,14 +10,14 @@ description: >-
   brief signals — a plan, a correction, or a stop. The advisor never edits
   code or runs tests itself. Caps consultations per task (default 5), reuses
   warm workflow agents before spawning new ones, and re-asserts the
-  discipline every 20 minutes through the /team-advisor-refresh loop. Adapts
+  discipline every 20 minutes through the /orchestrator-refresh loop. Adapts
   Anthropic's coordinator pattern (plan big, execute small) to Claude Code.
-  Triggers: '/team-advisor', 'team advisor strategy', 'run with a team
-  advisor', 'executor-advisor mode', 'team advisor enforcement', 'agent
+  Triggers: '/orchestrator', 'orchestrator strategy', 'run with an
+  orchestrator', 'executor-advisor mode', 'orchestrator enforcement', 'agent
   routing', 'orchestrate'.
 ---
 
-# Team Advisor Strategy
+# Orchestrator Strategy
 
 ## Principle
 
@@ -42,7 +42,7 @@ drives the plan and answers the executors when they get stuck.
 
 ## Gotchas
 
-- **Double invocation duplicates the reminder loop.** A second `/team-advisor`
+- **Double invocation duplicates the reminder loop.** A second `/orchestrator`
   in the same session schedules a second refresh loop. Check whether the loop
   is already running before you schedule one (see the invocation guard in
   Process step 1).
@@ -71,10 +71,10 @@ drives the plan and answers the executors when they get stuck.
    second loop.
 
 2. **Register the discipline reminder.** By default, schedule it with
-   `ScheduleWakeup` at `delaySeconds: 1200`, prompt `/team-advisor-refresh`,
+   `ScheduleWakeup` at `delaySeconds: 1200`, prompt `/orchestrator-refresh`,
    where each refresh re-schedules the next one — a 1200-second wakeup costs
    one prompt-cache miss per firing and nothing more (see Gotchas). The loop
-   mechanism (`/loop 20m /team-advisor-refresh`) is the escape hatch when
+   mechanism (`/loop 20m /orchestrator-refresh`) is the escape hatch when
    `ScheduleWakeup` is not available. Either way the reminder is the
    enforcement surface: each firing re-asserts the discipline while the run is
    in flight.
@@ -167,7 +167,7 @@ Routing rules:
 
 ## Constraints
 
-- One `/team-advisor` per session; the invocation guard blocks a second
+- One `/orchestrator` per session; the invocation guard blocks a second
   reminder loop.
 - The advisor orchestrates and advises but never edits code or runs a build or
   test itself — executors do that.

package/skills/{team-advisor-refresh → orchestrator-refresh}/SKILL.md

@@ -1,14 +1,14 @@
 ---
-name: team-advisor-refresh
+name: orchestrator-refresh
 description: >-
-  Fired by the /team-advisor loop reminder about every 20 minutes to
+  Fired by the /orchestrator loop reminder about every 20 minutes to
   re-assert the advisor discipline mid-run. A compressed restatement of
-  /team-advisor: orchestrate rather than execute, answer a blocked executor
+  /orchestrator: orchestrate rather than execute, answer a blocked executor
   with a plan, correction, or stop, and reuse warm agents before spawning new
-  ones. Triggers: '/team-advisor-refresh'.
+  ones. Triggers: '/orchestrator-refresh'.
 ---
 
-# Team Advisor Refresh
+# Orchestrator Refresh
 
 1. **You are the advisor.** Orchestrate and hold the user conversation; spawn
    executor subagents to do all the work — every code edit and build or test