@caddis/cli 0.4.33 → 0.4.35

package/bundles/antigravity-plugin/skills/rca/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: rca
+description: Record a root cause in one step — .caddis/rca/<date>-<slug>.md — or close one with the fixing commit
+---
+
+# /caddis:rca — record a root cause, or close one
+
+A root cause found mid-task gets forgotten by the next session that hits the same symptom. This
+command writes one down in a single step, and closes it later with the commit that fixed it.
+
+The request is **$ARGUMENTS**.
+
+## Mode select
+
+| `$ARGUMENTS` | Do this |
+|---|---|
+| starts with `done ` | Go to **Close mode** |
+| anything else | Go to **File mode** — the text is the symptom |
+
+---
+
+## File mode
+
+### Step 1 — build the slug
+Lower-case the symptom text, replace each run of characters outside `a-z0-9` with one `-`, trim
+`-` from both ends, cap at 60 characters (`Login fails: 401!` → `login-fails-401`). If nothing is left after cleaning, **stop and ask the user for a shorter title** — the
+one question this command may ask.
+
+### Step 2 — pick the path
+`.caddis/rca/<YYYY-MM-DD>-<slug>.md`, using today's date (UTC). Create `.caddis/rca/` first if it
+does not exist.
+
+**If that exact path already exists, refuse — never overwrite it.** Print the existing path and
+stop; the user can open it directly, or pick different (more specific) symptom text so the slug
+comes out differently.
+
+### Step 3 — write the file
+
+```markdown
+---
+type: rca
+status: open
+found: <YYYY-MM-DD>
+---
+
+# <symptom, verbatim>
+
+## Symptom
+<what was observed — the exact error, command, or behaviour>
+
+## Root cause
+<why it happened, not just what happened>
+
+## Fix
+<what changed to remove the cause>
+
+## How verified
+<the command or check that proves the fix, and its result>
+```
+
+Leave a section as its one-line prompt if the answer is not known yet — `/rca done` below is where
+it gets filled in for real.
+
+### Step 4 — verify
+
+```bash
+python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_gate.py" docs-check --root .
+```
+
+Exit 0 means the header is valid. Do not report the item as filed until this passes.
+
+### Step 5 — report
+One line: the path. Nothing else.
+
+---
+
+## Close mode — `done <file>`
+
+`<file>` is a path under `.caddis/rca/`, optionally followed by a commit SHA.
+
+1. If the file does not exist, say so and change nothing.
+2. If its header does not carry `type: rca`, say so and change nothing.
+3. If its `status:` is already `done`, say so and change nothing — closing an already-closed RCA is
+   a no-op, not a re-close.
+4. Otherwise set `status: done` and add `commit: <short SHA>` to the header. The SHA is whatever the
+   user gave after the filename in `$ARGUMENTS`; if none was given, use `git rev-parse --short HEAD`.
+   It must match `^[0-9a-f]{7,40}$`; if it does not, say so and change nothing.
+5. Fill in **Root cause**, **Fix**, and **How verified** only with facts from this session or the
+   fixing commit. A section you do not know stays as its Step 3 prompt; never guess.
+6. Run the Step 4 docs-check. If it does not exit 0, restore the file and report the error.
+7. Report the path and the recorded commit. Nothing else.
+
+## Rules
+- **Never** overwrite an existing RCA file. A repeat symptom is either the same file (edit it by
+  hand) or genuinely different (use different symptom text so the slug comes out different).
+- This command records facts about what already happened; it does not investigate or fix anything
+  itself.

package/bundles/antigravity-plugin/skills/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/antigravity-plugin/skills/safe-cleanup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: safe-cleanup
-description: Use BEFORE deleting any directory tree, clearing a scratchpad, removing git worktrees, or "tidying up" generated folders - especially on Windows, where a recursive delete that meets a junction or symlink destroys the link's TARGET. Also use when verifying that a Python venv or node_modules survived a cleanup, because pip check and file counts both report healthy on a half-deleted environment.
+description: Use BEFORE deleting a directory tree, scratchpad or git worktree, or "tidying up" generated folders, especially on Windows, where deleting through a junction or symlink destroys its target; and to verify a venv or node_modules survived.
 ---
 
 # Safe Cleanup

