@caddis/cli 0.4.33 → 0.4.35

package/bundles/codex/.codex/skills/docs/tech-explainer/SKILL.md

@@ -2,18 +2,13 @@
 name: tech-explainer
 context: fork
 description: >-
-  Write a plain-language technical explainer for a smart reader who did NOT do the investigation — a
-  manager, an infra colleague, a stakeholder, the person whose recommendation you are answering.
-  Layered Mermaid diagrams that rank causes by SIZE OF EFFECT, a controlled-vocabulary table,
-  Simplified Technical English, published withdrawn results, and questions back to the reader. Use
-  this skill whenever the user says "explain this to X", "explainer", "write this up for someone
-  non-technical", "plain English", "simplified technical english", "STE", "explain our findings",
-  "write up the benchmark results", "answer my manager's recommendations", "why is it slow — document
-  it", "make a doc with diagrams explaining the stack", or is about to summarise an investigation, a
-  benchmark, a postmortem, an architecture, or a disagreement for a reader who will not read the raw
-  data. NOT for handing off work to be BUILT by a vendor or another team (use explainer-doc for that —
-  it produces an actionable spec); NOT for READMEs or API docs (use technical-writing). This one
-  produces UNDERSTANDING: the reader must finish able to argue with you on the merits.
+  Plain-language explainer, with ranked Mermaid diagrams and Simplified Technical English, for a
+  reader who did NOT do the investigation (manager, stakeholder). Use when the user says "explain
+  this to X", "explainer", "write this up for someone non-technical", "plain English", "simplified
+  technical english", "STE", "explain our findings", "write up the benchmark results", "answer my
+  manager's recommendations", "why is it slow — document it", "make a doc with diagrams explaining
+  the stack", or summarises an investigation for a reader who won't read the raw data. Not for build
+  hand-offs (explainer-doc) or READMEs.
 ---
 
 # tech-explainer — make a stranger understand, and able to push back

package/bundles/codex/.codex/skills/docs/technical-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: technical-writing
 context: fork
-description: Technical documentation best practices for READMEs, API docs, architecture docs, runbooks, and developer guides. Use when writing or reviewing documentation, creating onboarding guides, or establishing documentation standards.
+description: Documentation best practices for READMEs, API docs, architecture docs, runbooks and developer guides. Use when writing or reviewing docs or setting documentation standards.
 ---
 
 # Technical Writing Skill

package/bundles/codex/.codex/skills/frontend/css-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: css-architecture
-description: CSS architecture, design token strategy, Tailwind conventions, CSS Modules, container queries, dark mode, responsive patterns, and animation architecture. Use for design token naming, CSS custom properties, Tailwind config, container queries, dark mode implementation, fluid typography, or CSS animation decisions. Complements frontend-design (what to achieve) with how to implement it.
+description: "CSS architecture: design tokens, custom properties, Tailwind config, CSS Modules, container queries, dark mode, fluid typography, animation. Covers how to implement styling; frontend-design covers what to achieve."
 ---
 
 # CSS Architecture Skill

package/bundles/codex/.codex/skills/frontend/frontend-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics while strictly adhering to the user's technical standards.
+description: Create distinctive, production-grade frontend interfaces that avoid generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters or applications.
 ---
 
 # Frontend Design Skill

package/bundles/codex/.codex/skills/frontend/react-dev/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-dev
 version: 1.0.0
-description: This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
+description: "Type-safe React 18-19 with TypeScript: components, generic components, hooks, events, Server Components, TanStack Router and React Router. Use when React TypeScript or React 19 is involved."
 ---
 
 # React TypeScript

package/bundles/codex/.codex/skills/frontend/ui-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-review
-description: Review UI implementations against design requirements, accessibility standards (WCAG 2.2 AA), and brand guidelines. Use when reviewing designs or validating UI before release.
+description: Review a UI against design requirements, WCAG 2.2 AA and brand guidelines. Use when validating UI before release.
 ---
 
 # UI Review Skill

