@rse/ase 0.9.11 → 0.9.13

package/plugin/meta/ase-skill.md

@@ -119,15 +119,25 @@ Skill Sequential Processing
     For speed, emit *all* `TaskCreate` calls together in a *single* turn
     (issued in parallel), *not* one-per-turn sequentially. Do *not*
     rely on the call order to establish the step order, as the parallel
-    results carry no guaranteed ordering. Instead, in the *immediately
-    following* turn, establish the strict order explicitly by chaining
-    the created tasks with `TaskUpdate`: for each <step/> after the
-    first one, call `TaskUpdate({ taskId: "<this/>", addBlockedBy:
-    [ "<prev/>" ] })` so that every step (with `taskId` <this/>) is
-    blocked by its predecessor step (with `taskId` <prev/>).
+    results carry no guaranteed ordering.
+
+    Instead, in the *immediately single following* turn, first
+    reconstruct the step-id-to-taskId mapping: because each task's
+    `subject` equals the originating <step/> `id` (and <step/> ids are
+    unique), match every created task back to its <step/> by comparing
+    the task's `subject` to the step `id` -- read the ids straight from
+    the `TaskCreate` results, or call `TaskList` if the results are
+    no longer at hand.
+
+    Then establish the strict order explicitly by chaining the created
+    tasks with `TaskUpdate`: for each <step/> after the first one,
+    resolve <this/> and <prev/> to the mapped `taskId` values and
+    call `TaskUpdate({ taskId: "<this/>", addBlockedBy: [ "<prev/>" ]
+    })` so that every step (with `taskId` <this/>) is blocked by its
+    predecessor step (with `taskId` <prev/>).
 
 -   *IMPORTANT*: For each <step/> you *MUST* use the `TaskUpdate` tool
-    for updating its status during processing.
+    for updating its status *during* processing, once a <step/> finished.
 
 -   *IMPORTANT*: You *MUST* sequentially execute every <step/> in
     a <flow/> *EXACTLY* as the instructions specify.
@@ -172,6 +182,12 @@ MCP Tool Calls
         ⧉ **ASE**: **ERROR:** MCP tool failed: <info/>
         </template>
 
+        *EXCEPTION*: this rule does *NOT* apply to the `ase_getopt` tool,
+        whose `ERROR:`-prefixed output is *expected* option-parsing
+        feedback handled exclusively by step 4 of the `getopt` procedure
+        (see `ase-getopt.md`); never emit this generic template for an
+        `ase_getopt` response.
+
     -   Only on a clean response: proceed as the skill instructs.
 
 Skill Identification
@@ -232,9 +248,11 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <title-len/> is the number of characters in the string
-    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
-    (67 - <title-len/>) times):
+    (where <raw-title/> is the visible un-styled text `⧉ ASE: <title/>`,
+    <raw-title-len/> is the number of characters in <raw-title/>, and
+    <bar/> is the `─` character repeated exactly (67 - <raw-title-len/>)
+    times -- the very same bar-width rule as `<ase-tpl-foot/>` and
+    `<ase-tpl-boxed/>`, so equal visible text yields equal total width):
 
     <template>
 
@@ -251,9 +269,11 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <title-len/> is the number of characters in the string
-    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
-    (67 - <title-len/>) times):
+    (where <raw-title/> is the visible un-styled text `⧉ ASE: <title/>`,
+    <raw-title-len/> is the number of characters in <raw-title/>, and
+    <bar/> is the `─` character repeated exactly (67 - <raw-title-len/>)
+    times -- the very same bar-width rule as `<ase-tpl-head/>` and
+    `<ase-tpl-boxed/>`, so equal visible text yields equal total width):
 
     <template>
 
@@ -275,19 +295,23 @@ Template Patterns
     </else>
 
 -   When `<ase-tpl-boxed title="<title/>"[ subtitle="<subtitle/>"]><content/></ase-tpl-boxed>`
-    should be expanded use the following helper placeholder and then the <template/>:
+    should be expanded use the following helper placeholders and then
+    the following <template/>:
 
     -   <if condition="<subtitle/> is not empty">
-            Set <raw-title>⧉ ASE: <title/>: <subtitle/><raw-title>.
+            Set <raw-title>⧉ ASE: <title/>: <subtitle/></raw-title>.
             Set <render-title>⧉ ASE: **`<title/>`**: `<subtitle/>`</render-title>.
         </if>
         <else>
-            Set <raw-title>⧉ ASE: <title/><raw-title>.
+            Set <raw-title>⧉ ASE: <title/></raw-title>.
             Set <render-title>⧉ ASE: **`<title/>`**</render-title>.
         </else>
