@caddis/cli 0.4.15 → 0.4.16

package/bundles/antigravity-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "caddis",
-  "version": "1.3.108",
+  "version": "1.3.109",
   "description": "caddis — agent-agnostic dev harness as an Antigravity (agy) plugin: TDD skills + commands, single-sourced with the Claude Code plugin."
 }

package/bundles/antigravity-plugin/skills/confluence-hla/SKILL.md

@@ -89,6 +89,12 @@ When authoring an HLA, strictly adhere to the following 7-section structure:
    [Note: 7.2 References is kept in working Markdown but STRICTLY OMITTED from Confluence HTML]
 ```
 
+### Key Section Authoring Guidelines:
+- **Section 3.1 Operational Process Flow:** Document the flow using clean, continuous numbered text steps (`1. **Step Name:** ...`). Completely omit ASCII, unicode, or plain-text drawing boxes, which break formatting in Confluence. The accompanying sequence diagram in 3.2 provides the visual workflow.
+- **Section 3.2 End-to-End Sequence Diagram:** Autonumber all interactions. Apply corporate palette classes (`clientStyle`, `serverStyle`, `appStyle`, `dataStyle`, `extStyle`). Wrap all participant names, notes, and message labels under 45 characters using `<br/>`.
+- **Section 4.1 Solution Design and Architecture:** The standardized title is `4.1 Solution Design and Architecture` (do NOT use "System Topology and Network Boundaries"). Provides the compact component topology and network boundary diagram.
+- **Tables:** All tables must be authored cleanly and converted into `<table class="wrapped">` with wrapped headers (`<th><p>Header</p></th>`) and wrapped table cells (`<td><p>Value</p></td>`).
+
 ---
 
 ## 3. High-Level Database and Data Processing Pipeline Discovery
@@ -272,7 +278,7 @@ Never use default bright or garish PlantUML colors. Use muted corporate Material
      - **Stage 2 (Middle):** Language Model Synthesis Engine (`LLMEngine`), receiving 90-degree orthogonal connections from each track's summary node (`NSum -right-> LLMEngine`, etc.).
      - **Stage 3 (Right):** Action Recommendation & Justification (`RecOutput`), receiving a horizontal connection from `LLMEngine`.
 
-4. **Component-to-Component Connections in System Topology:**
+4. **Component-to-Component Connections in Solution Design & Architecture:**
    - Connect internal component nodes directly (e.g., `Worker -down-> SQL`, `Worker -down-> Apigee`, `Worker -right-> LLM`).
    - Do NOT connect package boundaries (e.g., `HostLayer -down-> MidLayer`), which inflates diagram bounding boxes and distorts routing.
    - Use `skinparam nodesep 60` and `skinparam ranksep 50` for comfortable whitespace.
@@ -337,7 +343,7 @@ Inspect the target codebase across five dimensions:
 - Write using the 7-section canonical structure in Simplified Technical English.
 - Author PlantUML (or Mermaid) diagram blocks for:
   1. Sequence diagram
-  2. System topology diagram
+  2. Solution Design and Architecture diagram (compact topology)
   3. Multi-track summarization pipeline
   4. End-to-end database and processing pipeline (Section 4.5)
 - Document the Screener Feedback Service and RLHF loop (Section 4.6).

package/bundles/antigravity-plugin/skills/confluence-hla/scripts/convert_hla_to_confluence.py

@@ -180,7 +180,13 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
     subgraph_start_re = re.compile(r'^\s*subgraph\s+([A-Za-z0-9_]+)(?:\["([^"]+)"\]|\[([^\]]+)\])?', re.IGNORECASE)
     direction_re = re.compile(r'^\s*direction\s+(LR|RL|TB|TD)', re.IGNORECASE)
-    node_def_re = re.compile(r'([A-Za-z0-9_]+)\["([^"]+)"\](?::::([A-Za-z0-9_]+))?|([A-Za-z0-9_]+)\[([^\]]+)\](?::::([A-Za-z0-9_]+))?')
+    node_def_re = re.compile(
+        r'([A-Za-z0-9_]+)(?:'
+        r'\["([^"]+)"\]|\[([^\]]+)\]|'
+        r'\{"([^"]+)"\}|\{([^\}]+)\}|'
+        r'\("([^"]+)"\)|\(([^\)]+)\)'
+        r')(?::::([A-Za-z0-9_]+))?'
+    )
 
     has_flowchart = False
     for line in lines:
@@ -222,9 +228,9 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
         # 1. Extract node definitions
         for match in node_def_re.finditer(stripped):
-            n_id = match.group(1) or match.group(4)
-            n_lbl = match.group(2) or match.group(5)
-            n_cls = match.group(3) or match.group(6) or ""
+            n_id = match.group(1)
+            n_lbl = next(g for g in match.groups()[1:7] if g is not None)
+            n_cls = match.group(8) or ""
             node_info = {"id": n_id, "label": n_lbl, "class": n_cls}
             if sg_stack:
                 sg_stack[-1]["nodes"][n_id] = node_info
@@ -233,7 +239,7 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
         # 2. Clean line for edge extraction
         def repl_node(m):
-            return m.group(1) or m.group(4)
+            return m.group(1)
         clean_edge_line = node_def_re.sub(repl_node, stripped)
 
         # 3. Extract edges

package/bundles/codex/.codex/skills/docs/confluence-hla/SKILL.md

@@ -89,6 +89,12 @@ When authoring an HLA, strictly adhere to the following 7-section structure:
    [Note: 7.2 References is kept in working Markdown but STRICTLY OMITTED from Confluence HTML]
 ```
 
