@rse/ase 2.0.1 → 2.0.3

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-analyze
-argument-hint: "[--help|-h] [--performance|-p] [--security|-s] [--severity|-S=(LOW|MEDIUM|HIGH)] [--prefix|-P=<prefix>] [--staged] [--unstaged] [<source-reference>]"
+argument-hint: "[--help|-h] [--performance|-p] [--security|-s] [--severity|-S=(AUTO|LOW|MEDIUM|HIGH)] [--prefix|-P=<prefix>] [--staged] [--unstaged] [<source-reference>]"
 description: >
     Analyze the source code for problems in either the logic and
     semantics and its related control flow, performance and efficiency,
@@ -25,7 +25,7 @@ Analyze Source Code
 
 <expand name="getopt"
     arg1="ase-code-analyze"
-    arg2="--performance|-p --security|-s --severity|-S=(LOW|MEDIUM|HIGH) --prefix|-P= --staged --unstaged">
+    arg2="--performance|-p --security|-s --severity|-S=(AUTO|LOW|MEDIUM|HIGH) --prefix|-P= --staged --unstaged">
     $ARGUMENTS
 </expand>
 
@@ -56,10 +56,11 @@ problems in *performance* and *efficiency*, or problems in *security*.
 
 2.  <step id="STEP 2: Investigate Code Base">
 
-    <if condition="<ase-project-boxing/> is equal `black`">
+    <if condition="<ase-project-boxing/> is equal `black` and <getopt-option-severity/> is equal `AUTO`">
 
     The project source artifacts are classified as a *black box*, so
-    the user does *not* want them inspected or their problems surfaced.
+    the user does *not* want them inspected or their problems surfaced
+    (an *explicitly* given severity floor lifts this skip).
     *Skip* the entire investigation and analysis: do *not* invoke any
     `Bash`, `Glob`, or `Agent` tool and do *not* read any source, only
     output the following <template/> and then *SKIP* the remaining step
@@ -136,6 +137,14 @@ problems in *performance* and *efficiency*, or problems in *security*.
     <sources/> of individual source code files, expanding any
     directory or wildcard references with the `Glob` tool.
 
+    If <sources/> is empty (no *source-reference* given or none of it
+    resolvable), only output the following <template/> and then *STOP*
+    the entire flow (do not perform any further steps):
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-code-analyze**, ▶ ERROR: no source files to analyze -- give a *source-reference* or use `--staged`/`--unstaged`
+    </template>
+
     </else>
 
     Then partition <sources/>, preserving order, into at most *eight*
@@ -183,17 +192,24 @@ problems in *performance* and *efficiency*, or problems in *security*.
     do not overwrite each other.
 
     Before reporting, determine the *effective severity floor* <floor/>:
-    define the ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3, start from
-    <floor><getopt-option-severity/></floor> (default `LOW`), and - if
-    <ase-project-boxing/> is equal `grey` - raise <floor/> to `MEDIUM`
-    whenever its current rank is below `rank(MEDIUM)` (grey boxing
-    surfaces only *material* findings of severity `MEDIUM` and above).
+    define the ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3.
+
+    <if condition="<getopt-option-severity/> is equal `AUTO`">
+    Set <floor>MEDIUM</floor> if <ase-project-boxing/> is equal `grey`
+    (grey boxing surfaces only *material* findings of severity `MEDIUM`
+    and above), and <floor>LOW</floor> otherwise.
+    </if>
+    <else>
+    Set <floor><getopt-option-severity/></floor>: an *explicitly* given
+    severity floor always *wins* over the boxing, both over the `grey`
+    floor and over the `black` skip.
+    </else>
 
     Then *apply the effective severity floor* <floor/>: *Keep* a detected
     problem if and only if its `severity` field is `ACCEPTED` *or*
     `rank(severity)` is greater than or equal to `rank(<floor/>)`;
     *silently drop* all other problems (they are neither reported nor
-    persisted). With the default floor `LOW`, all problems are kept.
+    persisted). With the floor `LOW`, all problems are kept.
     `ACCEPTED` problems are *never* dropped.
 
     Then sort the surviving problems in <problems/> by their `severity`

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

