@rse/ase 0.9.57 → 0.9.58

package/dst/ase-service.js

@@ -24,6 +24,7 @@ import { MarkdownMCP } from "./ase-markdown.js";
 import { ArtifactMCP } from "./ase-artifact.js";
 import { KVMCP } from "./ase-kv.js";
 import { TimestampMCP } from "./ase-timestamp.js";
+import { SleepMCP } from "./ase-sleep.js";
 import { GetoptMCP } from "./ase-getopt.js";
 import { SkillsMCP } from "./ase-skills.js";
 import pkg from "../package.json" with { type: "json" };
@@ -268,6 +269,7 @@ export default class ServiceCommand {
             new ArtifactMCP(this.log).register(mcp);
             new KVMCP().register(mcp);
             new TimestampMCP().register(mcp);
+            new SleepMCP().register(mcp);
             new GetoptMCP().register(mcp);
             new SkillsMCP().register(mcp);
             new ConfigMCP(this.log).register(mcp);

package/dst/ase-sleep.js

@@ -0,0 +1,26 @@
+/*
+**  Agentic Software Engineering (ASE)
+**  Copyright (c) 2025-2026 Dr. Ralf S. Engelschall <rse@engelschall.com>
+**  Licensed under Apache 2.0 <https://spdx.org/licenses/Apache-2.0>
+*/
+import { z } from "zod";
+/*  MCP registration entry point for sleep tool  */
+export class SleepMCP {
+    register(mcp) {
+        mcp.registerTool("ase_sleep", {
+            title: "ASE sleep",
+            description: "Wait once for `duration` seconds and then return. " +
+                "The duration can be fractional (e.g. `1.5`). " +
+                "Returns `OK: slept <duration> seconds` as `text` after the duration elapsed.",
+            inputSchema: {
+                duration: z.number().positive().max(3600)
+                    .describe("wait duration in seconds (fractional values allowed, at most 3600)")
+            }
+        }, async (args) => {
+            await new Promise((resolve) => setTimeout(resolve, args.duration * 1000));
+            return {
+                content: [{ type: "text", text: `OK: slept ${args.duration} seconds` }]
+            };
+        });
+    }
+}

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":                              "0.9.57",
+    "version":                              "0.9.58",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

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

package/plugin/meta/ase-constitution.md

@@ -31,6 +31,10 @@ which boosts you to an expert-level Software Engineering AI agent.
 - Place a *blank line before any comment line*,
   but not when it is the first line of a block or an end-of-line comment.
 - Keep code and comment *formatting exactly as in the existing code*.
+- Keep comments *brief*: target *1-2 lines*, only as an exception use up to *4 lines*,
+  and only for *very complex algorithms* go up to at most *8 lines*.
+  If an existing comment is already at its limit and still has to be expanded,
+  first *compact* its wording before adding new content.
 - Use *regular comments* `/*  [...]  */` instead of end-of-line comments `//  [...]`.
 - Use *two leading/trailing spaces within comments* as in `/*  [...]  */`.
 - Always use *parentheses around arrow function parameters*, even for a single parameter.

package/plugin/meta/ase-control.md

@@ -95,6 +95,27 @@ Control Flow Constructs
     is finished and no further repetitions are performed. This construct
     is expanded into nothing. Do not output anything.
 
+-   *IMPORTANT*: You *MUST* honor the following control flow construct:
+    <sleep duration="<sleep-duration/>"/>:
+
+    This specifies a single *wait* of <sleep-duration/> seconds
+    (fractional values like `1.5` are allowed): call the
+    `ase_sleep(duration: <sleep-duration/>)` tool of the `ase` MCP
+    server, which returns once the duration has elapsed. This construct
+    is expanded into nothing. Do not output anything.
+
+-   *IMPORTANT*: You *MUST* honor the following control flow construct:
+    <await condition="<await-condition/>" [interval="<await-interval/>"]><await-body/></await>:
+
+    This specifies an <await-body/> whose execution *waits* until
+    <await-condition/> is met: if <await-condition/> is met, the
+    <await-body/> is executed once and the construct is finished. If
+    <await-condition/> is *not* met, wait for <await-interval/> seconds
+    (default: `60`) via the `ase_sleep(duration: <await-interval/>)`
+    tool of the `ase` MCP server and then *start over* by re-evaluating
+    <await-condition/>. This construct is expanded to its
+    <await-body/>. Do not output anything else.
+
 -   *IMPORTANT*: You *MUST* honor the following control flow construct:
     <agent <attr/>="<value/>" [...]><agent-body/></agent>:
 

package/plugin/meta/ase-skill.md

@@ -292,8 +292,10 @@ Artifact Boxing Transparency
         -   Internals exposed: *none* (no diffs, no code, no per-artifact explanation)
 
 -   *IMPORTANT*: Precedence rule: a skill's *explicit* `black` branches
+    and a skill's *explicit* output suppression instructions
     deterministically skip or suppress and *win* over the implicit decisions
-    above. Where no such branches exist, the decisions above apply.
+    above. Where no such branches or instructions exist, the decisions
+    above apply.
 
 Guidance Hint Level
 -------------------

package/plugin/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":                              "0.9.57",
+    "version":                              "0.9.58",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-craft
-argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--direct|-D] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
     Craft Source Code:
     Use when user wants to "create", "add", or "craft" a new feature from scratch.