package/bundles/antigravity-plugin/skills/ship/SKILL.md

@@ -9,10 +9,11 @@ Ship the current working changes via this repo's actual delivery pipeline. The p
 repo, so **detect it first**, then follow the matching lane. Preflight, staging, and commit are
 identical across lanes; only monitoring and validation differ.
 
-> **This is the express lane** — on repos where a push to the default branch deploys, `/ship` sends
-> work straight to prod with no review pause. Right for a hotfix. **For feature work, use the
-> reviewed lane instead: `/ship-pr`** (open a PR, monitor CI, stop at green) **→ `/ship-merge`**
-> (merge the green PR behind a deploy-confirm, validate, clean up).
+> **This is the express lane** — it pushes straight to the default branch with no review pause.
+> Right for a hotfix. On a repo where that push deploys to production, Step 2c stops it before the
+> push and the owner merges. **For feature work, use the reviewed lane instead: `/ship-pr`** (open a
+> PR, monitor CI, stop at green) **→ `/ship-merge`** (merge the green PR behind a deploy-confirm,
+> validate, clean up).
 
 Optional message: **$ARGUMENTS** (if empty, derive a conventional commit message from staged changes)
 
@@ -63,6 +64,19 @@ over 400 changed lines. No judgement in any of those — deliberately, because j
 what failed.
 <!-- /shared:cross-review-trigger -->
 
