@godv61/dsh-task-engine 0.23.8 → 0.23.9

package/lib/seed-preset.d.ts

@@ -1,11 +1,11 @@
 /**
  * Seed the `eng` preset into the user's `.agent-presets` root.
  *
- * Installing the bundle must put a pickable "工程化开发引�? preset in the preset
+ * Installing the bundle must put a pickable "工程化开发引操 preset in the preset
  * picker without anyone hand-copying a composition. The preset is the shipped
  * `standard` composition with three edits: the persona is replaced by the
  * engineering persona, `task-engine-agent` is appended, and nothing else changes
- * �?so a session on it has every tool `standard` has, plus `dev_task`.
+ * —so a session on it has every tool `standard` has, plus `dev_task`.
  *
  * The seed DERIVES the composition from the `standard` that is running, and
  * RE-DERIVES it whenever that source moves. The earlier version copied once and
@@ -43,7 +43,7 @@ declare const SEEDED_PERSONA_MARKER = "    text: |-\n";
  * schemas are mutually exclusive: a preset written with `prefix` is rejected
  * outright by an older persona plugin with `$.text missing required value`, and
  * `text` is rejected by the newer one. The seed therefore cannot hardcode
- * either name �?it reads which one the source composition already uses, since
+ * either name —it reads which one the source composition already uses, since
  * that composition is what the running harness mounts.
  */
 type PersonaField = 'text' | 'prefix';
@@ -74,7 +74,7 @@ declare function personaFieldOf(composition: string): PersonaField;
  * Replace the persona row's config with the engineering persona, keeping the
  * field name the running harness uses.
  *
- * The persona schema has moved (`text:` �?`prefix`/`suffix`), so this rewrites
+ * The persona schema has moved (`text:` →`prefix`/`suffix`), so this rewrites
  * the whole `config:` block of the `persona` row rather than matching one
  * historical phrasing, and writes whichever field
  * {@link personaFieldOf} found in the source. A `suffix:` row is preserved when
@@ -101,7 +101,7 @@ declare function wasSeeded(composition: string): boolean;
  *
  * Failures are swallowed: a seed that cannot write must not stop the bundle's
  * host half (its Remote controller and workbench) from loading. A preset that
- * was deleted by the user stays deleted �?re-derivation only touches a file the
+ * was deleted by the user stays deleted —re-derivation only touches a file the
  * seed itself created.
  */
 export declare function seedEngPreset(): void;

package/lib/seed-preset.js

@@ -1,11 +1,11 @@
 /**
  * Seed the `eng` preset into the user's `.agent-presets` root.
  *
- * Installing the bundle must put a pickable "工程化开发引�? preset in the preset
+ * Installing the bundle must put a pickable "工程化开发引操 preset in the preset
  * picker without anyone hand-copying a composition. The preset is the shipped
  * `standard` composition with three edits: the persona is replaced by the
  * engineering persona, `task-engine-agent` is appended, and nothing else changes
- * �?so a session on it has every tool `standard` has, plus `dev_task`.
+ * —so a session on it has every tool `standard` has, plus `dev_task`.
  *
  * The seed DERIVES the composition from the `standard` that is running, and
  * RE-DERIVES it whenever that source moves. The earlier version copied once and
@@ -57,7 +57,7 @@ function dshHome() {
  * time from the installed DSH rather than from a build-time constant.
  *
  * `@deepseek-ai/dsh-agent-presets` also exports `SHIPPED_PRESET_ROOT`, but that
- * is `fileURLToPath(new URL('../presets/', import.meta.url))` �?a constant baked
+ * is `fileURLToPath(new URL('../presets/', import.meta.url))` —a constant baked
  * into whichever copy of the package the *plugin* resolves. Under a real install
  * that is the plugin's own dependency tree, which can sit at a different DSH
  * version than the one running: the seed then copies an obsolete `standard`,
@@ -126,7 +126,7 @@ function personaFieldOf(composition) {
  * Replace the persona row's config with the engineering persona, keeping the
  * field name the running harness uses.
  *
- * The persona schema has moved (`text:` �?`prefix`/`suffix`), so this rewrites
+ * The persona schema has moved (`text:` →`prefix`/`suffix`), so this rewrites
  * the whole `config:` block of the `persona` row rather than matching one
  * historical phrasing, and writes whichever field
  * {@link personaFieldOf} found in the source. A `suffix:` row is preserved when
@@ -204,7 +204,7 @@ function deriveComposition() {
  *
  * Failures are swallowed: a seed that cannot write must not stop the bundle's
  * host half (its Remote controller and workbench) from loading. A preset that
- * was deleted by the user stays deleted �?re-derivation only touches a file the
+ * was deleted by the user stays deleted —re-derivation only touches a file the
  * seed itself created.
  */
 export function seedEngPreset() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@godv61/dsh-task-engine",
-  "version": "0.23.8",
+  "version": "0.23.9",
   "description": "Preset-workflow engineering delivery engine for DeepSeek Harness: a `dev_task` tool that hard-gates stage transitions and commit scope/message, per-node skill/rule bindings with progressive disclosure, a workbench to pick a flow preset and mount skills/rules, and preset-scoped activation — the tool and skills activate only for sessions on a preset that names the agent row.",
   "type": "module",
   "main": "lib/index.js",

package/scripts/verify-package.mjs

@@ -1,7 +1,7 @@
 /**
  * Black-box verification of the npm tarball before publishing: packs the
  * package, extracts it into a clean temp dir, and proves the published entry
- * points actually work �?main import, browser client registration, the bundled
+ * points actually work —main import, browser client registration, the bundled
  * `.p0-test.mjs`, the CLI, and the `files` whitelist.
  *
  * Run: `npm run verify:package`
@@ -51,7 +51,7 @@ check('tarball excludes build scripts', !listing.some(line => line.endsWith('bui
 // Every `node <file>` script the manifest declares must actually ship, EXCEPT
 // the build-time ones that `prepare` needs in the source tree only. A script
 // whose target is absent from `files` installs fine and then dies with
-// MODULE_NOT_FOUND �?which is exactly what verify:package and verify:dsh did
+// MODULE_NOT_FOUND —which is exactly what verify:package and verify:dsh did
 // until this assertion existed, because neither scripts/ path was published.
 {
   const manifest = JSON.parse(readFileSync(join(pkgRoot, 'package.json'), 'utf8'))