@@ -10,6 +10,7 @@ effort: xhigh
 allowed-tools:
     - "Skill"
     - "Agent"
+    - "Read"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -23,7 +24,7 @@ Craft Source Code
 
 <expand name="getopt"
     arg1="ase-code-craft"
-    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --direct|-D --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -45,9 +46,18 @@ From scratch *craft* the following feature:
 Procedure
 ---------
 
+<if condition="<getopt-option-direct/> is not equal to 'true'">
 You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
 filesystem-modifying tool during this entire skill. The *only*
 permitted way to persist artifacts is via `ase_task_save(...)`.
+</if>
+<else>
+The `--direct`/`-D` mode applies the crafting *in place*, so STEP 4
+below *requires* `Edit` and `Write` to modify the affected artifacts.
+Every modification *MUST* still stay restricted to the artifacts the
+crafting actually demands, and you *MUST* *NOT* call
+`ase_task_save(...)`, as no task plan is composed at all.
+</else>
 
 <flow>
 
@@ -136,13 +146,41 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     </step>
 
-4.  <step id="STEP 4: Choose Feature Crafting Approaches">
+4.  <if condition="<getopt-option-direct/> is equal to 'true'">
+
+    <step id="STEP 4: Direct Feature Crafting">
+
+    1.  Directly craft the <feature/> by modifying the affected
+        *artifacts* with a corresponding, complete *change set*,
+        based on your gathered knowledge about the code base and your
+        internalized crafting tenets. Also, if a CHANGELOG.md
+        file exists, make an appropriate entry there, too.
+
+    2.  Output only the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **changes directly applied**
+        </template>
+
+    3.  Then *IMMEDIATELY* *STOP* all further skill processing. You
+        *MUST* *NOT* output anything else in this STEP 4 or after it --
+        *independent* of <ase-project-boxing/>, whose exposure rules
+        are explicitly *overridden* here. Especially, do not output a
+        change summary, a list of modified artifacts, a rationale, or
+        a unified diff of the changes.
+
+    </step>
+
+    </if>
+    <else>
+
+    <step id="STEP 4: Choose Feature Crafting Approaches">
 
     <expand name="code-approaches" arg1="feature" arg2="crafting"></expand>
 
     </step>
 
-5.  <step id="STEP 5: Compose Feature Crafting Plan">
+    <step id="STEP 5: Compose Feature Crafting Plan">
 
     1.  *Compose a feature plan* for the chosen feature A<n/> by
         closely aligning to the existing architecture and the existing
@@ -187,4 +225,6 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     </step>
 
+    </else>
+
 </flow>

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

@@ -9,6 +9,7 @@
     [`--help`|`-h`]
     [`--auto`|`-a`]
     [`--dry`|`-d`]
+    [`--direct`|`-D`]
     [`--quick`|`-Q`]
     [`--next`|`-n` *option*[,...]]
     [*task-id*:] *feature*
@@ -22,10 +23,11 @@ investigating the existing code base, internalizing crafting tenets
 preferred approach, and composing a corresponding *task plan* aligned
 with the existing architecture.
 
-The skill does *not* directly modify source files. It persists the
-plan via `ase_task_save` and then hands off to `ase-task-edit`,
-`ase-task-preflight`, or `ase-task-implement`, as selected by
-`--next`.
+By default the skill does *not* directly modify source files. It
+persists the plan via `ase_task_save` and then hands off to
+`ase-task-edit`, `ase-task-preflight`, or `ase-task-implement`, as
+selected by `--next`. Only under `--direct` it skips the plan
+entirely and applies the change set to the affected artifacts itself.
 
 ##  OPTIONS
 
@@ -40,6 +42,15 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     type-checker, or program execution) once the source files have
     been modified.
 
+`--direct`|`-D`:
+    Craft the feature *immediately* and *in place*: skip the
+    feature approaches, the interactive dialog, and the entire task
+    plan ceremony, and directly apply the complete change set to the
+    affected artifacts, including a corresponding entry in an existing
+    `CHANGELOG.md` file. In this mode `--auto`, `--dry`, `--quick`, and
+    `--next` have no effect, as neither approaches are proposed nor a
+    plan is composed.
+
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended feature approach, compose the plan *without* the

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-refactor
-argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <request>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--direct|-D] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <request>"
 description: >
     Refactor Code:
     Use when user wants to "refactor" or "change" the code base.
@@ -10,6 +10,7 @@ effort: xhigh
 allowed-tools:
     - "Skill"
     - "Agent"