+### Key Section Authoring Guidelines:
+- **Section 3.1 Operational Process Flow:** Document the flow using clean, continuous numbered text steps (`1. **Step Name:** ...`). Completely omit ASCII, unicode, or plain-text drawing boxes, which break formatting in Confluence. The accompanying sequence diagram in 3.2 provides the visual workflow.
+- **Section 3.2 End-to-End Sequence Diagram:** Autonumber all interactions. Apply corporate palette classes (`clientStyle`, `serverStyle`, `appStyle`, `dataStyle`, `extStyle`). Wrap all participant names, notes, and message labels under 45 characters using `<br/>`.
+- **Section 4.1 Solution Design and Architecture:** The standardized title is `4.1 Solution Design and Architecture` (do NOT use "System Topology and Network Boundaries"). Provides the compact component topology and network boundary diagram.
+- **Tables:** All tables must be authored cleanly and converted into `<table class="wrapped">` with wrapped headers (`<th><p>Header</p></th>`) and wrapped table cells (`<td><p>Value</p></td>`).
+
 ---
 
 ## 3. High-Level Database and Data Processing Pipeline Discovery
@@ -272,7 +278,7 @@ Never use default bright or garish PlantUML colors. Use muted corporate Material
      - **Stage 2 (Middle):** Language Model Synthesis Engine (`LLMEngine`), receiving 90-degree orthogonal connections from each track's summary node (`NSum -right-> LLMEngine`, etc.).
      - **Stage 3 (Right):** Action Recommendation & Justification (`RecOutput`), receiving a horizontal connection from `LLMEngine`.
 
-4. **Component-to-Component Connections in System Topology:**
+4. **Component-to-Component Connections in Solution Design & Architecture:**
    - Connect internal component nodes directly (e.g., `Worker -down-> SQL`, `Worker -down-> Apigee`, `Worker -right-> LLM`).
    - Do NOT connect package boundaries (e.g., `HostLayer -down-> MidLayer`), which inflates diagram bounding boxes and distorts routing.
    - Use `skinparam nodesep 60` and `skinparam ranksep 50` for comfortable whitespace.
@@ -337,7 +343,7 @@ Inspect the target codebase across five dimensions:
 - Write using the 7-section canonical structure in Simplified Technical English.
 - Author PlantUML (or Mermaid) diagram blocks for:
   1. Sequence diagram
-  2. System topology diagram
+  2. Solution Design and Architecture diagram (compact topology)
   3. Multi-track summarization pipeline
   4. End-to-end database and processing pipeline (Section 4.5)
 - Document the Screener Feedback Service and RLHF loop (Section 4.6).

package/bundles/codex/.codex/skills/docs/confluence-hla/scripts/convert_hla_to_confluence.py

@@ -180,7 +180,13 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
     subgraph_start_re = re.compile(r'^\s*subgraph\s+([A-Za-z0-9_]+)(?:\["([^"]+)"\]|\[([^\]]+)\])?', re.IGNORECASE)
     direction_re = re.compile(r'^\s*direction\s+(LR|RL|TB|TD)', re.IGNORECASE)
-    node_def_re = re.compile(r'([A-Za-z0-9_]+)\["([^"]+)"\](?::::([A-Za-z0-9_]+))?|([A-Za-z0-9_]+)\[([^\]]+)\](?::::([A-Za-z0-9_]+))?')
+    node_def_re = re.compile(
+        r'([A-Za-z0-9_]+)(?:'
+        r'\["([^"]+)"\]|\[([^\]]+)\]|'
+        r'\{"([^"]+)"\}|\{([^\}]+)\}|'
+        r'\("([^"]+)"\)|\(([^\)]+)\)'
+        r')(?::::([A-Za-z0-9_]+))?'
+    )
 
     has_flowchart = False
     for line in lines:
@@ -222,9 +228,9 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
         # 1. Extract node definitions
         for match in node_def_re.finditer(stripped):
-            n_id = match.group(1) or match.group(4)
-            n_lbl = match.group(2) or match.group(5)
-            n_cls = match.group(3) or match.group(6) or ""
+            n_id = match.group(1)
+            n_lbl = next(g for g in match.groups()[1:7] if g is not None)
+            n_cls = match.group(8) or ""
             node_info = {"id": n_id, "label": n_lbl, "class": n_cls}
             if sg_stack:
                 sg_stack[-1]["nodes"][n_id] = node_info
@@ -233,7 +239,7 @@ def _parse_mermaid_flowchart(code: str) -> Optional[str]:
 
         # 2. Clean line for edge extraction
         def repl_node(m):
-            return m.group(1) or m.group(4)
+            return m.group(1)
         clean_edge_line = node_def_re.sub(repl_node, stripped)
 
         # 3. Extract edges

package/bundles/manifest.json

@@ -1,7 +1,7 @@
 {
-  "poolVersion": "1.3.108",
+  "poolVersion": "1.3.109",
   "bundles": {
-    "antigravity-plugin": "1.3.108",
+    "antigravity-plugin": "1.3.109",
     "antigravity-plugin-extras": "1.3.29",
     "codex": "unknown"
   }

package/package.json

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