@@ -9,7 +9,7 @@
     [`--help`|`-h`]
     [`--performance`|`-p`]
     [`--security`|`-s`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--prefix`|`-P` *prefix*]
     [`--staged`]
     [`--unstaged`]
@@ -32,11 +32,16 @@ The *analysis lens* depends on the selected options:
 
 The `--performance` and `--security` options are *mutually exclusive*.
 
-The `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`) option sets a *severity
-floor* (default `LOW`): problems below the chosen threshold are silently
-suppressed (neither reported nor persisted), ordered `LOW` < `MEDIUM` <
-`HIGH`. The default `LOW` keeps all problems; `ACCEPTED` problems are
-never suppressed. Surviving problems are reported in *descending
+The `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`) option sets a
+*severity floor* (default `AUTO`): problems below the chosen threshold
+are silently suppressed (neither reported nor persisted), ordered `LOW`
+< `MEDIUM` < `HIGH`. The default `AUTO` means `MEDIUM` for a project
+with `grey` boxing, no analysis at all for a project with `black`
+boxing, and `LOW` (keep all problems) otherwise; an explicitly given
+floor always wins over the boxing, i.e. it also analyzes a project with
+`black` boxing and, e.g. with `LOW`, reports all problems of a project
+with `grey` boxing. `ACCEPTED` problems are never suppressed. Surviving
+problems are reported in *descending
 severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED` - keeping the
 `file`/`line` order within the same severity - and are renumbered
 contiguously as `P<n>`, so `P1` is the most severe problem.

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

@@ -137,10 +137,11 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
         ⧉ **ASE**: ✪ skill: **ase-code-edit**, ⇌ issue: **<issue-id/>**, ▶ status: **issue retrieved**
         </template>
 
-        Otherwise, set <issue-id></issue-id> (empty) and only output the
-        following <template/>, then, under `--loop`, continue with the
-        *next* iteration at item 3.1 above, or, without `--loop`,
-        immediately *STOP* processing the entire current skill:
+        Otherwise, only output the following <template/>, then set
+        <issue-id></issue-id> and <query></query> (both empty, so the
+        next iteration asks for a fresh query), and then, under `--loop`,
+        continue with the *next* iteration at item 3.1 above, or, without
+        `--loop`, immediately *STOP* processing the entire current skill:
 
         <template>
         ⧉ **ASE**: ✪ skill: **ase-code-edit**, ▶ ERROR: no analyzer result exists for issue **<query/>**

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

@@ -65,7 +65,7 @@ information.
     should be clarified), `IMPLEMENTATION` (inner technical details,
     can be clarified), `REGRESSION` (what must not break, should be
     clarified), or `CONFIRMATION` (what proves the specified behavior,
-    should be clarified) -- and a 1-2 word `TOPIC` hint. The questions
+    should be clarified) -- and a 1-3 word `TOPIC` hint. The questions
     of a round are sorted by descending focus area importance
     (`DOMAIN`, `INTERFACE`, `ARCHITECTURE`, `IMPLEMENTATION`,
     `REGRESSION`, `CONFIRMATION`). Questions of focus area

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-lint
-argument-hint: "[--help|-h] [--auto|-a] [--severity|-S=(LOW|MEDIUM|HIGH)] [--include|-i=<aspect>[,...]] [--exclude|-e=<aspect>[,...]] [--staged] [--unstaged] [<source-reference>]"
+argument-hint: "[--help|-h] [--auto|-a] [--severity|-S=(AUTO|LOW|MEDIUM|HIGH)] [--include|-i=<aspect>[,...]] [--exclude|-e=<aspect>[,...]] [--staged] [--unstaged] [<source-reference>]"
 description: >
     Lint source code for potential code quality problems.
     Use when the user wants to "lint" or "check" source code.
