@rse/ase 0.9.7 → 0.9.9

package/plugin/meta/ase-skill.md

@@ -25,6 +25,18 @@ Skill Output
     Unicode characters, and the potential reduction of prose according
     to the currently defined persona style.
 
+-   *IMPORTANT*: For *Final-Message-Only Display* ("focus mode"):
+    some agent harnesses show the user only the *final* text message of
+    a turn and *hide* all text emitted *between* tool calls. If your
+    harness instructions indicate such a mode (e.g. *Claude Code* with
+    "focus mode" enabled), you *MUST* repeat *all* <template/> outputs
+    emitted since the last shown final text message -- *verbatim*, in
+    their *original order*, and each only *once* -- at the *top* of the
+    next final text message (i.e. the text after the last tool call of
+    a turn). Never *drop* or *summarize* a <template/> output just
+    because it would land between tool calls. If no such display mode
+    is indicated, do *not* repeat anything.
+
 -   *IMPORTANT*: The active *persona style* (see `ase-persona.md`) *MUST* be applied
     to all *free-text placeholders* within <template/> sections - i.e. any placeholder
     whose content you author yourself (such as `<description/>`, `<title/>`, `<objective/>`,
@@ -98,14 +110,21 @@ Skill Sequential Processing
 -   *IMPORTANT*: For each given <flow/>, you *MUST* use the
     `TaskCreate` tool to create a corresponding set of processing steps.
 
-    Each `<step id="xxx" [...]/>` corresponds to a `TaskCreate({
-    subject: "xxx", description: "xxx", activeForm: "xxx" })`. In other
-    words, use the text of the `id` attribute of <step/> for both
-    the `subject`, the `description`, and the `activeForm` fields of
+    Each `<step id="xxx" [...]>...</step>` corresponds to a
+    `TaskCreate({ subject: "xxx", description: "xxx" })`. In other
+    words, use the text of the `id` attribute of <step/> exactly
+    *as-is* for both the `subject`, and the `description` fields of
     `TaskCreate`.
 
-    Make the `TaskCreate` tool calls *sequentially*, *not* in parallel,
-    so the user can see intermediate results.
+    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/>).
 
 -   *IMPORTANT*: For each <step/> you *MUST* use the `TaskUpdate` tool
     for updating its status during processing.
@@ -208,12 +227,12 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 8 - 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>
 
