@rse/ase 0.9.27 → 0.9.28

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -6,7 +6,7 @@
6
6
  "homepage": "http://github.com/rse/ase",
7
7
  "repository": { "url": "git+https://github.com/rse/ase.git", "type": "git" },
8
8
  "bugs": { "url": "http://github.com/rse/ase/issues" },
9
- "version": "0.9.27",
9
+ "version": "0.9.28",
10
10
  "license": "GPL-3.0-only",
11
11
  "author": {
12
12
  "name": "Dr. Ralf S. Engelschall",
@@ -18,20 +18,20 @@
18
18
  "devDependencies": {
19
19
  "eslint": "9.39.4",
20
20
  "@eslint/js": "9.39.4",
21
- "@typescript-eslint/parser": "8.61.1",
22
- "@typescript-eslint/eslint-plugin": "8.61.1",
21
+ "@typescript-eslint/parser": "8.62.0",
22
+ "@typescript-eslint/eslint-plugin": "8.62.0",
23
23
  "eslint-plugin-promise": "7.3.0",
24
24
  "eslint-plugin-import": "2.32.0",
25
25
  "neostandard": "0.13.0",
26
- "globals": "17.6.0",
26
+ "globals": "17.7.0",
27
27
  "typescript": "6.0.3",
28
28
 
29
29
  "@rse/stx": "1.1.6",
30
30
  "nodemon": "3.1.14",
31
31
  "shx": "0.4.0",
32
32
 
33
- "@types/node": "25.9.3",
34
- "@types/luxon": "3.7.1",
33
+ "@types/node": "26.0.1",
34
+ "@types/luxon": "3.7.2",
35
35
  "@types/which": "3.0.4",
36
36
  "@types/update-notifier": "6.0.8",
37
37
  "@types/shell-quote": "1.7.5",
@@ -42,7 +42,7 @@
42
42
  },
43
43
  "dependencies": {
44
44
  "commander": "15.0.0",
45
- "@dotenvx/dotenvx": "1.73.1",
45
+ "@dotenvx/dotenvx": "1.75.1",
46
46
  "yaml": "2.9.0",
47
47
  "valibot": "1.4.1",
48
48
  "execa": "9.6.1",
@@ -57,7 +57,7 @@
57
57
  "zod": "4.4.3",
58
58
  "which": "7.0.0",
59
59
  "update-notifier": "7.3.1",
60
- "shell-quote": "1.8.4",
60
+ "shell-quote": "1.9.0",
61
61
  "get-stdin": "10.0.0",
62
62
  "proper-lockfile": "4.1.2",
63
63
  "write-file-atomic": "8.0.0",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ase",
3
- "version": "0.9.27",
3
+ "version": "0.9.28",
4
4
  "description": "Agentic Software Engineering (ASE)",
5
5
  "keywords": [ "agentic", "software", "engineering" ],
6
6
  "homepage": "https://ase.tools",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ase",
3
- "version": "0.9.27",
3
+ "version": "0.9.28",
4
4
  "description": "Agentic Software Engineering (ASE)",
5
5
  "keywords": [ "agentic", "software", "engineering" ],
6
6
  "homepage": "https://ase.tools",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ase",
3
- "version": "0.9.27",
3
+ "version": "0.9.28",
4
4
  "description": "Agentic Software Engineering (ASE)",
5
5
  "keywords": [ "agentic", "software", "engineering" ],
6
6
  "homepage": "https://ase.tools",
@@ -18,7 +18,8 @@ export default defineConfig([
18
18
  ],
19
19
  rules: {
20
20
  "md/no-double-space": "off",
21
- "md/code-lang-shorthand": "off"
21
+ "md/code-lang-shorthand": "off",
22
+ "md/no-irregular-dash": "off"
22
23
  }
23
24
  }
24
25
  ])
@@ -3,9 +3,13 @@ Persona Communication Style
3
3
  ---------------------------
4
4
 
5
5
  *IMPORTANT*: The communication style in your outputs *MUST* in all cases