@@ -23,7 +23,7 @@ Lint Source Code
 
 <expand name="getopt"
     arg1="ase-code-lint"
-    arg2="--auto|-a --severity|-S=(LOW|MEDIUM|HIGH) --include|-i=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --exclude|-e=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --staged --unstaged">
+    arg2="--auto|-a --severity|-S=(AUTO|LOW|MEDIUM|HIGH) --include|-i=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --exclude|-e=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --staged --unstaged">
     $ARGUMENTS
 </expand>
 
@@ -36,10 +36,11 @@ related to a set of code quality aspects.
 
 1.  <step id="STEP 1: Investigation">
 
-    <if condition="<ase-project-boxing/> is equal `black`">
+    <if condition="<ase-project-boxing/> is equal `black` and <getopt-option-severity/> is equal `AUTO`">
 
     The project source artifacts are classified as a *black box*, so
-    the user does *not* want them inspected or their problems surfaced.
+    the user does *not* want them inspected or their problems surfaced
+    (an *explicitly* given severity floor lifts this skip).
     *Skip* the entire investigation and reporting: do *not* invoke any
     `Bash`, `Glob`, or `Agent` tool and do *not* read any source, only
     output the following <template/> and then *SKIP* the remaining steps
@@ -51,6 +52,11 @@ related to a set of code quality aspects.
 
     </if>
 
+    Set <condensed>true</condensed> if <ase-project-boxing/> is equal
+    `grey` or `black` (the latter reached only under an explicitly given
+    severity floor), and <condensed>false</condensed> otherwise: a
+    *condensed* report suppresses the full unified diffs of STEP 3.
+
     First, determine the *effective aspect set* <aspects/>, i.e., the
     code quality aspects which are checked at all. For this, parse
     <getopt-option-include/> and <getopt-option-exclude/> as
@@ -135,6 +141,14 @@ related to a set of code quality aspects.
     list <sources/> of individual source code files, expanding any
     directory or wildcard references with the `Glob` tool.
 
+    If <sources/> is empty (no *source-reference* given or none of it
+    resolvable), only output the following <template/> and then *STOP*
+    the entire flow (do not perform any further steps):
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-code-lint**, ▶ ERROR: no source files to lint -- give a *source-reference* or use `--staged`/`--unstaged`
+    </template>
+
     </else>
 
     Then partition <sources/>, preserving order, into at most *eight*
@@ -160,24 +174,34 @@ related to a set of code quality aspects.
     parallel invocation is distinguishable in the progress display.
 
     Parse the result message of each `Agent` tool invocation as a JSON
-    array and concatenate all those arrays. Then *deduplicate* the
-    combined list: when two problems share the same `file`, `line`, and
+    array and concatenate all those arrays. Determine the *anchor* of
+    each problem as the `file` of its *first* `change-set` entry and the
+    `line` of that entry's *first* `change-hunks` entry, as problems carry
+    no top-level `file` and `line` fields. Then *deduplicate* the
+    combined list: when two problems share the same anchor and
     `aspect`, *silently drop* all but the first one (sub-agents may
     have read overlapping *related* files for comprehension). Finally
-    sort the list by `file` and then numerically by `line`, and set
-    <problems/> to that list.
+    sort the list by the anchor `file` and then numerically by the anchor
+    `line`, and set <problems/> to that list.
 
     Then determine the *effective severity floor* <floor/>: define the
-    ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3, start from
-    <floor><getopt-option-severity/></floor> (default `LOW`), and - if
-    <ase-project-boxing/> is equal `grey` - raise <floor/> to `MEDIUM`
-    whenever its current rank is below `rank(MEDIUM)` (grey boxing
-    surfaces only *material* findings of severity `MEDIUM` and above).
+    ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3.
+
+    <if condition="<getopt-option-severity/> is equal `AUTO`">
+    Set <floor>MEDIUM</floor> if <ase-project-boxing/> is equal `grey`
+    (grey boxing surfaces only *material* findings of severity `MEDIUM`
+    and above), and <floor>LOW</floor> otherwise.
+    </if>
+    <else>
+    Set <floor><getopt-option-severity/></floor>: an *explicitly* given
+    severity floor always *wins* over the boxing, both over the `grey`
+    floor and over the `black` skip.
+    </else>
 
     Then *apply the effective severity floor* <floor/>: *Keep* a problem
     in <problems/> if and only if its `severity` field is `ACCEPTED` *or*
     `rank(severity)` is greater than or equal to `rank(<floor/>)`;
