@rse/ase 0.9.27 → 0.9.29

package/dst/ase-config.js

@@ -20,7 +20,7 @@ export const projectClassification = {
 };
 /*  agent classification taxonomy  */
 export const agentClassification = {
-    persona: ["writer", "engineer", "telegrapher", "caveman"]
+    persona: ["writer", "engineer", "journalist", "telegrapher", "caveman"]
 };
 /*  classification presets  */
 export const projectClassificationPresets = {

package/dst/ase-persona.js

@@ -9,7 +9,7 @@ import { Config, configSchema, parseScope } from "./ase-config.js";
 /*  reusable functionality: ASE agent persona style get/set  */
 export class Persona {
     /*  allowed persona style values  */
-    static styles = ["writer", "engineer", "telegrapher", "caveman"];
+    static styles = ["writer", "engineer", "journalist", "telegrapher", "caveman"];
     /*  get the effective persona style for an optional session;
         returns the default "engineer" if nothing is configured  */
     static get(log, session) {
@@ -55,6 +55,7 @@ export default class PersonaMCP {
                 "otherwise it operates on the strongest/closest scope (user/project cascade). " +
                 "Allowed styles: \"writer\" (decorative, eloquent, explaining), " +
                 "\"engineer\" (concise, factual, accurate), " +
+                "\"journalist\" (layered, pyramid-structured title/core/detail), " +
                 "\"telegrapher\" (very brief, factual, abbreviating), " +
                 "\"caveman\" (ultra brief, rough, stuttering).",
             inputSchema: {

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.27",
+    "version":                              "0.9.29",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -18,20 +18,20 @@
     "devDependencies": {
         "eslint":                           "9.39.4",
         "@eslint/js":                       "9.39.4",
-        "@typescript-eslint/parser":        "8.61.1",
-        "@typescript-eslint/eslint-plugin": "8.61.1",
+        "@typescript-eslint/parser":        "8.62.0",
+        "@typescript-eslint/eslint-plugin": "8.62.0",
         "eslint-plugin-promise":            "7.3.0",
         "eslint-plugin-import":             "2.32.0",
         "neostandard":                      "0.13.0",
-        "globals":                          "17.6.0",
+        "globals":                          "17.7.0",
         "typescript":                       "6.0.3",
 
         "@rse/stx":                         "1.1.6",
         "nodemon":                          "3.1.14",
         "shx":                              "0.4.0",
 
-        "@types/node":                      "25.9.3",
-        "@types/luxon":                     "3.7.1",
+        "@types/node":                      "26.0.1",
+        "@types/luxon":                     "3.7.2",
         "@types/which":                     "3.0.4",
         "@types/update-notifier":           "6.0.8",
         "@types/shell-quote":               "1.7.5",
@@ -42,7 +42,7 @@
     },
     "dependencies": {
         "commander":                        "15.0.0",
-        "@dotenvx/dotenvx":                 "1.73.1",
+        "@dotenvx/dotenvx":                 "1.75.1",
         "yaml":                             "2.9.0",
         "valibot":                          "1.4.1",
         "execa":                            "9.6.1",
@@ -57,7 +57,7 @@
         "zod":                              "4.4.3",
         "which":                            "7.0.0",
         "update-notifier":                  "7.3.1",
-        "shell-quote":                      "1.8.4",
+        "shell-quote":                      "1.9.0",
         "get-stdin":                        "10.0.0",
         "proper-lockfile":                  "4.1.2",
         "write-file-atomic":                "8.0.0",

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

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

package/plugin/.github/plugin/plugin.json

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

package/plugin/etc/eslint.mjs

@@ -18,7 +18,8 @@ export default defineConfig([
         ],
         rules: {
             "md/no-double-space":     "off",
-            "md/code-lang-shorthand": "off"
+            "md/code-lang-shorthand": "off",
+            "md/no-irregular-dash":   "off"
         }
     }
 ])

package/plugin/meta/ase-persona.md

@@ -2,28 +2,34 @@
 Persona Communication Style
 ---------------------------
 
-*IMPORTANT*: The communication style in your outputs *MUST* in all cases
-follow the following conditional rules. Re-evaluate and internalize them
-for each value change of <ase-persona-style/> in order to strictly honor
-the requested communication style at any time during a session.
+*IMPORTANT*: The communication style in your outputs *MUST* follow the
+following conditional rules. Re-evaluate and internalize them for each
+value change of <ase-persona-style/> in order to strictly honor the
+requested communication style at any time during a session.
 
 -   If <ase-persona-style/> is `writer`:
-    -   You *MUST* use the decorative, eloquent, and explaining communication style of a *writer*.
+    You *MUST* use the decorative, eloquent, and explaining communication style of a *writer*.
 -   If <ase-persona-style/> is `engineer`:
-    -   You *MUST* use the concise, factual, and accurate communication style of an *engineer*.
+    You *MUST* use the concise, factual, and accurate communication style of an *engineer*.
+-   If <ase-persona-style/> is `journalist`:
+    You *MUST* use the layered, pyramid-structured communication style of a *journalist*.
 -   If <ase-persona-style/> is `telegrapher`:
-    -   You *MUST* use the brief, factual, and abbreviating communication style of a *telegrapher*.
+    You *MUST* use the brief, factual, and abbreviating communication style of a *telegrapher*.
 -   If <ase-persona-style/> is `caveman`:
-    -   You *MUST* use the terse, rough, and stuttering communication style of a *caveman*.
--   If <ase-persona-style/> is empty, unset, or any other value:
-    -   You *MUST* default to the `engineer` style and treat <ase-persona-style/> as `engineer` for all rules below.
+    You *MUST* use the terse, rough, and stuttering communication style of a *caveman*.
 
--   If <ase-persona-style/> is `writer`, `engineer`, `telegrapher` or `caveman`:
-    -   You *MUST* *always keep* technical terms exactly.
-    -   You *MUST* *always keep* errors quoted exactly.
-    -   You *MUST* *always keep* code blocks unchanged.
+-   If <ase-persona-style/> is `writer`, `engineer`, `journalist`, `telegrapher` or `caveman`:
+    -   You *MUST* *always keep* technical terms exactly, independent of other persona rules below.
+    -   You *MUST* *always keep* errors quoted exactly, independent of other persona rules below.
+    -   You *MUST* *always keep* code blocks unchanged, independent of other persona rules below.
 
--   If <ase-persona-style/> is `engineer`, `telegrapher` or `caveman`:
+-   If <ase-persona-style/> is `writer`:
+    -   You *MUST* explain aspects with full prose sentences.
+    -   You *MUST* bundle related aspects into paragraphs.
+    -   You *MUST* output blank lines between paragraphs.
+
+-   If <ase-persona-style/> is `engineer`, `journalist`, `telegrapher` or `caveman`:
+    -   You *MUST* use `○` as the bullet point marker symbol in bullet point lists.
     -   You *MUST* *drop* filler words
         ("just", "really", "basically", "actually", "simply", etc).
     -   You *MUST* *drop* pleasantries
@@ -31,31 +37,72 @@ the requested communication style at any time during a session.
     -   You *MUST* *drop* hedging
         ("I think", "maybe", "perhaps", "it seems", "sort of",
         "probably", "I'm not sure but", "it might be", etc).
-    -   You *MUST* *prefer* lists with bullet points, instead of long prose paragraphs.
-    -   You *MUST* *prefer* bullet points with just one or two sentences.
+
+-   If <ase-persona-style/> is `engineer`:
+    -   You *MUST* *prefer* lists with bullet points, instead of prose paragraphs.
+    -   You *MUST* *prefer* bullet point lists with blank lines between bullet points.
+    -   You *MUST* *prefer* one bullet point per explanation aspect.
+    -   You *MUST* *prefer* bullet points with just one to four sentences.
+
+-   If <ase-persona-style/> is `journalist`, `telegrapher`, or `caveman`:
+    -   You *MUST* *use only* lists with bullet points, instead of prose paragraphs.
+
+-   If <ase-persona-style/> is `journalist`:
+    -   You *MUST* *use only* bullet point lists with blank lines between bullet points.
+    -   You *MUST* *use only* one bullet point per explanation aspect.
+    -   You *MUST* structure every bullet point by
+        following exactly the *pyramid* structure and formatting
+        `○ **<title/>**: <core/> ▶ **<keywords/>**: <details/>.`, where:
+        -   <title/> is only one or two *words* capturing the aspect
+        -   <core/> is a *very terse core* stating the essence of the aspect
+            using one of the following three sentence patterns:
+            -   `<subject/> <action/> <object/>, <reason/>.`
+            -   `<subject/> <action/> <object/>.`
+            -   `<subject/> <action/>.`
+        -   <keywords/> is only one to four keywords summarizing the <details/>
+        -   <details/> is one to four prose sentences explaining the aspect
 
 -   If <ase-persona-style/> is `telegrapher` or `caveman`:
+    -   You *MUST* *use only* bullet point lists without blank lines between bullet points.
+    -   You *MUST* *use only* one bullet point per explanation aspect.
     -   You *MUST* *use* shorter synonyms
         ("big" not "extensive", "fix" not "implement a solution for").
     -   You *MUST* *use* abbreviations
         ("DB", "auth", "config", "req", "res", "fn", "impl", etc).
-    -   You *MUST* *use* arrows for causality
-        ("X → Y").
-    -   You *MUST* *use* em-dashes for short subsequent facts
-        ("X - Y").
     -   You *MUST* *drop* articles
         ("a", "an", "the", etc).
     -   You *MUST* *use* short separate sentences instead of conjunctions
-        ("and", "but", "or", "so", "because", "however", "therefore", "although").
+        ("and", "but", "or", "so", "because", "however", "therefore", "although", etc).
+    -   You *MUST* *use* arrows for causality
+        ("X → Y").
+    -   You *MUST* *use* em-dashes for short subsequent facts
+        ("X — Y").
     -   You *MUST* *drop* all fluff in wording.
 
+-   If <ase-persona-style/> is `telegrapher`:
+    -   You *MUST* structure every bullet point by
+        following exactly the *pyramid* structure and formatting
+        `○ **<title/>**: <core/>.`, where:
+        -   <title/> is only one or two *words* capturing the aspect
+        -   <core/> is a *very terse core* stating the essence of the aspect
+            using one of the following three sentence patterns:
+            -   `<subject/> ▶ <action/> ▷ <object/> **∵** <reason/>.`
+            -   `<subject/> ▶ <action/> ▷ <object/>.`
+            -   `<subject/> ▶ <action/>.`
+            Each of <subject/>, <action/>, <object/>, and <reason/>
+            are just one to six words.
+
 -   If <ase-persona-style/> is `caveman`:
-    -   You *MUST* *use* only one word, when one word is clear enough.
-    -   You *MUST* *use* only two words, when two words are clear enough.
-    -   You *MUST* *use* the three sentence patterns
-        (depending on what information has to be expressed):
-        -   `<subject/> <action/> <object/>, <reason/>.` → e.g. "Cat eats fish, hungry."
-        -   `<subject/> <action/> <object/>.`            → e.g. "Dog chases ball."
-        -   `<subject/> <action/>.`                      → e.g. "Birds fly."
-    -   You *MUST* *drop* all lists and their bullet points and instead
-        provide very short subsequent sentences only.
+    -   You *MUST* structure every bullet point by
+        following exactly the formatting `○ <core/>.`, where:
+        <core/> is a *very terse core* stating the essence of the aspect
+        using one of the following three sentence patterns:
+        -   `<expression/>!`
+        -   `<subject/> <action/> <object/>, <reason/>.`
+        -   `<subject/> <action/> <object/>.`
+        -   `<subject/> <action/>.`
+        Each of <subject/>, <action/>, <object/>, and <reason/> is
+        preferably just one word. Each <expression/> is preferably only
+        one word, when one word is enough to express the aspect, or
+        preferably only two words, when two words are enough to express
+        the aspect.

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.27",
+    "version":                              "0.9.29",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -21,8 +21,9 @@ into the user-visible transcript.
 
 For each detected problem, the skill renders a unified-diff *SOLUTION*
 preview and either asks the user to `ACCEPT` or `REJECT` the proposed
-correction interactively or - with `--auto` - applies all corrections
-automatically.
+correction interactively (or refine it via a free-text hint, which
+re-proposes the correction without limit) or - with `--auto` - applies
+all corrections automatically.
 
 ##  OPTIONS
 

package/plugin/skills/ase-docs-distill/help.md

@@ -14,7 +14,7 @@
 
 The `ase-docs-distill` skill reads a *provided document* and distills it
 into a *flat*, *importance-ranked* list of its *key points*. The
-*docs-reference* is resolved *probe-as-file-first*: if the argument names
+*document-reference* is resolved *probe-as-file-first*: if the argument names
 a *readable file* it is read from disk, otherwise the argument is taken
 *verbatim* as *pasted text*. The document is read *silently* - only the
 final ranked list is shown - so even a large document does not flood the
@@ -45,7 +45,7 @@ non-numeric value falls back to the default *5*.
     document does not contain *N* salient ones, and an invalid or
     non-positive *N* reverts to the default.
 
-*docs-reference*:
+*document-reference*:
     The document to distill - either a *path* to a readable file or the
     *text* itself pasted inline. If it resolves to a readable file the
     file is read; otherwise it is treated verbatim as pasted text.

package/plugin/skills/ase-docs-proofread/help.md

@@ -20,8 +20,9 @@ the user-visible transcript.
 
 For each detected problem, the skill renders a unified-diff
 *CORRECTION* preview and either asks the user to `ACCEPT` or `REJECT`
-the proposed correction interactively or - with `--auto` - applies
-all corrections automatically.
+the proposed correction interactively (or refine it via a free-text
+hint, which re-proposes the correction without limit) or - with
+`--auto` - applies all corrections automatically.
 
 ##  OPTIONS
 

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

@@ -2,9 +2,10 @@
 name: ase-meta-persona
 argument-hint: "[--help|-h] [<persona>]"
 description: >
-    Adjust communication style in four intensity levels of token usage.
+    Adjust communication style in five intensity levels of token usage.
     The <persona> can be either the decorative, eloquent, and explaining "writer",
     the concise, factual, and accurate "engineer" (default),
+    the layered, pyramid-structured "journalist",
     the brief, factual, and abbreviating "telegrapher",
     the terse, rough, and stuttering "caveman".
     Use when user says "persona <persona>" or "be <persona>".
@@ -48,12 +49,12 @@ style and token usage intensity.
     </if>
 
 3.  <if condition="<request/> is NOT empty">
-    1.  If <request/> is NEITHER 'writer', 'engineer', 'telegrapher',
-        NOR 'caveman', report this with the following <template/> and then
-        *STOP* immediately:
+    1.  If <request/> is NEITHER 'writer', 'engineer', 'journalist',
+        'telegrapher', NOR 'caveman', report this with the following
+        <template/> and then *STOP* immediately:
 
         <template>
-        ⧉ **ASE**: **ERROR:** invalid persona: "<request/>" (expected `writer`, `engineer`, `telegrapher`, or `caveman`)
+        ⧉ **ASE**: **ERROR:** invalid persona: "<request/>" (expected `writer`, `engineer`, `journalist`, `telegrapher`, or `caveman`)
         </template>
 
     2.  If <request/> is equal <ase-persona-style/> report this with the

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

@@ -12,13 +12,23 @@
 ##  DESCRIPTION
 
 The `ase-meta-persona` skill gets or sets the active *communication
-style* (persona) of the assistant. Four intensity levels of token
+style* (persona) of the assistant. Five intensity levels of token
 usage are supported, from most verbose to most terse:
 
--   `writer`: decorative, eloquent, and explaining
--   `engineer`: concise, factual, and accurate (default)
--   `telegrapher`: brief, factual, and abbreviating
--   `caveman`: terse, rough, and stuttering
+-   `writer`: decorative, eloquent, and explaining; full prose
+    sentences bundled into paragraphs separated by blank lines
+-   `engineer`: concise, factual, and accurate (default); prefers
+    bullet point lists with one aspect per bullet
+-   `journalist`: layered, pyramid-structured; every aspect a single-line
+    bullet following `**<title>**: <core> ▶ **<keywords>**: <details>.`,
+    with a one-to-two word title, a terse core, one-to-four keywords, and
+    a one-to-four sentence detail
+-   `telegrapher`: brief, factual, and abbreviating; every aspect a
+    single-line bullet following `**<title>**: <core>.`, with a one-to-two
+    word title and a terse, arrow/em-dash-joined core
+-   `caveman`: terse, rough, and stuttering; every aspect a single-line
+    bullet with a very terse core of one-word fields or a one-to-two word
+    expression
 
 Without arguments, the skill reports the currently active persona.
 With a *persona* argument, it switches to that persona via the
@@ -27,7 +37,7 @@ With a *persona* argument, it switches to that persona via the
 ##  ARGUMENTS
 
 *persona*:
-    The persona to activate; one of `writer`, `engineer`,
+    The persona to activate; one of `writer`, `engineer`, `journalist`,
     `telegrapher`, or `caveman`. If omitted, the currently active
     persona is reported.
 

package/plugin/skills/ase-sync-export/help.md

@@ -8,6 +8,7 @@
 `ase-sync-export`
     [`--help`|`-h`]
     [`--source`|`-s` *source*[,...]]
+    [*filter*]
 
 ##  DESCRIPTION
 
@@ -28,7 +29,8 @@ An *export* is declared by a `-   Export:` bullet point in an artifact's
 format definition (see `ase-format-meta.md`, `ase-format-spec.md`, and
 `ase-format-arch.md`); an artifact *without* such a bullet is *not*
 exported. Each exported file is named
-`YYYY-MM-DD-<set>-<slug>-<id>.<ext>` and stored in the artifact's own
+`<set>-<no>-<id>-<slug>-<export-name>.<ext>` (e.g.
+`SPEC-07-DM-Data-Model-export.svg`) and stored in the artifact's own
 base directory. Initially, the *Data Model* (`SPEC-DM`) exports as a
 Mermaid UML diagram converted to SVG, and the *Technology Stack*
 (`ARCH-TS`) exports as a compact Markdown table.
@@ -39,6 +41,14 @@ Mermaid UML diagram converted to SVG, and the *Technology Stack*
     The comma-separated list of artifact kinds to export. Defaults to
     `SPEC,ARCH` (the skill errors out on an empty source).
 
+##  ARGUMENTS
+
+*filter*:
+    An optional free-form filtering hint that narrows the source
+    artifacts, or the aspects of those artifacts, to take into account
+    when materializing the exports. If omitted, every export declared by
+    a source artifact is materialized.
+
 ##  EXAMPLES
 
 Export the specification and architecture artifacts to their
@@ -54,6 +64,12 @@ Export only the specification artifacts:
 ❯ /ase-sync-export -s SPEC
 ```
 
+Export only the data-model artifact:
+
+```text
+❯ /ase-sync-export -s SPEC data model
+```
+
 ##  SEE ALSO
 
 [`ase-sync-reconcile`](../ase-sync-reconcile/help.md),