+    - "Read"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -23,7 +24,7 @@ Refactor Source Code
 
 <expand name="getopt"
     arg1="ase-code-refactor"
-    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --direct|-D --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -45,9 +46,18 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 Procedure
 ---------
 
+<if condition="<getopt-option-direct/> is not equal to 'true'">
 You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
 filesystem-modifying tool during this entire skill. The *only*
 permitted way to persist artifacts is via `ase_task_save(...)`.
+</if>
+<else>
+The `--direct`/`-D` mode applies the refactoring *in place*, so STEP 4
+below *requires* `Edit` and `Write` to modify the affected artifacts.
+Every modification *MUST* still stay restricted to the artifacts the
+refactoring actually demands, and you *MUST* *NOT* call
+`ase_task_save(...)`, as no task plan is composed at all.
+</else>
 
 <flow>
 
@@ -136,13 +146,41 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     </step>
 
-4.  <step id="STEP 4: Choose Refactoring Approaches">
+4.  <if condition="<getopt-option-direct/> is equal to 'true'">
+
+    <step id="STEP 4: Direct Refactoring">
+
+    1.  Directly apply the refactoring <request/> by modifying the
+        affected *artifacts* with a corresponding, complete *change set*,
+        based on your gathered knowledge about the code base and your
+        internalized refactoring tenets. Also, if a CHANGELOG.md
+        file exists, make an appropriate entry there, too.
+
+    2.  Output only the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **changes directly applied**
+        </template>
+
+    3.  Then *IMMEDIATELY* *STOP* all further skill processing. You
+        *MUST* *NOT* output anything else in this STEP 4 or after it --
+        *independent* of <ase-project-boxing/>, whose exposure rules
+        are explicitly *overridden* here. Especially, do not output a
+        change summary, a list of modified artifacts, a rationale, or
+        a unified diff of the changes.
+
+    </step>
+
+    </if>
+    <else>
+
+    <step id="STEP 4: Choose Refactoring Approaches">
 
     <expand name="code-approaches" arg1="refactoring" arg2="refactoring"></expand>
 
     </step>
 
-5.  <step id="STEP 5: Compose Refactoring Plan">
+    <step id="STEP 5: Compose Refactoring Plan">
 
     1.  *Compose a refactoring plan* for the chosen refactoring A<n/> by
         closely aligning to the existing architecture and the existing
@@ -187,5 +225,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     </step>
 
+    </else>
+
 </flow>
 

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

@@ -9,6 +9,7 @@
     [`--help`|`-h`]
     [`--auto`|`-a`]
     [`--dry`|`-d`]
+    [`--direct`|`-D`]
     [`--quick`|`-Q`]
     [`--next`|`-n` *option*[,...]]
     [*task-id*:] *request*
@@ -22,10 +23,11 @@ clear interfaces, ...), proposing one or more *refactoring approaches*
 with pros and cons, letting the user pick the preferred approach,
 and composing a corresponding *task plan*.
 
-The skill does *not* directly modify source files. It persists the
-plan via `ase_task_save` and then hands off to `ase-task-edit`,
-`ase-task-preflight`, or `ase-task-implement`, as selected by
-`--next`.
+By default the skill does *not* directly modify source files. It
+persists the plan via `ase_task_save` and then hands off to
+`ase-task-edit`, `ase-task-preflight`, or `ase-task-implement`, as
+selected by `--next`. Only under `--direct` it skips the plan
+entirely and applies the change set to the affected artifacts itself.
 
 ##  OPTIONS
 
@@ -40,6 +42,15 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     type-checker, or program execution) once the source files have
     been modified.
 
+`--direct`|`-D`:
+    Apply the refactoring *immediately* and *in place*: skip the
+    refactoring approaches, the interactive dialog, and the entire task
+    plan ceremony, and directly apply the complete change set to the
+    affected artifacts, including a corresponding entry in an existing
+    `CHANGELOG.md` file. In this mode `--auto`, `--dry`, `--quick`, and
+    `--next` have no effect, as neither approaches are proposed nor a
+    plan is composed.
+
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended refactoring approach, compose the plan *without* the

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

@@ -206,8 +206,18 @@ resolution actually demands, and you *MUST* *NOT* call
         internalized problem resolution tenets. Also, if a CHANGELOG.md
         file exists, make an appropriate entry there, too.
 
-    2.  Do not output anything else in this STEP 4. Especially, do not
-        output a change summary or a unified diff of the changes.
+    2.  Output only the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **changes directly applied**
+        </template>
+
+    3.  Then *IMMEDIATELY* *STOP* all further skill processing. You
+        *MUST* *NOT* output anything else in this STEP 4 or after it --
+        *independent* of <ase-project-boxing/>, whose exposure rules
+        are explicitly *overridden* here. Especially, do not output a
+        change summary, a list of modified artifacts, a rationale, or
+        a unified diff of the changes.
 
     </step>