@rse/ase 0.9.34 → 0.9.36

package/plugin/meta/ase-dialog.md

@@ -13,167 +13,6 @@ User Dialog
     <user-dialog-tool>none</user-dialog-tool>
 </if>
 
-<define name="user-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:
-
-    -   <if condition="<ase-agent-tool/> is 'claude'">
-
-        1.  Start with <config></config> (set config to empty).
-            Do not output anything in this step!
-
-            Start with <n>0</n> (set entry count to zero).
-            <for items="2 3 4 5">
-                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/>`.
-                If <config/> is not empty, set <config><config/>, </config> (append comma).
-                Set <config><config/>{ label: "<label/>",
-                description: "<description/>" }</config> (append a config entry).
-                Set <n/> to <n/> + 1 (increment entry count).
-            </for>
-
-            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.2 (do not call `AskUserQuestion`)
-            and continue with step 2.3 dispatch.
-
-        2.  Call the `AskUserQuestion` tool of the agent harness with:
-
-            `AskUserQuestion({
-                questions: [
-                    {
-                        header:      "<question-label/>",
-                        question:    "<question-description/>",
-                        multiSelect: false,
-                        options: [
-                            <config/>
-                        ]
-                    }
-                ]
-            })`
-
-        3.  Check the tool result and dispatch accordingly:
-
-            -   If <result/> already starts with `ERROR:` (set by the
-                guard in step 2.1 above), keep <result/> unchanged and
-                *SKIP* all remaining dispatch in this step.
-
-            -   If the tool result contains `user doesn't want to proceed`,
-                `tool use was rejected`, or `user declined to answer
-                questions`, or the result clearly indicates that the
-                dialog was cancelled, rejected or skipped, set
-                <result>CANCEL</result>.
-
-            -   Otherwise, extract the selected <answer/> from the
-                tool result `"<question-description/>"="<answer/>"`.
-                Set <result><answer/></result>.
-                If <result/> is then NOT one
-                of the "label" values from <config/>, set
-                <result>OTHER: <result/></result>
-                (prefix result with "OTHER").
-
-            Do not output anything in this step!
-        </if>
-
-    -   <if condition="<ase-agent-tool/> is 'copilot'">
-
-        1.  Start with <config></config> (set config to empty).
-            Do not output anything in this step!
-
-            Start with <n>0</n> (set entry count to zero).
-            <for items="2 3 4 5">
-                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/>`.
-                If <config/> is not empty, set <config><config/>, </config> (append comma).
-                Set <config><config/>"<label/>: <description/>"</config> (append a config entry).
-                Set <n/> to <n/> + 1 (increment entry count).
-            </for>
-
-            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.2 (do not call `ask_user`)
-            and continue with step 2.3 dispatch.
-
-        2.  Call the `ask_user` tool of the agent harness with:
-
-            `ask_user({
-                question: "<question-label/>: <question-description/>",
-                allow_freeform: true,
-                choices: [
-                    <config/>
-                ]
-            })`
-
-        3.  Check the tool result and dispatch accordingly:
-
-            -   If <result/> already starts with `ERROR:` (set by the
-                guard in step 2.1 above), keep <result/> unchanged and
-                *SKIP* all remaining dispatch in this step.
-
-            -   If the tool result contains `User skipped question`
-                or the result clearly indicates that the
-                dialog was cancelled, rejected or skipped, set
-                <result>CANCEL</result>.
-
-            -   Otherwise, extract the selected answer from the tool
-                result and set <result/> accordingly. The harness may
-                return either the full `<label/>: <description/>` line or
-                just the bare `<label/>`. Determine the selected
-                <label/> by mapping the <result/> to one of the answer
-                labels parsed from <spec/> (lines 2 and following): if
-                <result/> is of the format `<label/>: <description/>`,
-                take its `<label/>` part; otherwise, if <result/> already
-                equals one of the answer labels, take it as-is. Set
-                <result><label/></result>. If <result/> is then NOT one
-                of the answer labels parsed from <spec/>, set
-                <result>OTHER: <result/></result>
-                (prefix result with "OTHER").
-
-            Do not output anything in this step!
-
-        </if>
-
-    -   <if condition="<ase-agent-tool/> is 'codex'">
-
-        OpenAI Codex CLI has *no* interactive user-dialog tool, so you
-        *MUST* *NOT* call any tool here. Instead, render the question and
-        answers as a custom Markdown dialog and let the user reply with a
-        free-text choice -- exactly as defined by the following expansion,
-        passing <spec/> as its question specification, and set <result/> to
-        the result of that custom dialog:
-
-        <expand name="custom-dialog" arg1="--other">
-            <spec/>
-        </expand>
-
-        Do not output anything in this step!
-
-        </if>
-
-</define>
-
 <define name="custom-dialog">
 
 In the following, you *MUST* *NOT* use the <user-dialog-tool/> tool!
@@ -216,7 +55,7 @@ following procedure:
             If this line does not exist, <break/>.
             If this line exists, parse it according to the format `<label/>: <description/>`.
             Set <n/> to <n/> + 1 (increment entry count).
-            Set <label-key/> to <ase-tpl-key digit="<n/>"/>.
+            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/>:
 
@@ -276,31 +115,31 @@ following procedure:
     3.  Do not output anything in this step!
         Check the <result/> and dispatch accordingly:
 
-        0.  If <result/> already starts with `ERROR:` (set by the
-            guard in step 2.1 above), keep <result/> unchanged and
-            *SKIP* all remaining sub-steps 3.1-3.3 of this dispatch.
+        1.  If <result/> already starts with `ERROR:` (potentially set by
+            the guard in step 2.1 above), keep <result/> unchanged and
+            *SKIP* all remaining steps 2.3.2 - 2.3.4 of this dispatch.
 
-        1.  If <result/> is `cancel`, `CANCEL`, `reject`, `REJECT`, or
+        2.  If <result/> is `cancel`, `CANCEL`, `reject`, `REJECT`, or
             otherwise 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>.
 
-        2.  Otherwise, determine the selected <label/>
+        3.  Otherwise, determine the selected <label/>
             by mapping the <result/> (usually containing one of the
             "key" or "label" strings) to one of the answer labels in
             <spec/>. Set <result><label/></result>.
 
-        3.  If <result/> is then *NEITHER* one of the "key"
+        4.  If <result/> is then *NEITHER* one of the "key"
             *NOR* "label" values from <spec/>:
             <if condition="<opts/> contains `--other`">
                 Set <result>OTHER: <result/></result>
-                (prefix result with "OTHER").
+                (prefix result with `OTHER: `).
             </if>
             <else>
                 Output the following <template/> and then *START OVER*
-                by *GOING* to step 2.2 above, reusing the already-built
-                <text/> from step 2.1 unchanged (do *NOT* re-enter step 2.1
+                by *GOING* to step 2.2.2 above, reusing the already-built
+                <text/> from step 2.2.1 unchanged (do *NOT* re-enter step 2.2.1
                 and do *NOT* rebuild <text/>, <keys/>, <n/>, or <width/>).
 
                 <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.34",
+    "version":                              "0.9.36",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -16,10 +16,10 @@
     "devDependencies": {
         "@rse/stx":                         "1.1.6",
         "markdownlint":                     "0.41.0",
-        "markdownlint-cli2":                "0.22.1",
-        "eslint":                           "10.5.0",
-        "@eslint/markdown":                 "8.0.2",
-        "eslint-markdown":                  "0.11.0"
+        "markdownlint-cli2":                "0.23.0",
+        "eslint":                           "10.6.0",
+        "@eslint/markdown":                 "8.0.3",
+        "eslint-markdown":                  "0.11.1"
     },
     "engines": {
         "npm":                              ">=10.0.0",

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

@@ -304,10 +304,11 @@ interface quality, quality attributes, and architecture governance.
       specification <mermaid-spec/> for a `flowchart TB` of the
       high-level component or layer structure and dispatch the rendering
       to the `ase-meta-diagram` sub-agent by calling the tool
-      `Agent(name: "ase-meta-diagram", description: "Diagram Rendering",
-      subagent_type: "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`,
-      using its returned fenced code block verbatim. Show layers /
-      slices / major components and their dependency direction.
+      `Agent(description: "Diagram Rendering", subagent_type:
+      "ase:ase-meta-diagram", prompt: <mermaid-spec/>,
+      run_in_background: false)`, using its returned fenced code block
+      verbatim. Show layers / slices / major components and their
+      dependency direction.
 
     - Mark detected *anomalies* directly in the Mermaid source.
       Because `!` and `?` are Mermaid special characters, *always

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

@@ -1,6 +1,6 @@
 ---
 name: ase-arch-discover
-argument-hint: "[--help|-h] [--limit|-l=12] <functionality>"
+argument-hint: "[--help|-h] [--limit|-l=12] [--staleness|-s=18] [--small-scope|-S] <functionality>"
 description: >
     Discover additional, third-party components (libraries/frameworks) for
     the technology stack to provide needed functionality.
@@ -25,7 +25,7 @@ Discover Components
 
 <expand name="getopt"
     arg1="ase-arch-discover"
-    arg2="--limit|-l=12">
+    arg2="--limit|-l=12 --staleness|-s=18 --small-scope|-S">
     $ARGUMENTS
 </expand>
 
@@ -166,18 +166,25 @@ for the technology stack to *provide* the *needed functionality*
             entries by Maven coordinate.
 
     6.  Call the `ase_component_info(stack: "<stack/>", components:
-        [ "<package-1/>", ..., "<package-C/>" ])` tool of the `ase` MCP
-        server *once* for the entire candidate set of discovered packages.
-        The tool dispatches internally on <stack/> and fetches all
-        metadata in maximum parallel and returns an array of objects `{
-        name, version, created, updated, repository, stars, downloads,
-        rank }`. For each
-        component <component-K/> (K=1-C) read from its corresponding
-        entry: <version-K/> from `version`, <updated-K/> from `updated`,
-        <created-K/> from `created`, <repository-K/> from `repository`,
-        <stars-K/> from `stars` (numeric or `N.A.`), <downloads-K/>
-        from `downloads` (numeric or `N.A.`) and <rank-K/> from `rank`
-        (numeric).
+        [ "<package-1/>", ..., "<package-C/>" ], staleMonths:
+        <getopt-option-staleness/>, smallScope: <getopt-option-small-scope/>)`
+        tool of the `ase` MCP server *once* for the entire candidate set of
+        discovered packages. When the <getopt-option-small-scope/> option is
+        enabled, the ranking treats the <functionality/> as *small-scope*,
+        i.e. narrow, self-contained, and low-effort enough that a
+        *dependency-free/hand-rolled* implementation is a realistic
+        alternative to pulling in a third-party component. The tool
+        dispatches internally on <stack/>
+        and fetches all metadata in maximum parallel and returns an array
+        of objects `{ name, version, created, updated, repository, stars,
+        downloads, deps, rank }`. For each component <component-K/>
+        (K=1-C) read from its corresponding entry: <version-K/> from
+        `version`, <updated-K/> from `updated`, <created-K/> from
+        `created`, <repository-K/> from `repository`, <stars-K/> from
+        `stars` (numeric or `N.A.`), <downloads-K/> from `downloads`
+        (numeric or `N.A.`), <deps-K/> from `deps` (numeric or `N.A.`)
+        and <rank-K/> from `rank` (numeric). The returned `rank` already
+        reflects the staleness and small-scope dependency penalties.
 
     7.  Sort, in descending order, the discovered candidate components
         <component-K/> (K=1-C) by their `rank` field and trim the result
@@ -192,7 +199,15 @@ for the technology stack to *provide* the *needed functionality*
         you should not stumble over) is its single most distinguishing
         perspective, and remember this as an <info-K/> (K=1-N) formatted
         like `<type/>: <hint/>` where <type/> is one of `USP`, `Crux`,
-        or `Gotcha` and <hint/> is a 1-6 word hint. Do not output
+        or `Gotcha` and <hint/> is a 1-6 word hint.
+
+        *Staleness override*: determine the coarse age <age-K/> (like
+        `2y`) of the last release from <updated-K/>. If <updated-K/> is
+        known and its age exceeds *twice* <getopt-option-staleness/>
+        months, *append* to <info-K/> the hint `Gotcha: stale/abandoned
+        -- last release <age-K/> ago`; else if its age exceeds
+        <getopt-option-staleness/> months, *append* to <info-K/> the
+        hint `Gotcha: aging -- last release <age-K/> ago`. Do not output
         anything.
     </step>
 
@@ -217,11 +232,11 @@ for the technology stack to *provide* the *needed functionality*
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT RANKING**:
 
-        | ⚑ *Component* | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
-        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
-        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  | ⚭ *Dep.*   |
+        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- | ---------: |
+        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> | <deps-1/>  |
         [...]
-        | **<name-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/> | <deps-N/>  |
         </template>
     </step>
 </flow>

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

@@ -8,6 +8,8 @@
 `ase-arch-discover`
     [`--help`|`-h`]
     [`--limit`|`-l=12`]
+    [`--staleness`|`-s=18`]
+    [`--small-scope`|`-S`]
     *functionality*
 
 ##  DESCRIPTION
@@ -20,9 +22,13 @@ The skill determines the project's technology stack (TypeScript,
 JavaScript, Kotlin, or Java), derives essential keywords from the
 requested functionality, queries the corresponding package registry
 (NPM or Maven Central), retrieves metadata (version, downloads,
-stars, dates) via the `ase_component_info` MCP tool, and reports
-the top-ranked components as a Markdown table together with a single
-distinguishing hint (USP, Crux, or Gotcha) per component.
+stars, dates, dependency count) via the `ase_component_info` MCP tool,
+and reports the top-ranked components as a Markdown table together with
+a single distinguishing hint (USP, Crux, or Gotcha) per component.
+
+The ranking penalizes *stale* components (last release older than the
+`--staleness` threshold) and, when the `--small-scope` option is given,
+demotes dependency-heavy components.
 
 ##  OPTIONS
 
@@ -31,6 +37,19 @@ distinguishing hint (USP, Crux, or Gotcha) per component.
     in the final ranking (default: 12). Raise it for a broader, more
     exhaustive survey, lower it for a quicker, narrower lookup.
 
+`--staleness`|`-s=18`:
+    The *staleness threshold* in months (default: 18). A component whose
+    last release is older than this is rank-penalized and flagged with an
+    `aging` gotcha; older than *twice* the threshold, it is penalized
+    harder and flagged as `stale/abandoned`.
+
+`--small-scope`|`-S`:
+    Treat the requested *functionality* as *small-scope* (default: off).
+    When enabled, the ranking demotes dependency-heavy components by a
+    dependency-weight penalty, since a dependency-free/hand-rolled
+    implementation is a realistic alternative for narrow, self-contained
+    functionality.
+
 ##  ARGUMENTS
 
 *functionality*:
@@ -57,6 +76,12 @@ Discover a broader set of up to 20 HTTP client components:
 ❯ /ase-arch-discover --limit 20 HTTP client with retries
 ```
 
+Discover HTTP clients, flagging any without a release in the last 12 months:
+
+```text
+❯ /ase-arch-discover --staleness 12 HTTP client with retries
+```
+
 ##  SEE ALSO
 
 [`ase-arch-analyze`](../ase-arch-analyze/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md).