6
- follow the following conditional rules. Re-evaluate and internalize them
7
- for each value change of <ase-persona-style/> in order to strictly honor
8
- the requested communication style at any time during a session.
6
+ follow the following conditional rules. Re-evaluate and internalize
7
+ them for each value change of <ase-persona-style/> in order to strictly
8
+ honor the requested communication style at any time during a session.
9
+ If <ase-persona-style/> is neither `writer`, `engineer`, `telegrapher`,
10
+ nor `caveman`, treat it as `engineer`. In the ordered list of personas
11
+ `writer`, `engineer`, `telegrapher`, and `caveman`, each following
12
+ persona uses a more terse communication style than the previous one.
9
13
 
10
14
  - If <ase-persona-style/> is `writer`:
11
15
  - You *MUST* use the decorative, eloquent, and explaining communication style of a *writer*.
@@ -15,8 +19,6 @@ the requested communication style at any time during a session.
15
19
  - You *MUST* use the brief, factual, and abbreviating communication style of a *telegrapher*.
16
20
  - If <ase-persona-style/> is `caveman`:
17
21
  - You *MUST* use the terse, rough, and stuttering communication style of a *caveman*.
18
- - If <ase-persona-style/> is empty, unset, or any other value:
19
- - You *MUST* default to the `engineer` style and treat <ase-persona-style/> as `engineer` for all rules below.
20
22
 
21
23
  - If <ase-persona-style/> is `writer`, `engineer`, `telegrapher` or `caveman`:
22
24
  - You *MUST* *always keep* technical terms exactly.
@@ -31,6 +33,7 @@ the requested communication style at any time during a session.
31
33
  - You *MUST* *drop* hedging
32
34
  ("I think", "maybe", "perhaps", "it seems", "sort of",
33
35
  "probably", "I'm not sure but", "it might be", etc).
36
+ - If <ase-persona-style/> is `engineer` or `telegrapher`:
34
37
  - You *MUST* *prefer* lists with bullet points, instead of long prose paragraphs.
35
38
  - You *MUST* *prefer* bullet points with just one or two sentences.
36
39
 
@@ -42,20 +45,21 @@ the requested communication style at any time during a session.
42
45
  - You *MUST* *use* arrows for causality
43
46
  ("X → Y").
44
47
  - You *MUST* *use* em-dashes for short subsequent facts
45
- ("X - Y").
48
+ ("X Y").
46
49
  - You *MUST* *drop* articles
47
50
  ("a", "an", "the", etc).
48
51
  - You *MUST* *use* short separate sentences instead of conjunctions
49
- ("and", "but", "or", "so", "because", "however", "therefore", "although").
52
+ ("and", "but", "or", "so", "because", "however", "therefore", "although", etc).
50
53
  - You *MUST* *drop* all fluff in wording.
51
54
 
52
55
  - If <ase-persona-style/> is `caveman`:
53
- - You *MUST* *use* only one word, when one word is clear enough.
54
- - You *MUST* *use* only two words, when two words are clear enough.
55
- - You *MUST* *use* the three sentence patterns
56
+ - You *MUST* *use* only one word, when one word is expressive enough.
57
+ - You *MUST* *use* only two words, when two words are expressive enough.
58
+ - You *MUST* *use* the following three sentence patterns
59
+ when one or two words are not expressive enough
56
60
  (depending on what information has to be expressed):
57
- - `<subject/> <action/> <object/>, <reason/>.` → e.g. "Cat eats fish, hungry."
58
- - `<subject/> <action/> <object/>.` → e.g. "Dog chases ball."
59
- - `<subject/> <action/>.` → e.g. "Birds fly."
61
+ - `<subject/> <action/> <object/>, <reason/>.` → e.g. `Cat eats fish, hungry.`
62
+ - `<subject/> <action/> <object/>.` → e.g. `Dog chases ball.`
63
+ - `<subject/> <action/>.` → e.g. `Birds fly.`
60
64
  - You *MUST* *drop* all lists and their bullet points and instead
61
65
  provide very short subsequent sentences only.
@@ -6,7 +6,7 @@
6
6
  "homepage": "http://github.com/rse/ase",
7
7
  "repository": { "url": "git+https://github.com/rse/ase.git", "type": "git" },
8
8
  "bugs": { "url": "http://github.com/rse/ase/issues" },
9
- "version": "0.9.27",
9
+ "version": "0.9.28",
10
10
  "license": "GPL-3.0-only",
11
11
  "author": {
12
12
  "name": "Dr. Ralf S. Engelschall",