@@ -226,15 +245,65 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 8 - 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>
+
+    ╰────━━━━**(** `⧉ 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>
 
-    ╰────━━━━**(** `<title/>` **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╭────━━━━**(** <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>
@@ -246,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.7",
+    "version":                              "0.9.9",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -15,7 +15,7 @@
     },
     "devDependencies": {
         "@rse/stx":                         "1.1.5",
-        "markdownlint":                     "0.40.0",
+        "markdownlint":                     "0.41.0",
         "markdownlint-cli2":                "0.22.1",
         "eslint":                           "10.4.1",
         "@eslint/markdown":                 "8.0.2",

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

@@ -7,94 +7,94 @@ disable-model-invocation: false
 model: opus
 effort: high
 allowed-tools:
-    - "Bash(wc:*)"
-    - "Bash(ls:*)"
-    - "Bash(tree:*)"
-    - "Bash(file:*)"
-    - "Bash(du:*)"
-    - "Bash(stat:*)"
-    - "Bash(grep:*)"
-    - "Bash(awk:*)"
-    - "Bash(head:*)"
-    - "Bash(tail:*)"
-    - "Bash(sort:*)"
-    - "Bash(uniq:*)"
-    - "Bash(cat:*)"
-    - "Bash(cut:*)"
-    - "Bash(tr:*)"
-    - "Bash(nl:*)"
-    - "Bash(column:*)"
-    - "Bash(diff:*)"
-    - "Bash(cmp:*)"
-    - "Bash(jq:*)"
-    - "Bash(cloc:*)"
-    - "Bash(tokei:*)"
-    - "Bash(scc:*)"
-    - "Bash(basename:*)"
-    - "Bash(dirname:*)"
-    - "Bash(realpath:*)"
-    - "Bash(readlink:*)"
-    - "Bash(pwd:*)"
-    - "Bash(which:*)"
-    - "Bash(whereis:*)"
-    - "Bash(type:*)"
-    - "Bash(namei:*)"
-    - "Bash(git log:*)"
-    - "Bash(git show:*)"
-    - "Bash(git diff:*)"
-    - "Bash(git blame:*)"
-    - "Bash(git ls-files:*)"
-    - "Bash(git ls-tree:*)"
-    - "Bash(git grep:*)"
-    - "Bash(git status:*)"
-    - "Bash(git rev-list:*)"
-    - "Bash(git rev-parse:*)"
-    - "Bash(git for-each-ref:*)"
-    - "Bash(git reflog:*)"
-    - "Bash(git cat-file:*)"
-    - "Bash(git config --get:*)"
-    - "Bash(git config --list:*)"
-    - "Bash(git remote:*)"
-    - "Bash(git branch:*)"
-    - "Bash(git tag --list:*)"
-    - "Bash(git describe:*)"
-    - "Bash(git shortlog:*)"
-    - "Bash(find * -name:*)"
-    - "Bash(find * -type:*)"
-    - "Bash(find * -path:*)"
-    - "Bash(find * -maxdepth:*)"
-    - "Bash(find * -mindepth:*)"
-    - "Bash(find * -size:*)"
-    - "Bash(find * -mtime:*)"
-    - "Bash(find * -newer:*)"
-    - "Bash(git diff:* | awk:*)"
-    - "Bash(git diff:* | grep:*)"
-    - "Bash(git diff:* | head:*)"
-    - "Bash(git diff:* | tail:*)"
-    - "Bash(git diff:* | wc:*)"
-    - "Bash(git log:* | head:*)"
-    - "Bash(git log:* | grep:*)"
-    - "Bash(git log:* | wc:*)"
-    - "Bash(git show:* | head:*)"
-    - "Bash(git show:* | grep:*)"
-    - "Bash(git grep:* | head:*)"
-    - "Bash(git grep:* | wc:*)"
-    - "Bash(git ls-files:* | grep:*)"
-    - "Bash(git ls-files:* | head:*)"
-    - "Bash(git ls-files:* | wc:*)"
-    - "Bash(grep:* | head:*)"
-    - "Bash(grep:* | sort:*)"
-    - "Bash(grep:* | wc:*)"
-    - "Bash(grep:* | sort:* | uniq:*)"
-    - "Bash(cat:* | grep:*)"
-    - "Bash(cat:* | awk:*)"
-    - "Bash(cat:* | head:*)"
-    - "Bash(cat:* | wc:*)"
-    - "Bash(find:* | head:*)"
-    - "Bash(find:* | wc:*)"
-    - "Bash(awk:* | head:*)"
-    - "Bash(sort:* | uniq:*)"
-    - "Bash(sort:* | head:*)"
+    - "Bash(wc *)"
+    - "Bash(ls *)"
+    - "Bash(tree *)"
+    - "Bash(file *)"
+    - "Bash(du *)"
+    - "Bash(stat *)"
+    - "Bash(grep *)"
+    - "Bash(awk *)"
+    - "Bash(head *)"
+    - "Bash(tail *)"
+    - "Bash(sort *)"
+    - "Bash(uniq *)"
+    - "Bash(cat *)"
+    - "Bash(cut *)"
+    - "Bash(tr *)"
+    - "Bash(nl *)"
+    - "Bash(column *)"
+    - "Bash(diff *)"
+    - "Bash(cmp *)"
+    - "Bash(jq *)"
+    - "Bash(cloc *)"
+    - "Bash(tokei *)"
+    - "Bash(scc *)"
+    - "Bash(basename *)"
+    - "Bash(dirname *)"
+    - "Bash(realpath *)"
+    - "Bash(readlink *)"
+    - "Bash(pwd *)"
+    - "Bash(which *)"
+    - "Bash(whereis *)"
+    - "Bash(type *)"
+    - "Bash(namei *)"
+    - "Bash(git log *)"
+    - "Bash(git show *)"
+    - "Bash(git diff *)"
+    - "Bash(git blame *)"
+    - "Bash(git ls-files *)"
+    - "Bash(git ls-tree *)"
+    - "Bash(git grep *)"
+    - "Bash(git status *)"
+    - "Bash(git rev-list *)"
+    - "Bash(git rev-parse *)"
+    - "Bash(git for-each-ref *)"
+    - "Bash(git reflog *)"
+    - "Bash(git cat-file *)"
+    - "Bash(git config --get *)"
+    - "Bash(git config --list *)"
+    - "Bash(git remote *)"
+    - "Bash(git branch *)"
+    - "Bash(git tag --list *)"
+    - "Bash(git describe *)"
+    - "Bash(git shortlog *)"
+    - "Bash(find * -name *)"
+    - "Bash(find * -type *)"
+    - "Bash(find * -path *)"
+    - "Bash(find * -maxdepth *)"
+    - "Bash(find * -mindepth *)"
+    - "Bash(find * -size *)"
+    - "Bash(find * -mtime *)"
+    - "Bash(find * -newer *)"
+    - "Bash(git diff * | awk *)"
+    - "Bash(git diff * | grep *)"
+    - "Bash(git diff * | head *)"
+    - "Bash(git diff * | tail *)"
+    - "Bash(git diff * | wc *)"
+    - "Bash(git log * | head *)"
+    - "Bash(git log * | grep *)"
+    - "Bash(git log * | wc *)"
+    - "Bash(git show * | head *)"
+    - "Bash(git show * | grep *)"
+    - "Bash(git grep * | head *)"
+    - "Bash(git grep * | wc *)"
+    - "Bash(git ls-files * | grep *)"
+    - "Bash(git ls-files * | head *)"
+    - "Bash(git ls-files * | wc *)"
+    - "Bash(grep * | head *)"
+    - "Bash(grep * | sort *)"
+    - "Bash(grep * | wc *)"
+    - "Bash(grep * | sort * | uniq *)"
+    - "Bash(cat * | grep *)"
+    - "Bash(cat * | awk *)"
+    - "Bash(cat * | head *)"
+    - "Bash(cat * | wc *)"
+    - "Bash(find * | head *)"
+    - "Bash(find * | wc *)"
+    - "Bash(awk * | head *)"
+    - "Bash(sort * | uniq *)"
+    - "Bash(sort * | head *)"
     - "Agent"
     - "Skill"
 ---
@@ -437,7 +437,6 @@ interface quality, quality attributes, and architecture governance.
     Finally, output the following <template/> to give a final hint:
 
     <template>
-    ⧉ **ASE**: ☻ skill: **<skill-name/>**, ▶ status: **skill finished**
     ⧉ **ASE**: ↪ hint: **For deeper analysis, suggestions on solution approaches and then final source code changes, use `/ase-code-resolve P{n}` or `/ase-code-resolve T{n}` in the same or even a different session.**
     </template>
     </step>

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,26 +99,35 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 3.  <step id="STEP 3: Discover Components">
-    -   From <stack/> and <functionality/>, derive essential keywords
+    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):
+
+        <template>
+        <ase-tpl-bullet-normal/> **RESULT**: technology stack could not be determined -- component discovery is only supported for JavaScript, TypeScript, Java, and Kotlin projects.
+        </template>
+
+    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
@@ -113,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
@@ -131,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
@@ -145,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
@@ -160,31 +182,31 @@ 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:
 
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT HINTS**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ⚖ *Hint*  |
-        | :----------------- | :------------- | :-------- |
-        | **<component-1/>** | `<package-1/>` | <info-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ⚖ *Hint*  |
+        | :------------ | :------------- | :-------- |
+        | **<name-1/>** | `<package-1/>` | <info-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <info-N/> |
+        | **<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>
         <ase-tpl-bullet-normal/> **COMPONENT RANKING**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
-        | :----------------- | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
-        | **<component-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
+        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
+        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
+        | **<name-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
         </template>
     </step>
 </flow>

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/SKILL.md

@@ -202,9 +202,12 @@ problems in *performance* and *efficiency*, or problems in *security*.
         <template>(`<filename/>#<function-or-method/>`)</template>.
 
     -   In <description/>, classify the problem with a <severity/>
-        of <template>LOW</template>, <template>MEDIUM</template> or
-        <template>HIGH</template>, ranked by the estimated *impact* of the
-        problem.
+        of <template>LOW</template>, <template>MEDIUM</template>,
+        <template>HIGH</template>, or <template>ACCEPTED</template>,
+        ranked by the estimated *impact* of the problem. Use
+        <template>ACCEPTED</template> when the problem is a deliberate,
+        justified trade-off that should remain on record but is never
+        dropped by the severity floor (see STEP 3).
 
     -   <if condition="<getopt-option-performance/> is equal `true`">
         In <evidence/>, ground the finding by citing either the inferred
@@ -241,5 +244,3 @@ problems in *performance* and *efficiency*, or problems in *security*.
     </step>
 
 </flow>
-
-</output>

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).