-    -   Set <raw-title-len/> to the number of characters in <raw-title/>.
-    -   Set <bar/> to the `─` character repeated exactly (67 - <raw-title-len/>) times.
-    -   Set <body> to <content/> with all line-starts prefixed with `│ `.
+    -   Set <raw-title-len/> to the number of characters in the visible
+        un-styled text <raw-title/>.
+    -   Set <bar/> to the `─` character repeated exactly (67 - <raw-title-len/>)
+        times -- the very same bar-width rule as `<ase-tpl-head/>` and
+        `<ase-tpl-foot/>`, so equal visible text yields equal total width.
+    -   Set <body/> to <content/> with all line-starts prefixed with `│ `.
 
     <template>
 

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.11",
+    "version":                              "0.9.13",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/skills/ase-arch-analyze/SKILL.md

@@ -375,13 +375,19 @@ interface quality, quality attributes, and architecture governance.
     - *Focal aspect*: <focal-aspect/> - <focal-state/>
     - *In tension with*: <partner-list/>
 
-    **RECOMMENDED**: lean toward *<focal|partners/>*
+    **RECOMMENDED**: lean toward *<lean-toward/>*
     *Reason*: <rationale/>
     *Implies*:
-    - <partner-aspect-1/>: <partner-implication-1/>
-    - <partner-aspect-2/>: <partner-implication-2/>
+    - <partner-aspect/>: <partner-implication/>
+    - ...
     </template>
 
+    For each partner in <partner-list/>, repeat the `*Implies*` line,
+    set <partner-aspect/> to the partner aspect, and set
+    <partner-implication/> to its brief implication. Set <lean-toward/>
+    to the aspect direction the recommendation favors (the *focal
+    aspect* or the *partners*).
+
     Hints:
 
     - For the final results, do *not* output anything else,
@@ -429,13 +435,14 @@ interface quality, quality attributes, and architecture governance.
       for the same aspect, and never emit both halves of a
       tension pair as separate PROBLEMs.
 
-    - *Additionally*, first call the `ase_kv_clear()` tool of the `ase`
-      MCP server to clear the in-memory key/value store, and then,
-      for *every* reported PROBLEM and TRADEOFF, persist its finding
-      result via the `ase_kv_set` tool of the `ase` MCP server, using
-      `key` set to `ase-issue-P<n/>` (for PROBLEMs) or
-      `ase-issue-T<n/>` (for TRADEOFFs) and `val` set to
-      `<title/>: <description/>`.
+    - *Additionally*, persist all reported findings in a *single*
+      `ase_kv_batch` call to the `ase` MCP server with `transactional`
+      set to `true`. The `commands` parameter array of this call
+      starts with one `{ command: "clear" }` entry, followed by one
+      `{ command: "set", key: "ase-issue-P<n/>", val: "<title/>:
+      <description/>" }` entry per reported PROBLEM and one
+      `{ command: "set", key: "ase-issue-T<n/>", val: "<title/>:
+      <description/>" }` entry per reported TRADEOFF.
     </step>
 
 4.  <step id="STEP 4: Give Final Hint">

package/plugin/skills/ase-code-craft/SKILL.md

@@ -249,7 +249,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -319,7 +319,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         as <head/> (or `none` if the list is `none`/empty).
         Set <args>--int-reuse-task</args>.
 
-        1.  <if condition="<head/> is equal `IMPLEMENT`">
+        1.  <if condition="<head/> is equal `DONE`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `DONE`
+            means the freshly composed plan is finalized as-is, so do
+            *not* hand off to `ase-task-edit`. Only output the following
+            <template/> and then *STOP*. Do *not* implement the plan.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- done**
+            </template>
+            </if>
+
+        2.  <elseif condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -327,9 +339,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             </if>
             Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
+        3.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -339,7 +351,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        3.  <else>
+        4.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

package/plugin/skills/ase-code-explain/SKILL.md

@@ -8,7 +8,6 @@ user-invocable: true
 disable-model-invocation: false
 effort: high
 allowed-tools:
-    - "Skill"
     - "Agent"
 ---
 

package/plugin/skills/ase-code-insight/SKILL.md

@@ -12,7 +12,7 @@ allowed-tools:
     - "Bash(sort *)"
     - "Bash(uniq *)"
     - "Bash(head *)"
-    - "Skill"
+    - "Bash(git log * | grep * | sort * | uniq * | sort * | head *)"
     - "Agent"
 ---
 

package/plugin/skills/ase-code-lint/SKILL.md

@@ -143,13 +143,24 @@ related to a set of code quality aspects.
                     Set <new-text/>       to the `new_text`       field of <item/>.
                     Set <context-after/>  to the `context_after`  field of <item/>.
 
