@rse/ase 0.9.8 → 0.9.9

package/dst/ase-statusline.js

@@ -245,12 +245,14 @@ export default class StatuslineCommand {
                 out += ansi;
                 col += raw.length;
             };
-            /*  active <color> span state: when non-null, renderer/literal output is buffered
-                instead of appended directly, and flushed via c[color](buf) on </color>  */
+            /*  active <color> span state: when non-null, each emitted chunk is colored
+                individually and passed straight through appendOutput, so column
+                accounting and line-wrapping continue to work per-chunk inside the span
+                instead of treating the whole colored run as one atomic chunk  */
             let span = null;
             const emit = (chunk) => {
-                if (span !== null)
-                    span.buf += chunk;
+                if (span !== null && span.color !== "default")
+                    appendOutput((c[span.color])(chunk));
                 else
                     appendOutput(chunk);
             };
@@ -446,13 +448,7 @@ export default class StatuslineCommand {
             };
             /*  walk each template line and render  */
             const closeSpan = () => {
-                if (span !== null) {
-                    const wrapped = span.color === "default" ?
-                        span.buf :
-                        (c[span.color])(span.buf);
-                    span = null;
-                    appendOutput(wrapped);
-                }
+                span = null;
             };
             for (const line of tmpl) {
                 let i = 0;
@@ -465,7 +461,7 @@ export default class StatuslineCommand {
                             if (m[1] === "/")
                                 closeSpan();
                             else if (span === null)
-                                span = { color: m[2], buf: "" };
+                                span = { color: m[2] };
                             i += m[0].length;
                             continue;
                         }

package/dst/ase-task.js

@@ -59,12 +59,22 @@ export class Task {
     static baseDir(log) {
         return path.join(Task.projectRoot(), Task.spec(log).basedir);
     }
+    /*  ensure a task id's "TASK-<id>.md" filename satisfies
+        the configured "files" miniglob  */
+    static enforceFiles(log, id) {
+        const { files } = Task.spec(log);
+        const filename = `TASK-${id}.md`;
+        if (!picomatch(files, { dot: true })(filename))
+            throw new Error(`task: id "${id}" yields filename "${filename}" ` +
+                `which does not match the configured "files" glob "${files}"`);
+    }
     /*  resolve the on-disk path for a given task id; as a side effect,
         eagerly migrate any legacy <basedir>/<id>/plan.md files to the
         current <basedir>/TASK-<id>.md layout on first access (guarded by
         a cheap check, so it is a no-op once the store is migrated)  */
     static path(log, id) {
         Task.validateId(id);
+        Task.enforceFiles(log, id);
         if (Task.needsMigration(log))
             Task.migrateAll(log);
         return path.join(Task.baseDir(log), `TASK-${id}.md`);
@@ -93,7 +103,7 @@ export class Task {
             return [];
         const migrated = [];
         for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
-            if (!entry.isDirectory() || !/^[A-Za-z0-9-]+$/.test(entry.name))
+            if (!entry.isDirectory() || !/^[A-Za-z0-9_-]+$/.test(entry.name))
                 continue;
             const id = entry.name;
             const oldFile = path.join(dir, id, "plan.md");
@@ -138,7 +148,7 @@ export class Task {
     }
     /*  rename a task by moving its <project>/<basedir>/TASK-<oldId>.md file
         to <project>/<basedir>/TASK-<newId>.md; the embedded
-        "# ✪ TASK <id>:" heading inside the plan content is rewritten to
+        "#   TASK <id>:" heading inside the plan content is rewritten to
         the new id; returns true on success, false if the source task does
         not exist; throws if the target id already exists  */
     static rename(log, oldId, newId) {

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.8",
+    "version":                              "0.9.9",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -42,7 +42,7 @@
     },
     "dependencies": {
         "commander":                        "15.0.0",
-        "@dotenvx/dotenvx":                 "1.71.2",
+        "@dotenvx/dotenvx":                 "1.71.3",
         "yaml":                             "2.9.0",
         "valibot":                          "1.4.1",
         "execa":                            "9.6.1",

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

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.8",
+    "version":     "0.9.9",
     "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.8",
+    "version":     "0.9.9",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/meta/ase-dialog.md

@@ -1,5 +1,4 @@
 
-
 User Dialog
 ===========
 
@@ -15,13 +14,16 @@ User Dialog
 Let the *user interactively choose* an answer.
 
 1.  Take the following question specification:
+
     <spec>
         <content/>
     </spec>
 
-    Each line of <spec/> (separated by newlines) is of the format:
+    The first line of <spec/> (separated by newlines) is of the format:
+    `<question-label/>: <question-description/>`
 
-    `<label/>: <description/>`.
+    The second and following lines of <spec/> (separated by newlines) are of the format:
+    `<label/>: <description/>`
 
     The first line provides the question label and the question
     description. The second and following lines each provide an
@@ -49,8 +51,8 @@ Let the *user interactively choose* an answer.
 
             If <n/> is less than 2:
             Set <result>ERROR: user-dialog requires 2-4 answer lines, got <n/></result>
-            and *SKIP* the following step 2 (do not call `AskUserQuestion`)
-            and continue with step 3 dispatch.
+            and *SKIP* the following step 2.2 (do not call `AskUserQuestion`)
+            and continue with step 2.3 dispatch.
 
         2.  Call the `AskUserQuestion` tool of the agent harness with:
 
@@ -103,8 +105,8 @@ Let the *user interactively choose* an answer.
 
             If <n/> is less than 2:
             Set <result>ERROR: user-dialog requires 2-4 answer lines, got <n/></result>
-            and *SKIP* the following step 2 (do not call `ask_user`)
-            and continue with step 3 dispatch.
+            and *SKIP* the following step 2.2 (do not call `ask_user`)
+            and continue with step 2.3 dispatch.
 
         2.  Call the `ask_user` tool of the agent harness with:
 
@@ -137,3 +139,99 @@ Let the *user interactively choose* an answer.
 
 </define>
 
+<define name="custom-dialog">
+Let the *user interactively choose* an answer.
+
+1.  Take the following question specification:
+
+    <spec>
+        <content/>
+    </spec>
+
+    The first line of <spec/> (separated by newlines) is of the format:
+    `<question-label/>: <question-description/>`
+
+    The second and following lines of <spec/> (separated by newlines) are of the format:
+    `<label/>: <description/>`
+
+    The first line provides the question label and the question
+    description. The second and following lines each provide an
+    answer label and an answer description.
+
+    Do not output anything in this step!
+
+2.  Dispatch according to the agent tool:
+
+    1.  You *MUST* not output anything in this step.
+
+        Set <text></text> (set to empty).
+        Set <keys></keys> (set to empty).
+        Set <n>1</n> (set entry count to one).
+        Set <width/> to the maximum length plus 3 of all <label/> strings in <spec/>.
+
+        <for items="2 3 4 5 6 7 8 9">
+            Take from <spec/> the line number <item/>.
+            If this line does not exist, <break/>.
+            If this line exists, parse it according to the format `<label/>: <description/>`.
+            Set <label-key/> to <ase-tpl-key digit="<n/>"/>.
+            Set <label-text/> to `<ase-tpl-pad width="<width/>" text="<label/>:"/>`.
+            Append an entry to <text/>:
+
+            <text>
+            <text/>
+            <ase-tpl-boxline><label-key/>  ▶  **<label-text/>** <description/></ase-tpl-boxline>
+            </text>
+
+            Set <n/> to <n/> + 1 (increment entry count).
+            <if condition="<keys/> is empty">
+                Set <keys><label-key/></keys>
+            </if>
+            <else>
+                Set <keys><keys/>/<label-key/></keys>
+            </else>
+        </for>
+
+        Set:
+
+        <text>
+        <ase-tpl-boxed title="QUESTION" subtitle="<question-label/>">
+
+        <ase-tpl-boxline>**<question-description/>**</ase-tpl-boxline>
+
+        <text/>
+
+        Please choose *one* option by typing <keys/>/**CANCEL** or free-text instruction.
+
+        </ase-tpl-boxed>
+        </text>
+
+        If <n/> is less than 3:
+        Set <result>ERROR: user-dialog requires 2-8 answer lines, got less</result>
+        and *SKIP* the following step 2 and continue with step 3 dispatch.
+
+    2.  Output the following <template/>, end the current turn, wait for the
+        user input, store the user input in <result/> and then continue with step 3:
+
+        <template>
+        <text/>
+        </template>
+
+    3.  Check the result and dispatch accordingly:
+
+        -   If <result/> indicates that the user doesn't want to proceed,
+            or the user declined to answer the question, or that the dialog
+            was cancelled, rejected or skipped, set <result>CANCEL</result>.
+
+        -   Otherwise, determine the selected <label/>
+            by mapping the <result/> (usually containing one of the
+            "key" or "label" strings) to one of the answer labels. Set
+            <result><label/></result>.
+
+            If <result/> is then *NOT* one of the "label" values from
+            <spec/>, set <result>OTHER: <result/></result> (prefix
+            result with "OTHER").
+
+        Do not output anything in this step!
+
+</define>
+

package/plugin/meta/ase-getopt.md

@@ -8,31 +8,39 @@ Do not output anything in the following steps. The entire purpose is to
 set placeholders into the context as a side-effect.
 
 1.  **Determine Parameters**:
-    Set <getopt-skill><arg1/></getopt-skill>.
-    Set <getopt-spec>--help|-h <arg2/></getopt-spec>.
-    Set <getopt-args><content/></getopt-args>.
+    Set <getopt-skill><arg1/></getopt-skill>
+    Set <getopt-spec>--help|-h <arg2/></getopt-spec>
+    Set <getopt-args><content/></getopt-args>
 
 2.  **Short-Circuit Processing**:
-    If <getopt-args/> does *NOT* match the regexp `(^|\s)-` (i.e.
-    contains no options at all):
-
-    For each option token in <getopt-spec/> of the form
-    `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
-    <getopt-option-<long/>/> to <default/> (for `=<default/>`
-    form), or to <c1/> (the first choice, for `=(<c1/>|<c2>/|...)`
-    form, or for the list form `=(<c1/>|<c2>/|...)...`),
-    or to `false` (for value-less options). Then set
-    <getopt-arguments><getopt-args/></getopt-arguments>.
-
-    Additionally, simulate <getopt-info/> as a comma-separated
-    markdown rendering of the parsed options in the form `<longN/>:
-    **<valueN/>**, [...]` (joined with `, `, with each value
-    shell-quoted if value contains spaces or special characters, and
-    excluding the `help` option and any *internal* option whose long
-    name starts with `int-`).
-
-    Then silently *SKIP* only the following steps 3-6
-    and proceed directly to step 7 to display the results.
+    You *MUST* decide here, via the following *mandatory* <if/> control
+    construct, whether the options are parsed *locally* (no MCP call) or
+    *remotely* (via the MCP call in steps 3-6). This is a *hard branch*,
+    not an optional optimization: when the <if/> branch is taken, steps
+    3-6 are *structurally unreachable* and you *MUST NOT* call the
+    `ase_getopt` MCP tool under any circumstances.
+
+    <if condition="<getopt-args/> does *NOT* match the regexp `(^|\s)-` (i.e. it does not start with an option)">
+        Parse the options *locally*, without any MCP call:
+
+        For each option token in <getopt-spec/> of the form
+        `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
+        <getopt-option-<long/>/> to <default/> (for `=<default/>`
+        form), or to <c1/> (the first choice, for `=(<c1/>|<c2>/|...)`
+        form, or for the list form `=(<c1/>|<c2>/|...)...`),
+        or to `false` (for value-less options). Then set
+        <getopt-arguments><getopt-args/></getopt-arguments>.
+
+        Additionally, simulate <getopt-info/> as a comma-separated
+        markdown rendering of the parsed options in the form `<longN/>:
+        **<valueN/>**, [...]` (joined with `, `, with each value
+        shell-quoted if value contains spaces or special characters, and
+        excluding the `help` option and any *internal* option whose long
+        name starts with `int-`).
+
+        You then *MUST* silently *SKIP* the steps 3-6 below
+        and proceed directly to step 7 to display the results.
+    </if>
 
 3.  **MCP Call**:
     Call the `ase_getopt(name: "<getopt-skill/>", spec:

package/plugin/meta/ase-skill.md

@@ -227,12 +227,12 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
-    the "─" character repeated (70 - 16 - length("<title/>")) times):
+    (where <bar/> = "─" x (67 - length("⧉ ASE: <title/>")), i.e., <bar/> is
+    the "─" character repeated (67 - length("⧉ ASE: <title/>")) times):
 
     <template>
 
-    ╭────━━━━**(** `<title/>` **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╭────━━━━**(** `⧉ ASE`: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
@@ -245,15 +245,65 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
-    the "─" character repeated (71 - 16 - length("<title/>")) times):
+    (where <bar/> = "─" x (67 - length("⧉ ASE: <title/>")), i.e., <bar/> is
+    the "─" character repeated (67 - length("⧉ ASE: <title/>")) times):
 
     <template>
 
-    ╰────━━━━**(** `<title/>` **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╰────━━━━**(** `⧉ ASE`: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
+-   When `<ase-tpl-boxline><line/></ase-tpl-boxline>` should be expanded, use:
+
+    <if condition="<line/> is not empty">
+        <template>
+        │ <line/>
+        </template>
+    </if>
+    <else>
+        <template>
+        │
+        </template>
+    </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/>:
+
+    -   <if condition="<subtitle/> is not empty">
+            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 <render-title>`⧉ ASE`: **`<title/>`**</render-title>.
+        </else>
+    -   Set <bar/> to ("─" x (67 - length("<raw-title/>"))),
+        i.e., set <bar/> to the "─" character repeated (67 - length("<raw-title/>")) times.
+    -   Set <body> to <content/> with all line-starts prefixed with `│ `.
+
+    <template>
+
+    ╭────━━━━**(** <render-title/> **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    │
+    <body/>
+    │
+    ╰────━━━━**(** <render-title/> **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+
+    </template>
+
+-   When `<ase-tpl-key digit="<digit/>"/>` should be expanded, use:
+
+    <if condition="<digit/> is '1'"><template>➊</template></if>
+    <if condition="<digit/> is '2'"><template>➋</template></if>
+    <if condition="<digit/> is '3'"><template>➌</template></if>
+    <if condition="<digit/> is '4'"><template>➍</template></if>
+    <if condition="<digit/> is '5'"><template>➎</template></if>
+    <if condition="<digit/> is '6'"><template>➏</template></if>
+    <if condition="<digit/> is '7'"><template>➐</template></if>
+    <if condition="<digit/> is '8'"><template>➑</template></if>
+    <if condition="<digit/> is '9'"><template>➒</template></if>
+
 -   When `<ase-tpl-bullet-secondary/>` should be expanded, use:
 
     <template>⚪</template>
@@ -265,3 +315,9 @@ Template Patterns
 -   When `<ase-tpl-bullet-signal/>` should be expanded, use:
 
     <template>🟠</template>
+
+-   When `<ase-tpl-pad width="<width/>" text="<text/>"/>` should be expanded, use
+    (where <ws/> = ` ` x (<width/> - length("<text/>")), i.e., <ws/> is
+    the ` ` character repeated (<width/> - length("<text/>")) times):
+
+    <template><text/><ws/></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.8",
+    "version":                              "0.9.9",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -46,5 +46,5 @@ Analyze a specific module:
 
 ##  SEE ALSO
 
-`ase-arch-discover`, `ase-code-analyze`, `ase-code-resolve`,
-`ase-code-refactor`, `ase-code-insight`.
+[`ase-arch-discover`](../ase-arch-discover/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md),
+[`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-insight`](../ase-code-insight/help.md).

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

@@ -37,13 +37,26 @@ for the technology stack to *provide* the *needed functionality*
 
 <flow>
 1.  <step id="STEP 1: Determine Functionality">
-    -   Derive the needed <functionality/> from the <request/>, but keep
+    1.  Derive the needed <functionality/> from the <request/>, but keep
         the functionality description very *brief* but still *precise*.
 
-    -   If <functionality/> is not clear or not precise enough, raise
-        questions to the user with the help of an interactive user dialog tool.
+    2.  If <functionality/> is not clear, not precise, or not specific
+        enough, let the *user interactively choose* the intended
+        functionality. For this you *MUST* use the custom `custom-dialog`
+        and *NOT* the `AskUserQuestion` based "user-dialog":
 
-    -   Display the determined final functionality with just the following
+        <expand name="custom-dialog">
+            Functionality: Which functionality should the components provide?
+            <answer-1/>: (grounded candidate functionality 1)
+            <answer-2/>: (grounded candidate functionality 2)
+            <answer-3/>: (grounded candidate functionality 2)
+            <answer-4/>: (grounded candidate functionality 3)
+        </expand>
+
+        Then use the <result/> and its corresponding grounded candidate
+        functionality to adjust <functionality/> accordingly.
+
+    3.  Display the determined final functionality with just the following
         <template/>:
 
         <template>
@@ -52,32 +65,32 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 2.  <step id="STEP 2: Determine Technology Stack">
-    -   Determine the used technology stack:
+    1.  Determine the used technology stack:
 
-        -   If a file `package.json` is found in the top-level directory
+        1.  If a file `package.json` is found in the top-level directory
             of the project and contains an entry `typescript` under `dependencies`
             or `devDependencies`, then <stack>TypeScript</stack>.
 
-        -   Else, if a file `package.json` is found in the top-level directory
+        2.  Else, if a file `package.json` is found in the top-level directory
             of the project, then <stack>JavaScript</stack>.
 
-        -   Else, if a file `build.gradle.kts` or `settings.gradle.kts`
+        3.  Else, if a file `build.gradle.kts` or `settings.gradle.kts`
             is found in the top-level directory, then <stack>Kotlin</stack>.
 
-        -   Else, if a file `build.gradle` is found in the top-level directory and
+        4.  Else, if a file `build.gradle` is found in the top-level directory and
             is applying `kotlin`, `org.jetbrains.kotlin.jvm`, `kotlin-android`,
             or `kotlin-multiplatform` plugins, then <stack>Kotlin</stack>.
 
-        -   Else, if a file `pom.xml` is found in the top-level directory and
+        5.  Else, if a file `pom.xml` is found in the top-level directory and
             contains `kotlin-maven-plugin` or `kotlin-stdlib` dependencies, then
             <stack>Kotlin</stack>.
 
-        -   Else, if a file `pom.xml` or `build.gradle` is found in the top-level directory
+        6.  Else, if a file `pom.xml` or `build.gradle` is found in the top-level directory
             of the project, then <stack>Java</stack>.
 
-        -   Else, use <stack>Unknown</stack>.
+        7.  Else, use <stack>Unknown</stack>.
 
-    -   Display the determined final technology stack with just the
+    2.  Display the determined final technology stack with just the
         following <template/>:
 
         <template>
@@ -86,7 +99,7 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 3.  <step id="STEP 3: Discover Components">
-    -   If <stack/> is "Unknown", the technology stack could not be
+    1.  If <stack/> is "Unknown", the technology stack could not be
         determined and no component discovery backend is available.
         Inform the user with just the following <template/> and then
         *STOP* the entire flow (do not perform any further steps):
@@ -95,26 +108,26 @@ for the technology stack to *provide* the *needed functionality*
         <ase-tpl-bullet-normal/> **RESULT**: technology stack could not be determined -- component discovery is only supported for JavaScript, TypeScript, Java, and Kotlin projects.
         </template>
 
-    -   From <stack/> and <functionality/>, derive essential keywords
+    2.  From <stack/> and <functionality/>, derive essential keywords
         <keyword-L/> (L=1-M), which allow you to search for suitable
         components.
 
-    -   In the to be discovered result set of components <component-K/>
+    3.. In the to be discovered result set of components <component-K/>
         (K=1-N), remember the component name as <name-K/>, the
         official package name as <package-K/>, the latest version as
         <version-K/>, the stars as <stars-K/>, the created date as
         <created-K/>, the last updated date as <updated-K/>, the total
         number of downloads in the last month as <downloads-K/>.
 
-    -   If <stack/> is "JavaScript" or "TypeScript":
+    4.  If <stack/> is "JavaScript" or "TypeScript":
 
-        -   Based on the essential keywords <keyword-L/> (L=1-M),
+        1.  Based on the essential keywords <keyword-L/> (L=1-M),
             use the `ase-meta-search` skill in a subagent to *generally*
             discover an initial set of a maximum of <getopt-option-limit/> *NPM packages*
             <component-K/> and at least their real name <name-K/> and
             their unique package names <package-K/>.
 
-        -   Use the shell command `npm search --json --searchlimit <getopt-option-limit/>
+        2.  Use the shell command `npm search --json --searchlimit <getopt-option-limit/>
             "<keyword-1/>" [...] "<keyword-M/>"` to *specifically*
             discover an additional set of a maximum of <getopt-option-limit/> *NPM packages*
             <component-K/> and at least their unique package names
@@ -122,16 +135,16 @@ for the technology stack to *provide* the *needed functionality*
             (L=1-M). Merge the results into the already existing result
             set, but deduplicate entries.
 
-    -   If <stack/> is "Java" or "Kotlin":
+    5.  If <stack/> is "Java" or "Kotlin":
 
-        -   Based on the essential keywords <keyword-L/> (L=1-M),
+        1.  Based on the essential keywords <keyword-L/> (L=1-M),
             use the `ase-meta-search` skill in a subagent to *generally*
             discover an initial set of a maximum of <getopt-option-limit/> *Maven packages*
             <component-K/> and at least their real name <name-K/> and
             their unique Maven coordinates <package-K/> of the form
             `groupId:artifactId`.
 
-        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+[...]+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
+        2.  Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+[...]+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
             to *specifically* discover an additional set of a maximum
             of <getopt-option-limit/> *Maven packages* <component-K/> and at least their
             unique Maven coordinates <package-K/> (i.e. `<g/>:<a/>` from
@@ -140,7 +153,7 @@ for the technology stack to *provide* the *needed functionality*
             into the already existing result set, but deduplicate
             entries by Maven coordinate.
 
-    -   Call the `ase_component_info(stack: "<stack/>", components:
+    6.  Call the `ase_component_info(stack: "<stack/>", components:
         [ "<package-1/>", ..., "<package-N/>" ])` tool of the `ase` MCP
         server *once* for the entire set of discovered packages.
         The tool dispatches internally on <stack/> and fetches all
@@ -154,11 +167,11 @@ for the technology stack to *provide* the *needed functionality*
         from `downloads` (numeric or `N.A.`) and <rank-K/> from `rank`
         (numeric).
 
-    -   Sort, in descending order, the discovered components
+    7.  Sort, in descending order, the discovered components
         <component-K/> (K=1-N) by their `rank` field and trim the result
         list to just a maximum of <getopt-option-limit/> total components.
 
-    -   For each component <component-K/> (K=1-N), research and then
+    8.  For each component <component-K/> (K=1-N), research and then
         decide which *one* of *USP* (Unique Selling Point -- what makes
         it unique), *Crux* (what you should notice), or *Gotcha* (what
         you should not stumble over) is its single most distinguishing
@@ -169,7 +182,7 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 4.  <step id="STEP 4: Report Components">
-    -   Display the determined, individual components as a Markdown
+    1.  Display the determined, individual components as a Markdown
         *table* with just the following <template/> and do not output
         anything else:
 
@@ -183,7 +196,7 @@ for the technology stack to *provide* the *needed functionality*
         | **<name-N/>** | `<package-N/>` | <info-N/> |
         </template>
 
-    -   Display the discovered components as a Markdown *table*
+    2.  Display the discovered components as a Markdown *table*
         with just the following <template/>:
 
         <template>

package/plugin/skills/ase-arch-discover/help.md

@@ -59,4 +59,4 @@ Discover a broader set of up to 20 HTTP client components:
 
 ##  SEE ALSO
 
-`ase-arch-analyze`, `ase-meta-search`, `ase-meta-evaluate`.
+[`ase-arch-analyze`](../ase-arch-analyze/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md).

package/plugin/skills/ase-code-analyze/help.md

@@ -83,5 +83,5 @@ Analyze a directory, reporting only `MEDIUM` and `HIGH` problems:
 
 ##  SEE ALSO
 
-`ase-code-resolve`, `ase-code-refactor`, `ase-code-lint`,
-`ase-code-explain`, `ase-arch-analyze`.
+[`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-lint`](../ase-code-lint/help.md),
+[`ase-code-explain`](../ase-code-explain/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).