-    *silently drop* all other problems. With the default floor `LOW`, all
+    *silently drop* all other problems. With the floor `LOW`, all
     problems are kept. `ACCEPTED` problems are *never* dropped.
 
     Finally, sort the surviving problems in <problems/> by their
@@ -259,7 +283,7 @@ related to a set of code quality aspects.
             1.  Set <file/>         to the `file`         field of <item/>.
                 Set <change-hunks/> to the `change-hunks` field of <item/>.
 
-                Unless <ase-project-boxing/> is equal `grey` (where the
+                Unless <condensed/> is equal `true` (where the
                 full unified diff is suppressed and no context lines are
                 rendered at all), *silently* read the current content of
                 <file/> with the `Read` tool - reusing the content read
@@ -273,7 +297,7 @@ related to a set of code quality aspects.
                 context lines of substep 2 below, so the rendered diff
                 shows real context even when a sub-agent supplied none.
 
-                Unless <ase-project-boxing/> is equal `grey` (where the
+                Unless <condensed/> is equal `true` (where the
                 full unified diff is suppressed and this per-file header is
                 unused), set <diff-file/> to the following <template/>:
 
@@ -317,8 +341,8 @@ related to a set of code quality aspects.
                     Keep the sub-agent supplied values only when
                     <file-lines/> is empty.
 
-                2.  *Skip* this substep entirely when <ase-project-boxing/>
-                    is equal `grey` - the full unified diff is suppressed
+                2.  *Skip* this substep entirely when <condensed/>
+                    is equal `true` - the full unified diff is suppressed
                     there, so none of the <hunk-body/>, <old-count/>,
                     <new-count/>, <old-start/>, or <new-start/> values
                     below are consumed (substep 4 builds only the condensed
@@ -373,10 +397,10 @@ related to a set of code quality aspects.
 
                     <template>`<file/>`:<line/></template>
 
-                4.  <if condition="<ase-project-boxing/> is equal `grey`">
+                4.  <if condition="<condensed/> is equal `true`">
 
-                    The full unified diff is *suppressed* under grey boxing
-                    (see substep 5 below), so *skip* the full-diff append
+                    The full unified diff is *suppressed* in a condensed
+                    report (see substep 5 below), so *skip* the full-diff append
                     and instead build only a *condensed* one-line
                     representation of this hunk: determine <old-snippet/>
                     as the *single-line* collapse of <old-text/> (join its
@@ -406,7 +430,7 @@ related to a set of code quality aspects.
 
                 </for>
 
-            3.  Unless <ase-project-boxing/> is equal `grey` (where
+            3.  Unless <condensed/> is equal `true` (where
                 <diff-file/> is unused), append <diff-file/> to <diff/>.
 
             </for>
@@ -422,10 +446,11 @@ related to a set of code quality aspects.
 
         5.  <if condition="<getopt-option-auto/> is not equal `true`">
 
-            <if condition="<ase-project-boxing/> is equal `grey`">
+            <if condition="<condensed/> is equal `true`">
 
-            The project source artifacts are classified as a *grey box*, so
-            the user does *not* want the full artifact internals surfaced:
+            The project source artifacts are classified as a *grey box* (or
+            *black box*), so the user does *not* want the full artifact
+            internals surfaced:
             *suppress* the full unified diff and instead show only the
             *condensed* one-line-per-hunk representation. Report the
             solution with the following <template/>:
@@ -494,8 +519,8 @@ related to a set of code quality aspects.
             -   <if condition="<result/> is 'ACCEPT'">
                 Invoke the `Edit` tool to apply the changes exactly
                 as given by the hunks of the current <change-set/>
-                (rendered as <diff/>, unless suppressed under grey
-                boxing). The operation will be auto-approved by the ASE
+                (rendered as <diff/>, unless suppressed in a condensed
+                report). The operation will be auto-approved by the ASE
                 `pre-tool-use` hook (which tracks the active skill),
                 so *no* interactive permission prompt will appear.
                 After applying the changes, just continue with the next

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

@@ -8,7 +8,7 @@
 `ase-code-lint`
     [`--help`|`-h`]
     [`--auto`|`-a`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--include`|`-i`=*aspect*[`,`...]]
     [`--exclude`|`-e`=*aspect*[`,`...]]
     [`--staged`]
@@ -60,11 +60,16 @@ the code, and comments contradicting the code.
     Automatically apply every proposed correction without asking the
     user via the interactive dialog.
 
--   `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
-    Set the *severity floor* (default `LOW`): findings below the chosen
+-   `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `AUTO`): findings below the chosen
     threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
-    `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
-    never suppressed. Surviving findings are reported in *descending
+    `HIGH`. The default `AUTO` means `MEDIUM` for a project with `grey`
+    boxing, no linting at all for a project with `black` boxing, and
+    `LOW` (keep all findings) otherwise; an explicitly given floor always
+    wins over the boxing, i.e. it also lints a project with `black`
+    boxing and, e.g. with `LOW`, acts on all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed. Surviving
+    findings are reported in *descending
     severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED`, keeping the
     `file`/`line` order within the same severity.
 

package/plugin/skills/ase-help-intent/data.md

@@ -175,7 +175,7 @@ Discover HTTP clients, flagging any without a release in the last 12 months:
     [`--help`|`-h`]
     [`--performance`|`-p`]
     [`--security`|`-s`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--prefix`|`-P` *prefix*]
     [`--staged`]
     [`--unstaged`]
@@ -198,11 +198,16 @@ The *analysis lens* depends on the selected options:
 
 The `--performance` and `--security` options are *mutually exclusive*.
 
-The `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`) option sets a *severity
-floor* (default `LOW`): problems below the chosen threshold are silently
-suppressed (neither reported nor persisted), ordered `LOW` < `MEDIUM` <
-`HIGH`. The default `LOW` keeps all problems; `ACCEPTED` problems are
-never suppressed. Surviving problems are reported in *descending
+The `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`) option sets a
+*severity floor* (default `AUTO`): problems below the chosen threshold
+are silently suppressed (neither reported nor persisted), ordered `LOW`
+< `MEDIUM` < `HIGH`. The default `AUTO` means `MEDIUM` for a project
+with `grey` boxing, no analysis at all for a project with `black`
+boxing, and `LOW` (keep all problems) otherwise; an explicitly given
+floor always wins over the boxing, i.e. it also analyzes a project with
+`black` boxing and, e.g. with `LOW`, reports all problems of a project
+with `grey` boxing. `ACCEPTED` problems are never suppressed. Surviving
+problems are reported in *descending
 severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED` - keeping the
 `file`/`line` order within the same severity - and are renumbered
 contiguously as `P<n>`, so `P1` is the most severe problem.
@@ -367,7 +372,7 @@ information.
     should be clarified), `IMPLEMENTATION` (inner technical details,
     can be clarified), `REGRESSION` (what must not break, should be
     clarified), or `CONFIRMATION` (what proves the specified behavior,
-    should be clarified) -- and a 1-2 word `TOPIC` hint. The questions
+    should be clarified) -- and a 1-3 word `TOPIC` hint. The questions
     of a round are sorted by descending focus area importance
     (`DOMAIN`, `INTERFACE`, `ARCHITECTURE`, `IMPLEMENTATION`,
     `REGRESSION`, `CONFIRMATION`). Questions of focus area
@@ -627,7 +632,7 @@ Get insights into a specific subsystem:
 `ase-code-lint`
     [`--help`|`-h`]
     [`--auto`|`-a`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--include`|`-i`=*aspect*[`,`...]]
     [`--exclude`|`-e`=*aspect*[`,`...]]
     [`--staged`]
@@ -679,11 +684,16 @@ the code, and comments contradicting the code.
     Automatically apply every proposed correction without asking the
     user via the interactive dialog.
 
--   `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
-    Set the *severity floor* (default `LOW`): findings below the chosen
+-   `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `AUTO`): findings below the chosen
     threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
-    `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
-    never suppressed. Surviving findings are reported in *descending
+    `HIGH`. The default `AUTO` means `MEDIUM` for a project with `grey`
+    boxing, no linting at all for a project with `black` boxing, and
+    `LOW` (keep all findings) otherwise; an explicitly given floor always
+    wins over the boxing, i.e. it also lints a project with `black`
+    boxing and, e.g. with `LOW`, acts on all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed. Surviving
+    findings are reported in *descending
     severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED`, keeping the
     `file`/`line` order within the same severity.
 
@@ -1169,11 +1179,10 @@ Shorten a document to at most 250 words unattended:
 
 The `ase-help-skill` skill renders the *manual page* (`help.md`) of the
 ASE skill addressed by *skill-name*. The page is emitted verbatim,
-framed between a `( HELP )` header and footer rule.
+framed between a `MANUAL PAGE` header and footer rule.
 
 The *skill-name* is resolved against a *catalog* of all ASE skills --
-one `name: purpose` entry per skill, generated into
-`skills/ase-help-skill/data.md` by `npm start build` in `plugin/`.
+one `name: purpose` entry per skill, grouped by skill category.
 Before resolving, any leading `/` and `ase:` prefix is stripped, so
 `ase-code-lint`, `/ase-code-lint`, and `ase:ase-code-lint` are
 equivalent. Resolution then proceeds in three tiers, each tried only if
@@ -1191,7 +1200,7 @@ most nine answer lines, a broader abbreviation such as `task` shows the
 first nine candidates and states how many exist in total.
 
 If *skill-name* is omitted, the whole catalog is rendered as a
-browsable `Skill`/`Purpose` table instead.
+browsable list, grouped by skill category, instead.
 
 The skill exposes *no* option flags beyond `--help`/`-h`.
 
@@ -2062,9 +2071,11 @@ complete, unmodified individual responses.
 -   `--models`|`-m` *model*[,...]:
     Restrict the *foreign* LLMs that are queried to the given
     comma-separated list of *model* tokens. Recognized tokens are
-    `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, and `qwen`,
-    where `all` selects every model. The default is `all`. Models that
-    are not selected (or not available) are *silently skipped*.
+    `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, `qwen`,
+    `claude`, `codex`, and `copilot`, where `all` selects every API-based
+    model, but *not* the harness-based `claude`, `codex`, and `copilot`
+    models, which are queried only when given explicitly. The default
+    is `all`. Models that are not selected (or not available) are *silently skipped*.
     Anthropic Claude (the skill itself) is *always* included,
     independent of this option.
 
@@ -2597,8 +2608,8 @@ changes in the Git *index*.
 Each entry is formatted as `<change-type> [<artifact-kind>]: <summary>`
 where *change-type* is one of `FEATURE`, `IMPROVEMENT`, `BUGFIX`,
 `UPDATE`, `CLEANUP`, or `REFACTOR`, and *artifact-kind* is one or more
-comma-separated *artifact class* tags out of `spec`, `arch`, `code`,
-`docs`, `infr`, or `othr`. Entries are grouped and sorted by this
+comma-separated *artifact class* tags out of `spec`, `code`, `docs`,
+`infr`, or `othr`. Entries are grouped and sorted by this
 prefix. The date in the section header is also updated to the current
 date.
 
@@ -3169,7 +3180,9 @@ before it is committed or merged.
     threshold are suppressed, ordered `LOW` < `MEDIUM` < `HIGH`. The
     default `AUTO` means `MEDIUM` for a project with `grey` boxing and
     `LOW` (keep all findings) otherwise; an explicitly given floor always
-    wins over the boxing. `ACCEPTED` findings are never suppressed, and
+    wins over the boxing, i.e. it also reviews a project with `black`
+    boxing and, e.g. with `LOW`, shows all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed, and
     the number of suppressed findings is always reported. Surviving
     findings are rendered in *descending severity* order `HIGH`,
     `MEDIUM`, `LOW`, `ACCEPTED`. The floor only affects the rendered
@@ -3392,7 +3405,8 @@ approach selection close with an `EDIT TODO` box showing the established
 
 The change set stays strictly restricted to the `SPEC` artifacts -- the
 artifact kinds `CODE`, `DOCS`, `TASK`, `INFR`, and `OTHR` are never
-touched. Every generated artifact carries the current `Created:` and
+touched, except for an entry in an already existing `CHANGELOG.md`
+file. Every generated artifact carries the current `Created:` and
 `Modified:` timestamps, and every changed artifact gets its `Modified:`
 timestamp refreshed.
 
@@ -3800,13 +3814,13 @@ a unified diff instead.
     as nothing is written to disk.
 
 -   `--target`|`-t` *target*[,...]:
-    The comma-separated list of artifact kinds to update. Required (the
-    skill errors out on an empty target).
+    The comma-separated list of artifact kinds to update (default:
+    `CODE,DOCS,INFR,OTHR`). An empty target lets the skill error out.
 
 -   `--source`|`-s` *source*[,...]:
     The comma-separated list of artifact kinds to update *from*. The
-    special value `auto` resolves to all recognized kinds except those
-    in *target*.
+    special value `auto` (the default) resolves to all recognized kinds
+    except those in *target*.
 
 ##  ARGUMENTS
 
@@ -4711,7 +4725,7 @@ in state `[-]` (cancelled) or `[>]` (deferred) are never questioned.
 ##  ARGUMENTS
 
 -   *id*:
-    Grill the task with the unique identifier *id* (default: `default`).
+    Grill the task with the unique identifier *id* (default: the current task).
     The skill accepts *only* an optional *id* argument and never a
     free-text instruction.
 
@@ -4923,6 +4937,22 @@ the entire verification phase is strictly skipped: no build, tests,
 linter, type-checker, or program execution is performed once the
 source files have been modified.
 
+The implementation runs to *completion*: the skill never concludes
+while any point of the plan is still unimplemented, neither because the
+change set grew large nor because an open question stands in the way.
+Undecided details and defensible alternatives are therefore *decided by
+the skill itself*, guided by the surrounding artifacts and the
+internalized tenets, instead of interrupting the run with a question.
+Once the change set is applied, the run closes with up to two boxed
+summaries: `OPEN POINTS` lists everything now waiting for the user --
+points left unimplemented on a *genuine blocker* no assumption can
+bridge, follow-ups deliberately left out of scope with their reason,
+and results needing review -- and `DECISIONS` lists each decision the
+skill took on its own together with its rationale, so it can be
+revisited or overruled. Either box is omitted entirely when it has no
+content; a run which implemented every point and decided nothing on its
+own emits no box at all.
+
 After implementation, the user is asked whether to stop, hand off to
 `ase-task-edit`, hand off to `ase-task-integrate`, or delete the task
 plan, unless `--next` pre-selects this choice.
@@ -5275,8 +5305,8 @@ DEFERRED     INTEGRATING INTEGRATED CANCELLED
 -   `--include`|`-i`=*state*[`,`...]:
     Restrict the listed task plans to the given comma-separated list of
     lifecycle states (e.g. `IMPLEMENTING,STALLED`). Without this option,
-    all states are listed. The `none` sentinel selects no state at all,
-    the `finished` sentinel selects the finished states.
+    all states are listed. The `none` sentinel (the default) imposes no
+    restriction, the `finished` sentinel selects the finished states.
 
 -   `--exclude`|`-e`=*state*[`,`...]:
     Remove the given comma-separated list of lifecycle states from the

package/plugin/skills/ase-help-skill/help.md

@@ -13,11 +13,10 @@
 
 The `ase-help-skill` skill renders the *manual page* (`help.md`) of the
 ASE skill addressed by *skill-name*. The page is emitted verbatim,
-framed between a `( HELP )` header and footer rule.
+framed between a `MANUAL PAGE` header and footer rule.
 
 The *skill-name* is resolved against a *catalog* of all ASE skills --
-one `name: purpose` entry per skill, generated into
-`skills/ase-help-skill/data.md` by `npm start build` in `plugin/`.
+one `name: purpose` entry per skill, grouped by skill category.
 Before resolving, any leading `/` and `ase:` prefix is stripped, so
 `ase-code-lint`, `/ase-code-lint`, and `ase:ase-code-lint` are
 equivalent. Resolution then proceeds in three tiers, each tried only if
@@ -35,7 +34,7 @@ most nine answer lines, a broader abbreviation such as `task` shows the
 first nine candidates and states how many exist in total.
 
 If *skill-name* is omitted, the whole catalog is rendered as a
-browsable `Skill`/`Purpose` table instead.
+browsable list, grouped by skill category, instead.
 
 The skill exposes *no* option flags beyond `--help`/`-h`.
 

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

@@ -38,6 +38,15 @@ by querying *multiple* AIs for an *optimal consensus*.
 
 1.  <step id="STEP 1: Preview Own Answer">
 
+    <if condition="<getopt-arguments/> is empty">
+    Only output the following <template/> and then immediately *STOP*
+    processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-meta-quorum**, ▶ ERROR: expected a `<question>` argument
+    </template>
+    </if>
+
     The user-selectable foreign models are restricted by the
     `--models`/`-m` option, parsed into <getopt-option-models/>
     as a comma-separated list of model tokens. The getopt parser

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

@@ -29,9 +29,11 @@ complete, unmodified individual responses.
 -   `--models`|`-m` *model*[,...]:
     Restrict the *foreign* LLMs that are queried to the given
     comma-separated list of *model* tokens. Recognized tokens are
-    `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, and `qwen`,
-    where `all` selects every model. The default is `all`. Models that
-    are not selected (or not available) are *silently skipped*.
+    `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, `qwen`,
+    `claude`, `codex`, and `copilot`, where `all` selects every API-based
+    model, but *not* the harness-based `claude`, `codex`, and `copilot`
+    models, which are queried only when given explicitly. The default
+    is `all`. Models that are not selected (or not available) are *silently skipped*.
     Anthropic Claude (the skill itself) is *always* included,
     independent of this option.
 

package/plugin/skills/ase-meta-workflow/sample.md

@@ -17,10 +17,12 @@ Analyze and Resolve Source Code Problems
 
 <expand name="getopt"
     arg1="optimizer"
-    arg2="--id|-i <id>=optimizer">
+    arg2="--id|-i=optimizer">
     $ARGUMENTS
 </expand>
 
+Set <id><getopt-option-id/></id>.
+
 <flow>
 
 1.  <step id="STEP 1: Analyze Code">
@@ -29,7 +31,7 @@ Analyze and Resolve Source Code Problems
         subagent_type="general-purpose"
         run_in_background=false>
 
-        Run <skill name="ase-code-analyze" args="--prefix <id/> <getopt-arguments/>"/>
+        Run <skill name="ase:ase-code-analyze" args="--prefix <id/> <getopt-arguments/>"/>
 
     </agent>
 
@@ -39,7 +41,7 @@ Analyze and Resolve Source Code Problems
 
     <parallel>
 
-    For each `P<n/>` in the result set, in ascending order and strictly *one at a time*:
+    For each `P<n/>` in the result set, in ascending order:
 
     1.  Call the Agent: