@rse/ase 2.0.2 → 2.0.3

package/dst/man/ase-task-status.1

@@ -1,4 +1,4 @@
-.TH "ASE-TASK-STATUS" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-TASK-STATUS" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-task-status\fR - Get or Set the Lifecycle Status of a Task
 .SH "SYNOPSIS"

package/dst/man/ase-task-store.1

@@ -1,4 +1,4 @@
-.TH "ASE-TASK-STORE" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-TASK-STORE" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-task-store\fR - Manage the per-user task store REST API server
 .SH "SYNOPSIS"

package/dst/man/ase-task-view.1

@@ -1,4 +1,4 @@
-.TH "ASE-TASK-VIEW" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-TASK-VIEW" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-task-view\fR - Show a Task Plan in the Pager
 .SH "SYNOPSIS"

package/dst/man/ase-task.1

@@ -1,4 +1,4 @@
-.TH "ASE-TASK" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-TASK" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-task\fR - Manage Persisted Task Plans
 .SH "SYNOPSIS"

package/dst/man/ase-util-compat.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-COMPAT" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-COMPAT" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-compat\fR - Output Expected Probe Values of the Compatibility Self-Test
 .SH "SYNOPSIS"

package/dst/man/ase-util-diagram.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-DIAGRAM" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-DIAGRAM" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-diagram\fR - Render Mermaid or D2 Diagrams as Unicode/ASCII Art or SVG
 .SH "SYNOPSIS"

package/dst/man/ase-util-meta.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-META" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-META" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-meta\fR - Output Plugin Meta Files
 .SH "SYNOPSIS"

package/dst/man/ase-util-metric.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-METRIC" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-METRIC" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-metric\fR - Measure the Length Metrics of a Text
 .SH "SYNOPSIS"

package/dst/man/ase-util-mint.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-MINT" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-MINT" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-mint\fR - Mint Hash-Derived Identifiers
 .SH "SYNOPSIS"

package/dst/man/ase-util-worktree.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL-WORKTREE" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL-WORKTREE" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util-worktree\fR - Resolve the ASE Worktree Directories
 .SH "SYNOPSIS"

package/dst/man/ase-util.1

@@ -1,4 +1,4 @@
-.TH "ASE-UTIL" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE-UTIL" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase-util\fR - Utility Commands
 .SH "SYNOPSIS"

package/dst/man/ase.1

@@ -1,4 +1,4 @@
-.TH "ASE" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
+.TH "ASE" "1" "October 2026" "2.0.3" "Agentic Software Engineering (ASE)"
 .SH "NAME"
 \fBase\fR - Agentic Software Engineering (ASE)
 .SH "SYNOPSIS"

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "https://ase.tools",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "https://github.com/rse/ase/issues" },
-    "version":                              "2.0.2",
+    "version":                              "2.0.3",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

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

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

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

package/plugin/meta/ase-skill.md

@@ -306,6 +306,13 @@ Artifact Boxing Transparency
     above. Where no such branches or instructions exist, the decisions
     above apply.
 
+-   *IMPORTANT*: Severity rule: an *explicitly* given severity floor
+    (option `--severity`|`-S` other than `AUTO`) of a finding-producing
+    skill *overrules* the boxing for *which* findings are inspected and
+    acted on: it lifts the `black` skip and the `grey` floor `MEDIUM`,
+    so e.g. `-S LOW` acts on *all* findings of severity `LOW` and above.
+    The boxing still governs the *internals exposed* of each finding.
+
 Guidance Hint Level
 -------------------
 

package/plugin/mods/ase-mods.ts

