@rse/ase 0.9.12 → 0.9.13

package/dst/ase-compat.js

@@ -12,7 +12,7 @@ const EXPECTED = {
     "xml-placeholders/overwrite": "99",
     "xml-placeholders/indexed": "+1,-1",
     "xml-placeholders/nested-attr": "20",
-    "xml-placeholders/entity": "○",
+    "xml-placeholders/entity": "⦿",
     /*  control-flow  */
     "control-flow/branch": "mid",
     "control-flow/while-sum": "15",

package/dst/ase-diagram.js

@@ -117,12 +117,15 @@ export class Diagram {
     /*  detect terminal color capability  */
     static detectColorMode() {
         let mode = "none";
+        let explicit = false;
         /*  attempt 1: query environment variable (explicitly)  */
         if (process.env.ASE_TERM_COLORS !== undefined)
-            if (/^(?:none|ansi16|ansi256)$/.test(process.env.ASE_TERM_COLORS))
+            if (/^(?:none|ansi16|ansi256)$/.test(process.env.ASE_TERM_COLORS)) {
                 mode = process.env.ASE_TERM_COLORS;
+                explicit = true;
+            }
         /*  attempt 2: query stdout  */
-        if (mode === "none" && process.stdout.isTTY) {
+        if (!explicit && process.stdout.isTTY) {
             const depth = process.stdout.getColorDepth();
             if (depth >= 8)
                 mode = "ansi256";

package/dst/ase-getopt.js

@@ -108,7 +108,8 @@ export class GetoptMCP {
                 if (listOpts.length > 0) {
                     const opts = cmd.opts();
                     for (const { long, choices } of listOpts) {
-                        const v = opts[long];
+                        const key = long.replace(/-(.)/g, (_, c) => c.toUpperCase());
+                        const v = opts[key];
                         if (typeof v !== "string")
                             continue;
                         const items = v.split(",").map((s) => s.trim()).filter((s) => s.length > 0);

package/dst/ase-mcp.js

@@ -133,6 +133,8 @@ export default class MCPCommand {
         };
         /*  trigger a reconnect chain (idempotent while one is active)  */
         const triggerReconnect = (reason) => {
+            if (reconnecting)
+                return;
             reconnecting = true;
             this.log.write("warning", `mcp: ${reason} — reconnecting`);
             reconnect(0).catch(() => { });

package/dst/ase-persona.js

@@ -21,7 +21,10 @@ export class Persona {
         const val = cfg.get("agent.persona");
         if (val === undefined)
             return "engineer";
-        return String(isScalar(val) ? val.value : val);
+        const style = String(isScalar(val) ? val.value : val);
+        if (!Persona.styles.includes(style))
+            return "engineer";
+        return style;
     }
     /*  set the persona style on the strongest scope of an optional session  */
     static set(log, style, session) {

package/dst/ase-skills.js

@@ -263,10 +263,20 @@ export class Skills {
         const halfLife = 365 / 2;
         /*  lifespan requires both timestamps; recentness requires the
             updated timestamp -- any unavailable date-derived factor is
-            treated as neutral `1` so the entry can still be ranked by the
-            remaining metrics, instead of collapsing the product to zero  */
+            given a neutral default so the entry can still be ranked by the
+            remaining metrics, instead of collapsing the product to zero.
+            For `lifespan` (an unbounded duration) the multiplicative-neutral
+            `1` is also the low floor, so a missing value cannot unfairly
+            inflate the rank. For `recentness`, however, the value is an
+            exp-decay factor bounded in `(0,1]` where `1` is the *ceiling*
+            (a just-now update), not a floor -- defaulting a missing update
+            date to `1` would hand packages with absent metadata the highest
+            possible recentness and let them outrank genuinely fresh ones.
+            We therefore default a missing `recentness` to the decay value at
+            one half-life (`0.5`), a conservative midpoint that keeps the
+            entry rankable without rewarding the missing date.  */
         const lifespan = (!Number.isNaN(cMs) && !Number.isNaN(uMs)) ? Math.max(0, uMs - cMs) : 1;
-        const recentness = !Number.isNaN(uMs) ? Math.exp(-Math.max(0, (now - uMs) / msPerDay) / halfLife) : 1;
+        const recentness = !Number.isNaN(uMs) ? Math.exp(-Math.max(0, (now - uMs) / msPerDay) / halfLife) : 0.5;
         return d * s * lifespan * recentness;
     }
     /*  compute the per-alternative product-sum (rating) row from a

package/dst/ase-statusline.js

@@ -67,7 +67,7 @@ const formatTokens = (n) => {
     if (n >= 1_000_000)
         return `${(n / 1_000_000).toFixed(1)}M`;
     if (n >= 1_000)
-        return `${Math.round(n / 1_000)}k`;
+        return `${(n / 1_000).toFixed(1)}k`;
     return `${n}`;
 };
 /*  format a millisecond duration as a compact human-readable string (e.g. 6d 12hr 7m, 4hr 27m, 12m 30s)  */
@@ -362,7 +362,7 @@ export default class StatuslineCommand {
                     emit(`${prefix("◔", "context")}${bar} ${pct}%`);
                 },
                 C: () => {
-                    const pct = Math.floor(data.context_window?.used_percentage ?? 0);
+                    const pct = data.context_window?.used_percentage ?? 0;
                     const tokensCur = (data.context_window?.total_input_tokens ?? 0) +
                         (data.context_window?.total_output_tokens ?? 0);
                     const tokensLim = pct > 0 && tokensCur > 0 ? Math.round(tokensCur * 100 / pct) : 0;

package/dst/ase.js

@@ -18,7 +18,7 @@ import ArtifactCommand from "./ase-artifact.js";
 import CompatCommand from "./ase-compat.js";
 import pkg from "../package.json" with { type: "json" };
 /*  globally initialize logger  */
-const log = new Log("ase", "warning", "-");
+const log = new Log("ase", "info", "-");
 /*  main entry point (wrapped in a regular async function to avoid
     top-level await, which would be reported as "unsettled" by Node in
     the long-running daemon process spawned by "ase service start")  */

package/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.12",
+    "version":                              "0.9.13",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.12",
+    "version":     "0.9.13",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.12",
+    "version":     "0.9.13",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.12",
+    "version":     "0.9.13",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/meta/ase-dialog.md

@@ -185,7 +185,7 @@ following procedure:
 
     Do not output anything in this step!
 
-2.  Dispatch according to the agent tool:
+2.  Render the custom dialog, collect the user input, and dispatch on the result:
 
     1.  You *MUST* not output anything in this step.
 

package/plugin/meta/ase-format-arch.md

@@ -243,7 +243,7 @@ at runtime.
         for the component's existence and boundary.
 
     -   In case a component has no dependencies at all, the
-        entire `- Depends On:` bullet point is omitted.
+        entire `-   Depends On:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.
@@ -666,8 +666,16 @@ How the Non-Functional Requirements (NR) are addressed.
         perspective addresses, one of `Performance`, `Scalability`,
         `Reliability`, `Availability`, `Security`, `Privacy`,
         `Usability`, `Accessibility`, `Maintainability`, `Portability`,
-        `Compatibility`, or `Compliance` (aligned with the Non-Functional
-        Requirements categories).
+        `Compatibility`, or `Compliance`. This enumeration is a
+        solution-oriented refinement of the Non-Functional Requirements
+        (NR) categories and intentionally differs from them: the NR
+        categories follow the ISO/IEC 25010:2023 top-level characteristics
+        (and include `Safety` and `Flexibility`), whereas the perspective
+        qualities decompose some of these into the finer-grained,
+        architecturally actionable attributes `Scalability`,
+        `Availability`, `Privacy`, `Accessibility`, and `Portability`. A
+        perspective's quality therefore need not match the category of the
+        `SPEC-NR-<spec-nr-requirement-id/>` it addresses.
 
     -   <arch-qp-perspective-requirement/> is a
         `SPEC-NR-<spec-nr-requirement-id/>` reference to the corresponding
@@ -722,10 +730,11 @@ forces at play, the chosen response, and the reasoning that justifies it.
 
     ##  DECISION: <arch-dr-decision-name/> <a id="ARCH-DR-<arch-dr-decision-id/>"></a>
 
-    -   Status:    <arch-dr-decision-status/>
-    -   Affects:   <arch-dr-decision-element/>, [...]
-    -   Created:   <arch-dr-decision-created/>
-    -   Modified:  <arch-dr-decision-modified/>
+    -   Status:        <arch-dr-decision-status/>
+    -   Affects:       <arch-dr-decision-element/>, [...]
+    -   Superseded-By: <arch-dr-decision-superseded-by/>
+    -   Created:       <arch-dr-decision-created/>
+    -   Modified:      <arch-dr-decision-modified/>
 
     -   WHEN (Context):
         <arch-dr-decision-context/>
@@ -752,12 +761,17 @@ forces at play, the chosen response, and the reasoning that justifies it.
         <arch-dr-decision-decision/>, not longer than 80 characters.
 
     -   <arch-dr-decision-status/> is one of `proposed`, `accepted`,
-        `deprecated`, or `superseded by ARCH-DR-<arch-dr-decision-id/>`.
+        `deprecated`, or `superseded`.
 
     -   <arch-dr-decision-element/> is an `ARCH-FV-<arch-fv-component-id/>`
         or `ARCH-DP-<arch-dp-node-id/>` reference to the functional
         element or deployment node the decision affects.
 
+    -   <arch-dr-decision-superseded-by/> is an
+        `ARCH-DR-<arch-dr-decision-id/>` reference to the decision that
+        supersedes this decision. It is present if and only if the
+        <arch-dr-decision-status/> is `superseded`.
+
     -   <arch-dr-decision-created/> is the timestamp when this decision was
         created, and <arch-dr-decision-modified/> is the timestamp when
         this decision was last modified, both in the same ISO-style format
@@ -832,7 +846,10 @@ forces at play, the chosen response, and the reasoning that justifies it.
         job.
 
     -   In case the element reference is not present, the
-        entire `- Affects:` bullet point is omitted.
+        entire `-   Affects:` bullet point is omitted.
+
+    -   In case the <arch-dr-decision-status/> is not `superseded`, the
+        entire `-   Superseded-By:` bullet point is omitted.
 
     -   In case the `NOTES (Background)` content is not present, the
         entire `NOTES (Background)` chunk is omitted.

package/plugin/meta/ase-format-meta.md

@@ -29,9 +29,13 @@ Artifact Meta Information
 -   **Artifact**:
 
     At level 2, each **Artifact Set** is composed of many **Artifact**s.
-    Each **Artifact** has a unique identifier <artifact-id/>, which is
-    an upper-case, two-letter identifier (e.g. `CJ` for `Customer
-    Journey`) derived from the **Artifact** name.
+    Each **Artifact** has an identifier <artifact-id/>, which is an
+    upper-case, two-letter identifier (e.g. `CJ` for `Customer Journey`)
+    derived from the **Artifact** name. The <artifact-id/> is unique
+    only *within* its **Artifact Set**; the globally-unique handle of an
+    **Artifact** is the qualified form <artifact-set-id/>-<artifact-id/>
+    (e.g. `SPEC-DP` and `ARCH-DP` are distinct artifacts). All
+    references to an **Artifact** *MUST* use this qualified form.
 
     Each **Artifact** also has a sequence number <artifact-no/>, which
     is the zero-padded, two-digit position of the **Artifact** (starting

package/plugin/meta/ase-format-spec.md

@@ -871,8 +871,8 @@ for main, alternative, and exceptional paths.
 
     -   <spec-uc-usecase-description/>: a concise paragraph (1-3
         sentences) of prose describing the use case at a glance, without
-        prescribing the step-by-step flow (which belongs to the **Use
-        Case Scenarios** **Artifact**).
+        prescribing the step-by-step flow (which belongs to the
+        **SCENARIO** blocks of this use case).
 
     -   In case the use case realizes no specific functional requirement,
         the entire `- Requirements:` bullet point is omitted.
@@ -884,7 +884,7 @@ for main, alternative, and exceptional paths.
 
     <format>
 
-    ### SCENARIO: <spec-uc-usecase-scenario-name/> (<spec-uc-usecase-scenario-type/>)
+    ### SCENARIO: <spec-uc-usecase-scenario-name/> (<spec-uc-usecase-scenario-type/>) <a id="SPEC-UC-<spec-uc-usecase-id/>-<spec-uc-usecase-scenario-id/>"></a>
 
     1.  <spec-uc-usecase-scenario-step/>
     2.  <spec-uc-usecase-scenario-step/>
@@ -894,6 +894,11 @@ for main, alternative, and exceptional paths.
 
 -   <spec-uc-usecase-scenario/> details:
 
+    -   <spec-uc-usecase-scenario-id/>: per-use-case unique "slug" of
+        always 1-3 lower-cased words (concatenated with "-" characters
+        and in total not longer than 30 characters), derived from
+        <spec-uc-usecase-scenario-name/>.
+
     -   <spec-uc-usecase-scenario-name/>: a short (3-8 word) summary of the
         scenario.
 
@@ -1213,9 +1218,9 @@ turn.
         visualizes (optional).
 
     -   <spec-ds-storyboard-scenario/> is a
-        Use Case scenario type `<spec-uc-usecase-scenario-type/>` of
-        the corresponding **Aspect** of the Use Case **Artifact** the
-        storyboard visualizes (optional).
+        `SPEC-UC-<spec-uc-usecase-id/>-<spec-uc-usecase-scenario-id/>`
+        reference to the corresponding scenario **Aspect** of the Use
+        Case **Artifact** the storyboard visualizes (optional).
 
     -   <spec-ds-frame-name/>: a short (2-5 word) label for the screen,
         turn, or state depicted by the storyboard frame. Frames are

package/plugin/meta/ase-getopt.md

@@ -27,8 +27,8 @@ set placeholders into the context as a side-effect.
         `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
         <getopt-option-<long/>/> to <default/> (for `=<default/>`
         form), or to the *single token* <c1/> (the first choice, both
-        for the choice form `=(<c1/>|<c2>/|...)` and for the list form
-        `=(<c1/>|<c2>/|...)...` -- an *unsupplied* list-option always
+        for the choice form `=(<c1/>|<c2/>|...)` and for the list form
+        `=(<c1/>|<c2/>|...)...` -- an *unsupplied* list-option always
         defaults to the single token <c1/>, *not* to a whole list),
         or to `false` (for value-less options). Then set
         <getopt-arguments><getopt-args/></getopt-arguments>.
@@ -63,6 +63,10 @@ set placeholders into the context as a side-effect.
     validate each remaining token themselves as they consume it).
 
 4.  **Short-Circuit for Error**:
+    This step is the *sole* and *authoritative* handler for an
+    `ERROR:`-prefixed `ase_getopt` response; the generic MCP-Tool-Calls
+    error rule (see `ase-skill.md`) explicitly does *NOT* apply here, so
+    only the <template/> below is emitted (never both).
     If <text/> starts with `ERROR:`:
     Remove all `ERROR:` or `error:` prefixes from <text/>.
     Then only output the following <template/> and

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.12",
+    "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

@@ -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

@@ -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)
@@ -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'">

package/plugin/skills/ase-meta-compat/SKILL.md

@@ -71,7 +71,7 @@ Procedure
         `width="<w/>"` and read the attribute `width` back.
         Record actual result for `xml-placeholders/nested-attr`.
 
-    6.  *entity*: Evaluate the XML entity `&#x25CB;` and get the rendered
+    6.  *entity*: Evaluate the XML entity `&#x29BF;` and get the rendered
         Unicode character.
         Record actual result for `xml-placeholders/entity`.
 
@@ -152,8 +152,6 @@ Procedure
 
     Set <re-total/> to the number of regex probes above.
 
-    </step>
-
 5.  STEP 5: Probe Arithmetic
 
     Execute *all* of the following arithmetic probes (in the given
@@ -181,8 +179,6 @@ Procedure
 
     Set <arith-total/> to the number of arithmetic probes above.
 
-    </step>
-
 6.  STEP 6: Fetch Expected Values and Score
 
     Call the `ase_compat()` tool of the `ase` MCP server with an
@@ -209,8 +205,6 @@ Procedure
     -   Set <re-pass/>    to the number of `regex/*`            probes that passed.
     -   Set <arith-pass/> to the number of `arithmetic/*`       probes that passed.
 
-    </step>
-
 7.  STEP 7: Compute and Report Compatibility
 
     Compute each category's *pass-rate* (a value in 0.0…1.0) by dividing
@@ -269,9 +263,7 @@ Procedure
     4.  If <failures/> is not empty:
         Append to <verdict/> the suffix ` (failed: <failures/>)`.
 
-    Output the final compatibility report with the following <template/>:
-
-    <template>
+    Finally, output the compatibility report:
 
     **RESULTS**:
 
@@ -284,5 +276,3 @@ Procedure
     | **OVERALL**          |             |                              | **<overall-pct/>%** |
 
     **VERDICT**: <verdict/>
-
-    </template>

package/plugin/skills/ase-meta-diff/SKILL.md

@@ -274,9 +274,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         <ase-tpl-bullet-signal/> **CHANGE RISK REPORT**: Overall: **<band/>** (<aggregate/>/5)
 
-        | Axis        | Score      | Findings                                                    |
-        | ----------- | ---------- | ----------------------------------------------------------- |
-        | **<axis/>** | <score/>/5 | ● **EVIDENCE**: <evidence/> ● **MITIGATION**: <mitigation/> |
+        | Axis        | Score      | Findings                                                                                              |
+        | ----------- | ---------- | ----------------------------------------------------------------------------------------------------- |
+        | **<axis/>** | <score/>/5 | ● **EVIDENCE**: <evidence/><if condition="axis score is `>= 4`"> ● **MITIGATION**: <mitigation/></if> |
         </template>
     </step>
 

package/plugin/skills/ase-meta-evaluate/SKILL.md

@@ -81,15 +81,17 @@ multi-*criteria* decision matrix.
     -   For each alternative <alternative-K/> (K=1-N), decide whether
         it is a genuine member of <class-of-alternatives/>. If any
         <alternative-K/> is *not* a member (i.e. the alternatives are not
-        mutually comparable within a single class), let <alternative-J/>
-        (J=1-P, P<=N) be the subset of non-member alternatives, output the
-        following <template/> and *stop the entire flow* immediately without
-        executing any further steps:
+        mutually comparable within a single class), collect the subset
+        of non-member alternatives into the space-separated list
+        <non-members/> (the <alternative-K/> for which the membership
+        decision was negative), output the following <template/> and
+        *stop the entire flow* immediately without executing any further
+        steps:
 
         <template>
         <ase-tpl-bullet-signal/> **ERROR: INCOMPARABLE ALTERNATIVES**: *<class-of-alternatives/>*
 
-        <for items="<alternative-J/> [...]">
+        <for items="<non-members/>">
         ⚑ **<item/>** (*member of a different class*)
         </for>
         </template>
@@ -217,29 +219,29 @@ multi-*criteria* decision matrix.
         appear large; the all-negative regime is surfaced as a dedicated
         warning branch below. Do not output anything.
 
-    -   If <percentage/> is less than 0.01 (i.e. <distance/> is
-        effectively zero relative to abs(<rating-K/>)), stop the flow after
-        you output just the following <template/> and do not output anything
-        else:
-
-        <template>
-        <ase-tpl-bullet-signal/> **ERROR**: ✘ *MULTIPLE BEST ALTERNATIVES FOUND*,
-        ⚠ *Please give some hints on the criteria to ensure a single best alternative!*
-        </template>
-
-    -   Otherwise, if <rating-K/> is less than zero (i.e. all alternatives
+    -   If <rating-K/> is less than zero (i.e. all alternatives
         rate negatively and the "best" is merely the least-bad), stop the
         flow after you output just the following <template/> and do not
         output anything else. This all-negative check is evaluated *before*
-        the small-distance check below, so that an all-negative alternative
+        the small-distance checks below, so that an all-negative alternative
         set with a small winning gap surfaces the all-negative warning rather
-        than being masked by the small-distance branch:
+        than being masked by the multiple-best or small-distance branches:
 
         <template>
         <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
         ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
         </template>
 
+    -   Otherwise, if <percentage/> is less than 0.01 (i.e. <distance/> is
+        effectively zero relative to abs(<rating-K/>)), stop the flow after
+        you output just the following <template/> and do not output anything
+        else:
+
+        <template>
+        <ase-tpl-bullet-signal/> **ERROR**: ✘ *MULTIPLE BEST ALTERNATIVES FOUND*,
+        ⚠ *Please give some hints on the criteria to ensure a single best alternative!*
+        </template>
+
     -   Otherwise, if <percentage/> is less than 0.10, stop the flow after
         you output just the following <template/> and do not output anything
         else:

package/plugin/skills/ase-meta-quorum/SKILL.md

@@ -142,9 +142,9 @@ by querying *multiple* AIs for an *optimal consensus*.
     set <disagreement/> to `(no quorum: no foreign AIs were available)`,
     then skip the rest of this step.
 
-    Otherwise, determine, on a Likert scale of 0..<n/>, the amount of the
-    overall consensus <c/> of all the responses. The <n/> is the *total
-    number of responders* (yourself plus all available foreign AIs above).
+    Otherwise, let <n/> be the *total number of responders* (yourself plus
+    all available foreign AIs above). Then determine, on a Likert scale of
+    0..<n/>, the amount of the overall consensus <c/> of all the responses.
     If all responses disagree, the consensus <c/> is zero.
     If all responses agree, <c/> is <n/>.
 

package/plugin/skills/ase-task-condense/SKILL.md

@@ -93,6 +93,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Set <words-before><words/></words-before> (remember the loaded
         word count for the strictly-smaller check in step 3).
 
+        <if condition="<content/> contains 'Created:  <text/>'">
+        Set <timestamp-created><text/></timestamp-created> (extract the
+        original creation timestamp so it can be re-inserted unchanged
+        into the condensed <content/> in step 3).
+        </if>
+
         Only output the following <template/>:
 
         <template>

package/plugin/skills/ase-task-edit/SKILL.md

@@ -171,7 +171,11 @@ Set <content-dirty>true</content-dirty>.
 
     1.  Determine any existing plan content:
 
-        <if condition="<getopt-option-int-reuse-task/> is equal `true`">
+        <if condition="
+            <getopt-option-int-reuse-task/> is equal `true`
+            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
+            exists earlier in the current session
+        ">
             Set <text/> to the `text` argument of the most recent
             `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
             *without* calling `ase_task_load` again. Set <status>plan
@@ -286,7 +290,7 @@ Set <content-dirty>true</content-dirty>.
             </template>
         </if>
 
-    4.  <if condition="<content/> does not contain '#   TASK' AND <instruction/> is empty">
+    4.  <if condition="no line of <content/> matches the case-insensitive regex `^\s*#+\s*TASK\b` AND <instruction/> is empty">
         Set <instruction><content/></instruction> (set instruction to content).
         Set <content></content> (set content to empty).
         Set <content-dirty>true</content-dirty>.

package/plugin/skills/ase-task-grill/SKILL.md

@@ -80,7 +80,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  Determine the current task plan content:
 
-        <if condition="<getopt-option-int-reuse-task/> is equal `true`">
+        <if condition="
+            <getopt-option-int-reuse-task/> is equal `true`
+            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
+            exists earlier in the current session
+        ">
             Set <text/> to the `text` argument of the most recent
             `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
             *without* calling `ase_task_load` again. Set <status>plan
@@ -105,12 +109,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
             Set <plan><text/></plan> (set plan to text).
             Calculate the number of words <words/> of <plan/>.
+            Then output the following <template/>:
 
-        Output the following <template/>:
-
-        <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
-        </template>
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
+            </template>
 
     2.  <if condition="<plan/> is empty">
         Complain and tell the user to use the `ase-code-resolve`,

package/plugin/skills/ase-task-id/SKILL.md

@@ -52,9 +52,9 @@ Configure Task Id
     </if>
 
 4.  <if condition="<request/> is NOT empty">
-    -   Set <ase-task-id><request/></ase-task-id> and
-        call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")`
-        tool from the `ase` MCP server.
+    -   Call the `ase_task_id(id: "<request/>", session: "<ase-session-id/>")`
+        tool from the `ase` MCP server. Check the response as mandated
+        above; only on a clean response set <ase-task-id><request/></ase-task-id>.
 
     -   Output:
         <template>

package/plugin/skills/ase-task-implement/SKILL.md

@@ -97,7 +97,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  Determine the current task plan content:
 
-        <if condition="<getopt-option-int-reuse-task/> is equal `true`">
+        <if condition="
+            <getopt-option-int-reuse-task/> is equal `true`
+            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
+            exists earlier in the current session
+        ">
             Set <text/> to the `text` argument of the most recent
             `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
             *without* calling `ase_task_load` again. Set <status>plan
@@ -210,7 +214,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             skill accepts only an optional `[<id>]` argument and no
             `--next` option; remaining tokens are intentionally discarded.
             Only output the following <template/> and then call the
-            tool `Skill(skill: "ase:ase-task-delete", args: <args/>)`
+            tool `Skill(skill: "ase:ase-task-delete", args: "<args/>")`
             to invoke the `ase:ase-task-delete` skill in order to
             *delete* the updated plan. Immediately stop processing the
             current skill once the `Skill` tool was used.

package/plugin/skills/ase-task-preflight/SKILL.md

@@ -97,7 +97,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  Determine the current task plan content:
 
-        <if condition="<getopt-option-int-reuse-task/> is equal `true`">
+        <if condition="
+            <getopt-option-int-reuse-task/> is equal `true`
+            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
+            exists earlier in the current session
+        ">
             Set <text/> to the `text` argument of the most recent
             `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
             *without* calling `ase_task_load` again. Set <status>plan

package/plugin/skills/ase-task-rename/SKILL.md

@@ -71,6 +71,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </template>
         </if>
 
+    6.  <if condition="<old/> is equal <new/>">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<old/>**, ▶ status: **task unchanged (old and new task id are equal)**
+        </template>
+        </if>
+
 2.  **Perform Operation**:
 
     1.  Call the `ase_task_rename(old: "<old/>", new: "<new/>")` tool of the