+**2c. DEPLOY BOUNDARY** — before the push; nothing skips it:
+
+```bash
+python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_gate.py" deploy-boundary --repo .
+```
+
+Exit **0** (no deploy signal found) — push. Exit **1** (a push to the default branch deploys to
+production), exit **3** (it cannot tell), or any other non-zero code — **stop. Do not merge or push to
+the default branch.** The commit stays local. If it sits on the default branch, move it to a feature
+branch first (`git switch -c <feature-branch>`). Then open a PR with `/ship-pr` and hand the merge
+to the owner with the PR link. Show the gate's output and end the command. This holds whatever confirmation was given:
+`--yes`, a confirm flag, "just merge it" or an earlier approval cannot bypass it.
+
 **3. PUSH** — to the repo's default branch (confirm the branch first; don't assume `main`):
 ```
 git push origin <branch>
@@ -113,6 +127,7 @@ Release tag:     <tag> → <sha> | n/a
 
 ## Rules
 - Never push before preflight gates are green.
+- Never push to the default branch unless `deploy-boundary` exited 0 on this run.
 - Never use `git add -A` without reviewing `git status` first.
 - Do not edit a workflow file (`.gitea/workflows/` or `.github/workflows/`) to make a failing gate
   pass — fix the source.

package/bundles/antigravity-plugin/skills/ship-merge/SKILL.md

@@ -28,6 +28,20 @@ Resolve the target PR from `$ARGUMENTS`, else the current branch's open PR. No o
 that and point at `/ship-pr`. Read `AGENTS.md` + the workflow file(s) for the repo's real deploy
 job names and default branch — never assume.
 
+## Step 0b — Deploy boundary (before the confirm; nothing skips it)
+
+Run it before asking for any confirmation, in a checkout of the PR's own repository. If the
+PR belongs to another repository, treat that as exit **3**.
+
+```bash
+python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_gate.py" deploy-boundary --repo .
+```
+
+Exit **0** — go on to Step 1. Exit **1** (a push to the default branch deploys to production), exit
+**3** (it cannot tell), or any other non-zero code — **stop. Do not merge.** Hand the merge to the
+owner with the PR link. Show the gate's output and end the command. This holds whatever confirmation
+was given: `--yes`, a confirm flag, "just merge it" or an earlier approval cannot bypass it.
+
 ## Step 1 — Refuse unless green + mergeable + reviewed
 
 All of, per the repo's own rules:
@@ -94,6 +108,7 @@ Cleanup:       remote branch ✗ deleted / local ✗ deleted / backup ref droppe
 
 ## Rules
 - Never merge without: green required checks **and** the explicit human deploy-confirm.
+- Never merge unless `deploy-boundary` exited 0 on this run. No confirmation overrides it.
 - Never delete a branch before its deploy is validated green.
 - Never `git add -A` without reviewing `git status`; never edit a workflow file to make a gate pass.
 - Local-only lane: no PR, no merge — refuse and point at `/ship`.

package/bundles/antigravity-plugin/skills/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/antigravity-plugin/skills/sql/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sql
-description: Write high-quality, optimized SQL with best practices for performance, NULL handling, security, and readability. Database-agnostic patterns with dialect-specific notes.
+description: "Write optimized, secure, readable SQL: performance, NULL handling, dialect-specific notes."
 ---
 
 # SQL Expert Skill

package/bundles/antigravity-plugin/skills/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/antigravity-plugin/skills/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/antigravity-plugin/skills/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/antigravity-plugin/skills/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/antigravity-plugin/skills/using-git-worktrees/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-git-worktrees
-description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
+description: "Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan: creates an isolated git worktree safely."
 ---
 
 # Using Git Worktrees

package/bundles/antigravity-plugin/skills/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/antigravity-plugin/skills/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/antigravity-plugin/skills/windows-deployment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: windows-deployment
-description: "Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, reverse proxy (IIS or nginx), and git-pull workflow. Use when deploying any web app to a Windows prod server, setting up NSSM services, configuring IIS or nginx reverse proxy, making code environment-aware for dev/prod, or troubleshooting prod deployment issues."
+description: "Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, IIS or nginx reverse proxy and git-pull. Use for Windows prod deploys, NSSM, reverse proxy setup, dev/prod config, or prod troubleshooting."
 ---
 
 # Windows Server Deployment Skill

package/bundles/antigravity-plugin/warm_start_agy.py

@@ -91,38 +91,97 @@ def _first_existing(paths: list[str]) -> str:
     return ""
 
 
-def _branch_slug(root: str) -> str:
-    """Filesystem-safe current branch name, or "" when it can't be determined (best-effort)."""
+def scan_relays(root: str) -> list[tuple[str, dict]]:
+    results: list[tuple[str, dict]] = []
+    try:
+        from caddis_frontmatter import parse
+    except Exception:
+        _here = os.path.dirname(os.path.abspath(__file__))
+        for p in (
+            # Source tree: caddis_frontmatter.py is authored in claude-harness/scripts/.
+            os.path.join(os.path.dirname(_here), "scripts"),
+            # agy plugin: this file sits at the plugin root; scripts are in <plugin>/scripts/.
+            os.path.join(_here, "scripts"),
+            # Source tree, top-level scripts/ (harmless if the module is not there).
+            os.path.join(os.path.dirname(os.path.dirname(_here)), "scripts"),
+        ):
+            if os.path.isdir(p) and p not in sys.path:
+                sys.path.insert(0, p)
+        try:
+            from caddis_frontmatter import parse
+        except Exception:
+            def parse(t): return {}
+
+    for d in _ARTIFACT_DIRS:
+        relay_dir = os.path.join(root, d, "relay")
+        if not os.path.isdir(relay_dir):
+            continue
+        try:
+            entries = list(os.scandir(relay_dir))  # exhausting it closes the handle
+        except OSError:
+            continue
+        for entry in entries:
+            if entry.is_file() and entry.name.endswith(".md"):
+                try:
+                    with open(entry.path, encoding="utf-8", errors="ignore") as handle:
+                        text = handle.read()
+                    meta = parse(text)
+                    results.append((entry.path, meta))
+                except Exception:
+                    continue
+    return results
+
+
+def resolve_relay(root: str, session_id: str = "") -> tuple[str, str | None]:
+    """First existing relay doc for `root` and matched workstream name, else ("", None).
+
+    1. Session ID match takes precedence (matching meta['session_id'] with session_id).
+    2. Otherwise, if current branch is non-default, match relays by branch/workstream name.
+       If exactly 1 match: inject full relay.
+    3. If default branch or multiple/no matches: inject index (.caddis/relay.md).
+    """
+    relays = scan_relays(root)
+
+    # 1. Session ID match takes precedence
+    if session_id:
+        for path, meta in relays:
+            if meta.get("session_id") and str(meta.get("session_id")) == str(session_id):
+                ws = meta.get("workstream") or os.path.splitext(os.path.basename(path))[0]
+                return path, ws
+
+    # 2. Branch lookup (best-effort)
     try:
         branch = subprocess.run(
             ["git", "-C", root, "rev-parse", "--abbrev-ref", "HEAD"],
             capture_output=True, text=True, timeout=3,
         ).stdout.strip()
     except Exception:
-        return ""
-    if not branch or branch == "HEAD":
-        return ""
-    return "".join(c if (c.isalnum() or c in "-_.") else "-" for c in branch)
-
-
-def resolve_relay(root: str) -> str:
-    """First existing relay doc for `root`, else "".
-
-    Preference order mirrors inject_relay.py:
-      1. .caddis/relay/<branch>.md          (per-branch team mode)
-      2. .caddis/relay.md                   (solo/default)
-      3. .claude/relay/<branch>.md          (legacy per-branch)
-      4. relay.md                           (legacy repo root)
-    """
-    slug = _branch_slug(root)
-    candidates: list[str] = []
-    if slug:
-        candidates += [os.path.join(root, d, "relay", f"{slug}.md") for d in _ARTIFACT_DIRS]
-    candidates += [os.path.join(root, d, "relay.md") for d in _ARTIFACT_DIRS]
-    if slug:
-        candidates.append(os.path.join(root, ".claude", "relay", f"{slug}.md"))
-    candidates.append(os.path.join(root, "relay.md"))
-    return _first_existing(candidates)
+        branch = ""
+
+    default_branches = {"main", "master", "trunk", "develop", "HEAD", ""}
+    slug = ""  # set below for a non-default branch; also read by the legacy fallback
+    if branch and branch not in default_branches:
+        slug = "".join(c if (c.isalnum() or c in "-_.") else "-" for c in branch)
+        matched = []
+        for path, meta in relays:
+            ws = meta.get("workstream")
+            b = meta.get("branch")
+            stem = os.path.splitext(os.path.basename(path))[0]
+            if (b and b in (branch, slug)) or (ws and ws in (branch, slug)) or stem in (branch, slug):
+                matched.append((path, ws or stem))
+        if len(matched) == 1:
+            return matched[0]
+
+    # 3. Fallback: index (.caddis/relay.md) or legacy files
+    # Index, then the legacy per-branch .claude/relay/<branch>.md, then a root relay.md --
+    # the order used before workstream relays existed.
+    legacy_branch = []
+    if branch and branch not in default_branches:
+        legacy_branch = [os.path.join(root, ".claude", "relay", f"{slug}.md")]
+    candidates = ([os.path.join(root, d, "relay.md") for d in _ARTIFACT_DIRS] + legacy_branch
+                  + [os.path.join(root, "relay.md")])
+    idx_path = _first_existing(candidates)
+    return idx_path, None
 
 
 def truncate_relay(text: str) -> str:
@@ -270,25 +329,60 @@ def main() -> None:
         conversation = str(data.get("conversationId") or "").strip()
 
         blocks = []
+        open_work_blocks = []
         for root in roots:
-            relay = resolve_relay(root)
-            if not relay:
+            if conversation and _already_injected(root, conversation):
                 continue
+            relay, matched_ws = resolve_relay(root, conversation)
+            text = ""
+            if relay:
+                try:
+                    with open(relay, encoding="utf-8") as handle:
+                        text = handle.read().strip()
+                except Exception as _exc:
+                    _hook_note("agy relay read", _exc, root)
+            if text:
+                # Label the block ONLY when there is more than one root. A single-root session
+                # must produce byte-identical output to before this change.
+                if len(roots) > 1:
+                    blocks.append("relay for " + os.path.basename(root.rstrip("/\\")) + ":")
+                blocks.append(truncate_relay(text))
+
+            # Open-work rows as plain text without seeding instruction. Shown with or without a
+            # relay: to-dos and plan phases exist before the first handoff writes one.
+            shown_open_work = False
             try:
-                text = open(relay, encoding="utf-8").read().strip()
+                from pathlib import Path as _Path
+                # agy plugin: warm_start_agy.py sits at the plugin root, scripts in <plugin>/scripts.
+                # Source tree: claude-harness/agy -> <repo>/scripts, where caddis_todo.py is authored.
+                _here = os.path.dirname(os.path.abspath(__file__))
+                for _sc in (os.path.join(os.path.dirname(os.path.dirname(_here)), "scripts"),
+                            os.path.join(_here, "scripts")):
+                    if os.path.isdir(_sc) and _sc not in sys.path:
+                        sys.path.insert(0, _sc)
+                import caddis_todo
+                open_items = caddis_todo.open_work(_Path(root), matched_ws)
+                if open_items:
+                    # Same budget as the Claude Code hook: next 5 phases, 5 ad-hoc items.
+                    phases = [r for r in open_items if r.get("kind") == "phase"][:5]
+                    todos = [r for r in open_items if r.get("kind") != "phase"][:5]
+                    shown = phases + todos
+                    ow_lines = ["## Open work"]
+                    if len(open_items) > len(shown):
+                        ow_lines.append(f"(+{len(open_items) - len(shown)} more open items — run /catchup to see them.)")
+                    for row in shown:
+                        ow_lines.append(f"- {row['id']} [{row['kind']}] {' '.join(str(row['title']).split())[:100]}")
+                    if len(roots) > 1:
+                        open_work_blocks.append("open work for " + os.path.basename(root.rstrip("/\\")) + ":\n" + "\n".join(ow_lines))
+                    else:
+                        open_work_blocks.append("\n".join(ow_lines))
+                    shown_open_work = True
             except Exception as _exc:
-                _hook_note("agy relay read", _exc, root)
-                continue
-            if not text:
-                continue
-            if conversation and _already_injected(root, conversation):
-                continue
-            # Label the block ONLY when there is more than one root. A single-root session
-            # must produce byte-identical output to before this change.
-            if len(roots) > 1:
-                blocks.append("relay for " + os.path.basename(root.rstrip("/\\")) + ":")
-            blocks.append(truncate_relay(text))
-            if conversation:
+                _hook_note("agy open work injection", _exc, root)
+
+            # A relay that exists but failed to read must not be marked injected just because
+            # open work was shown: the next invocation retries the relay.
+            if conversation and (text or (not relay and shown_open_work)):
                 _mark_injected(root, conversation)
 
         # agy has no SessionStart event, so this first invocation is also where the freshness
@@ -298,12 +392,14 @@ def main() -> None:
         for root in roots:
             fresh.extend(freshness_lines(root))
 
-        if not blocks and not fresh:
+        if not blocks and not fresh and not open_work_blocks:
             return
         parts = []
         if blocks:
             parts.append(RELAY_FRAME_HEADER + "\n" + "\n\n".join(blocks)
                          + "\n\n" + RELAY_FRAME_FOOTER)
+        if open_work_blocks:
+            parts.append("\n\n".join(open_work_blocks))
         if fresh:
             parts.append("\n".join(fresh))
         payload = json.dumps({"injectSteps": [{"ephemeralMessage": "\n\n".join(parts)}]})

package/bundles/antigravity-plugin-extras/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "caddis-extras",
-  "version": "1.3.39",
+  "version": "1.3.40",
   "description": "caddis-extras — the long-tail skills for the Antigravity (agy) caddis plugin; install alongside caddis for the full set."
 }