@@ -236,7 +236,7 @@ export const register: Register = (on, options) => {
     /*  the last known width of the terminal, the already seen tables, the
         latest (still unanswered) table, the picks and the selected question of the
         still unsubmitted prompt, and the frozen picks of the already answered tables  */
-    let columns = 80
+    let columns  = 80
     const seen   = new Set<string>()
     let latest: string | undefined
     let picks    = new Map<number, string>()
@@ -326,22 +326,25 @@ export const register: Register = (on, options) => {
         }
 
         /*  draw a line of a cell: its styled runs, padded to the column width  */
-        const paint = (chars: Char[], columns: number): (string | RenderElement)[] => [
+        const paint = (chars: Char[], span: number): (string | RenderElement)[] => [
             ...split(chars).map(({ text, bold, color }) =>
                 bold || color !== undefined ? Text({ bold, color, children: text }) : text),
-            " ".repeat(Math.max(0, columns - width(chars)))
+            " ".repeat(Math.max(0, span - width(chars)))
         ]
 
         /*  insert the number of a clicked question or the short response of a clicked
             answer into the prompt and refresh the picks and the selection from it  */
         const press = (number: number, letter?: string) => () => {
-            void $.prompt.read()
+            $.prompt.read()
                 .then(({ text }) => $.prompt.fill({ text: insert(text, number, letter) }))
                 .then((box) => {
                     picks    = pick(box.text)
                     selected = select(box.text)
                     $.ui.invalidate("ui.render")
                 })
+                .catch(() => {
+                    /*  ignore a prompt which is no longer accessible  */
+                })
         }
 
         /*  draw a line of a cell: in the latest table as the styled text inside a
@@ -351,11 +354,11 @@ export const register: Register = (on, options) => {
             the run's bold style, but not its color, as its hover style, because the
             engine leaves the space cells uncolored) on top of it; otherwise as
             styled text only  */
-        const draw = (chars: Char[], columns: number, group: string, line: number,
+        const draw = (chars: Char[], span: number, group: string, line: number,
             onPress: () => void): RenderElement[] => {
             const w = width(chars)
             if (e.requestId !== latest || w === 0)
-                return [ Text({ children: paint(chars, columns) }) ]
+                return [ Text({ children: paint(chars, span) }) ]
             const buttons = split(chars).map(({ text, bold }, r) =>
                 Button({ key: `${group}/${line}/${r}`, label: text, plain: true, onPress,
                     hover: { scope: group, inverse: true, bold } }))
@@ -365,7 +368,7 @@ export const register: Register = (on, options) => {
                     Box({ position: "absolute", top: 0, left: 0, display: "none",
                         hover: { scope: group, display: "flex" }, flexDirection: "row", children: buttons })
                 ] }),
-                Text({ children: " ".repeat(Math.max(0, columns - w)) })
+                Text({ children: " ".repeat(Math.max(0, span - w)) })
             ]
         }
 

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
@@ -191,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-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
@@ -179,16 +185,23 @@ related to a set of code quality aspects.
     `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
@@ -270,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
@@ -284,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/>:
 
@@ -328,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
@@ -384,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
@@ -417,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>
@@ -433,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/>:
@@ -505,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.
@@ -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.
 
@@ -3170,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

package/plugin/skills/ase-repo-review/SKILL.md

@@ -224,11 +224,12 @@ Procedure
 
 2.  <step id="STEP 2: Review 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 the changes scrutinized or their
-    findings surfaced. *Skip* the entire review investigation: do
+    findings surfaced (an *explicitly* given severity floor lifts this
+    skip). *Skip* the entire review investigation: do
     *not* invoke the `Agent` tool and do *not* read any change, set
     <findings/> to the *empty* list, set <hidden/> to `0`, set
     <verdict/> to `SKIPPED (boxing: black)`, set <summary/> to a
@@ -288,7 +289,8 @@ Procedure
     <else>
     Set <floor><getopt-option-severity/></floor> and
     <floor-origin>--severity <getopt-option-severity/></floor-origin>:
-    an *explicitly* given severity floor always *wins* over the boxing.
+    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 finding

package/plugin/skills/ase-repo-review/help.md

@@ -75,7 +75,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