package/bundles/codex/.codex/skills/frontend/warm-editorial-ui/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: warm-editorial-ui
-description: Apply the "Warm Editorial Refinement" design system — a sophisticated, executive-grade aesthetic with warm cream surfaces (light mode) and warm charcoal surfaces (dark mode), Bahnschrift + Plus Jakarta Sans typography, generous rounded corners, multi-layer shadows, and a warm neutral palette. Supports both light and dark themes via CSS custom properties and the `.dark` class. Use this skill whenever the user wants to build an app, dashboard, component, or web UI using the abc-project visual style. Trigger on phrases like "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or any request to build a new tool/app/dashboard for XYZ Brand or similar contexts. This is the canonical design template for all new frontend builds.
+description: Apply the "Warm Editorial Refinement" design system (warm cream/charcoal surfaces, Bahnschrift + Plus Jakarta Sans, layered shadows), the canonical template for new frontend builds. Use for apps, dashboards or UI in the abc-project style, or on "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or a new tool for XYZ Brand.
 ---
 
 # Warm Editorial Refinement — Design System

package/bundles/codex/.codex/skills/media/mermaid-diagrams/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mermaid-diagrams
 context: fork
-description: Create software diagrams using Mermaid text-based syntax. Use for class diagrams (domain modeling, OOP design), sequence diagrams (API flows, interactions), flowcharts (processes, algorithms, user journeys), ERD (database schemas), C4 architecture diagrams, state diagrams, git graphs, gantt charts, and data visualization.
+description: "Software diagrams in Mermaid: class, sequence, flowchart, ERD, C4, state, git graph, gantt. Use for domain models, API flows, processes and database schemas."
 ---
 
 # Mermaid Diagramming

package/bundles/codex/.codex/skills/media/particle-art/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: particle-art
 version: 1.0.0
-description: Generate animated particle art React/Next.js components — zero dependencies, spring physics, CSS-variable theming, DPR-correct canvas, mouse interaction. Use when the user wants animated hero art, a living logo, a branded initial or monogram, a constellation background, or any "particles that form a shape". Triggers on "particle animation", "node network", "animated letter/logo/initials", "living letter", "morphing particles", "constellation", "neural net art", "dot field", "stipple portrait", "halftone animation", "ASCII art animation", "background art for my site", or "art that reacts to mouse". Covers — text/initials → spring-node letter; preset patterns (constellation, helix, spiral, DNA, hex-grid, wave, infinity); custom SVG paths; custom polygon points; Unicode halftone stipple; Gaussian dot field with sparks; SVG circuit traces; hybrid combos. Outputs a complete, self-contained, copy-paste-ready React component. Prefer this over p5.js (zero-dep, React-native, TypeScript), tsParticles (richer spring physics, CSS-var theming), Three.js (lightweight, no WebGL).
+description: Zero-dependency animated particle art as a React/Next.js component (spring physics, CSS-variable theming, mouse interaction). Use for animated hero art or a living logo, or on "particles that form a shape", "particle animation", "node network", "animated letter/logo/initials", "living letter", "morphing particles", "constellation", "neural net art", "dot field", "stipple portrait", "halftone animation", "ASCII art animation", "background art for my site", or "art that reacts to mouse".
 ---
 
 # Particle Art Generator

package/bundles/codex/.codex/skills/testing/playwright/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: playwright
 context: fork
-description: Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
+description: "Browser automation and testing with Playwright: auto-detects dev servers; tests pages, forms, logins, links, screenshots and responsive layouts. Use to test websites or automate any browser task."
 ---
 
 **IMPORTANT - Path Resolution:**

package/bundles/codex/.codex/skills/testing/test-strategy/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: test-strategy
 context: fork
-description: Test planning and strategy for projects of any size. Use when defining what to test, choosing test types, setting coverage goals, building test pyramids, or planning quality gates. Produces TEST-STRATEGY.md with prioritized test plan. Routes to Tester agent for execution.
+description: "Plan what to test: test types, coverage goals, test pyramid, quality gates. Produces a prioritized TEST-STRATEGY.md for the Tester agent."
 ---
 
 # Test Strategy Skill