-                2.  If <context/> is not empty, set
+                2.  Set <old-start/> to the line of the first hunk line, i.e.,
+                    the line of <context-before/> (one before <line/>).
+                    Set <new-start/> to the same as <old-start/> (the unchanged
+                    <context-before/> line shares the same start in both files).
+                    Set <old-count/> to the total number of old-side hunk lines, i.e.,
+                    the number of lines in <context-before/>, <old-text/>, and
+                    <context-after/> combined.
+                    Set <new-count/> to the total number of new-side hunk lines, i.e.,
+                    the number of lines in <context-before/>, <new-text/>, and
+                    <context-after/> combined.
+
+                3.  If <context/> is not empty, set
                     <context><context/>,</context> (append a comma).
                     Then append the following <template/> to <context/>:
 
                     <template>`<file/>`:<line/></template>
 
-                3.  Append the following <template/> to <diff-file/>:
+                4.  Append the following <template/> to <diff-file/>:
 
                     <template>
                     @@ -<old-start/>,<old-count/> +<new-start/>,<new-count/> @@
@@ -159,18 +170,6 @@ related to a set of code quality aspects.
                      <context-after/>
                     </template>
 
-                    Hints:
-                    -   The <old-start/> is the line of the first hunk line, i.e.,
-                        the line of <context-before/> (one before <line/>).
-                    -   The <new-start/> is the same as <old-start/> (the unchanged
-                        <context-before/> line shares the same start in both files).
-                    -   The <old-count/> is the total number of old-side hunk lines, i.e.,
-                        the number of lines in <context-before/>, <old-text/>, and
-                        <context-after/> combined.
-                    -   The <new-count/> is the total number of new-side hunk lines, i.e.,
-                        the number of lines in <context-before/>, <new-text/>, and
-                        <context-after/> combined.
-
                 </for>
 
             3.  Append <diff-file/> to <diff/>.

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -238,7 +238,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -308,7 +308,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         as <head/> (or `none` if the list is `none`/empty).
         Set <args>--int-reuse-task</args>.
 
-        1.  <if condition="<head/> is equal `IMPLEMENT`">
+        1.  <if condition="<head/> is equal `DONE`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `DONE`
+            means the freshly composed plan is finalized as-is, so do
+            *not* hand off to `ase-task-edit`. Only output the following
+            <template/> and then *STOP*. Do *not* implement the plan.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- done**
+            </template>
+            </if>
+
+        2.  <elseif condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -316,9 +328,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             </if>
             Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
+        3.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -328,7 +340,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        3.  <else>
+        4.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -71,6 +71,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <problem-id/> and stop processing.
 
     2.  <if condition="
+            <problem-id/> is not set AND
             <problem/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
         ">
         Set <ase-task-id><problem/></ase-task-id> (set task id to problem)
@@ -289,7 +290,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -366,7 +367,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         as <head/> (or `none` if the list is `none`/empty).
         Set <args>--int-reuse-task</args>.
 
-        1.  <if condition="<head/> is equal `IMPLEMENT`">
+        1.  <if condition="<head/> is equal `DONE`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `DONE`
+            means the freshly composed plan is finalized as-is, so do
+            *not* hand off to `ase-task-edit`. Only output the following
+            <template/> and then *STOP*. Do *not* implement the plan.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- done**
+            </template>
+            </if>
+
+        2.  <elseif condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -374,9 +387,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             </if>
             Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
+        3.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
             tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
@@ -386,7 +399,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        3.  <else>
+        4.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

package/plugin/skills/ase-docs-proofread/SKILL.md

@@ -119,6 +119,17 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         3.  <if condition="<getopt-option-auto/> is not 'true'">
 
+            Set <old-start/> to the line of the first hunk line, i.e.,
+            the line of <context-before/> (one before <line/>).
+            Set <new-start/> to the same as <old-start/> (the unchanged
+            <context-before/> line shares the same start in both files).
+            Set <old-count/> to the total number of old-side hunk lines, i.e.,
+            the number of lines in <context-before/>, <old-text/>, and
+            <context-after/> combined.
+            Set <new-count/> to the total number of new-side hunk lines, i.e.,
+            the number of lines in <context-before/>, <new-text/>, and
+            <context-after/> combined.
+
             Render the proposed correction as a *unified diff* with *up to
             two* lines of context in a fenced block based on the following <template/>:
 
@@ -138,18 +149,6 @@ Analyze documents for spelling, punctuation, or grammar errors
 
             </template>
 
-            Hints:
-            -   The <old-start/> is the line of the first hunk line, i.e.,
-                the line of <context-before/> (one before <line/>).
-            -   The <new-start/> is the same as <old-start/> (the unchanged
-                <context-before/> line shares the same start in both files).
-            -   The <old-count/> is the total number of old-side hunk lines, i.e.,
-                the number of lines in <context-before/>, <old-text/>, and
-                <context-after/> combined.
-            -   The <new-count/> is the total number of new-side hunk lines, i.e.,
-                the number of lines in <context-before/>, <new-text/>, and
-                <context-after/> combined.
-
             </if>
 
         4.  <if condition="<getopt-option-auto/> is not 'true'">