package/bundles/codex/.codex/skills/testing/webapp-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: webapp-testing
 context: fork
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+description: "Test local web apps with Playwright: verify frontend behavior, debug UI, capture screenshots and browser logs."
 license: Complete terms in LICENSE.txt
 ---
 

package/bundles/codex/.codex/skills/workflow/advisory-hub/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: advisory-hub
-description: Cross-session phase validation for multi-phase implementation plans — a long-lived "Hub" session RE-DERIVES each implementation phase's claims independently instead of trusting its self-assessment. Use when the user says "advisory hub", "validate this phase", "phase report", "hub verdict", "advisory context", "who checks the implementing session", "the plan turned out to be wrong", "hand off the hub", "re-derive don't trust", or when a long, multi-session plan with expensive-to-reverse decisions (a migration, a security change, anything touching production data correctness) needs an independent session that verifies every phase before the next one starts. NOT for a three-phase feature — it costs a full extra session's context per phase, and a skill that doesn't say so gets applied everywhere and resented. Every Hub artefact belongs in `.caddis/advisory-hub-reports/` — a succession prompt is `hub-NN.spawn.md` there, never a generic prompts folder, even when you write it by hand instead of running `/caddis:spawn-hub`.
+description: A long-lived "Hub" session re-derives each phase of a multi-session plan instead of trusting its self-report. Use when the user says "advisory hub", "validate this phase", "phase report", "hub verdict", "advisory context", "who checks the implementing session", "the plan turned out to be wrong", "hand off the hub", "re-derive don't trust", or a long plan with expensive-to-reverse work (a migration, a security change, production data correctness) needs independent checks; not for short features. Hub artefacts, including `hub-NN.spawn.md`, go in `.caddis/advisory-hub-reports/`.
 ---
 
 # Advisory Hub — cross-session phase validation

package/bundles/codex/.codex/skills/workflow/skill-creator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-creator
 context: fork
-description: Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
+description: Create, edit and improve skills, run evals and benchmarks, and optimize a skill's description for triggering accuracy.
 ---
 
 # Skill Creator

package/bundles/codex/AGENTS.md

@@ -47,11 +47,15 @@ Claude Code has subagents with their own context for exactly this; agents withou
 
 ### Resuming a session
 On a fresh session read in order: `.caddis/relay.md` (if present) → the active plan in
-`.caddis/plans/` → its tracker. The conversation is disposable; these files are the truth.
+`.caddis/plans/` → its tracker. Codex has no startup hook and must read `.caddis/relay.md`
+(the workstream index or active relay) on session start. The conversation is disposable;
+these files are the truth.
 
 ## Always-active conventions
 - **Commits**: Conventional Commits (`feat:`, `fix:`, `test:`, `chore:`). One logical change per commit.
 - **Terse**: lead with the answer; results/code over prose.
+- **Reuse**: Before writing new code, search for an existing function to reuse. Prefer the standard library or an installed package over new code or a new dependency.
+- **Shared points**: Before changing a function, find all its callers. Fix the shared point, unless the callers need different behaviour.
 - **Secrets**: never commit; keep env/config secrets git-ignored. Never print credentials.
 - **Document frontmatter**: Every descriptive Markdown deliverable you write (plan, PRD, ADR, design doc,
   runbook, analysis, handoff) must open with a YAML frontmatter block:

package/bundles/manifest.json

@@ -1,8 +1,8 @@
 {
-  "poolVersion": "1.3.120",
+  "poolVersion": "1.3.122",
   "bundles": {
-    "antigravity-plugin": "1.3.120",
-    "antigravity-plugin-extras": "1.3.39",
+    "antigravity-plugin": "1.3.122",
+    "antigravity-plugin-extras": "1.3.40",
     "codex": "unknown"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@caddis/cli",
-  "version": "0.4.33",
+  "version": "0.4.35",
   "description": "Install, update and diagnose the caddis dev harness across every coding agent you use (Claude Code, agy/Antigravity, and more).",
   "keywords": [
     "caddis",