dsh-embedded-workbench 0.8.2 → 0.8.3

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Amethyst Luna
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Amethyst Luna
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/lib/index.js

@@ -1,197 +1,208 @@
-/**
- * embedded-workbench — DeepSeek Harness native plugin for the Embedded
- * Workbench toolbox. Injects the session-start gate text (1% Rule, Red
- * Flags, Plan Verification Gate, skills roster) into the first model step
- * of every agent session, mirroring the SessionStart hook the Claude Code
- * plugin installs. The 8 skills ship in this package's `skills/` directory
- * and are registered at apply time into dsh's `ctx.skills` registry through
- * the standard filesystem provider, so they appear in every session catalog
- * without a manual copy step.
- *
- * Injection listens on agent/pre-step and appends the gate to the FIRST
- * model step that runs, once per session (guarded by the session's durable
- * history). Session-start inbox injection was dropped: a blank-session preset
- * switch (agentPreset.select -> recompose) can clear the inbox before the
- * first step, losing the gate for the whole session. The pre-step decision is
- * the durable path - anchored/bootstrap presets that strip first-step injected
- * reminders (skill catalog, AGENTS.md, gate plugins) simply defer this message
- * to the first step after their promotion, and the history guard re-injects it
- * there. The default gate text is the dsh-native adaptation of
- * `hooks/session-start-content.md`: behavior rules
- * (1% Rule / Red Flags / Plan Verification Gate) stay in sync, while
- * presentation is adapted to dsh's native skill catalog — no roster table
- * (the model sees skills in its catalog) and no install instructions (those
- * live in `.dsh/INSTALL.md`). Deployments override via Config.
- *
- * @module embedded-workbench-dsh
- */
-import { fileURLToPath } from 'node:url';
-import z from '@deepseek-ai/schemastery';
-import { createUserMessage } from '@deepseek-ai/dsh-llm';
-import { FileSystemSkillProvider } from '@deepseek-ai/dsh-skill-filesystem';
-export const name = 'embedded-workbench';
-// Skills are contributed through the registry service, which dsh-base always
-// mounts before bundle rows such as this one apply.
-export const inject = ['skills'];
-// Absolute path of the package's shipped skills directory. `lib/index.js`
-// lives one level below the package root, so `../skills` from the module URL
-// lands on `<package>/skills` regardless of where the package was installed.
-const SKILLS_DIR = fileURLToPath(new URL('../skills', import.meta.url));
-const GATE_PLUGIN_ID = 'embedded-workbench';
-const DEFAULT_GATE_CONTENT = `<EXTREMELY_IMPORTANT>
-Plugin embedded-workbench is active. You have embedded C/C++ firmware development skills — names and "Use when" triggers are in your skill catalog; load them with the skill tool. No custom agents in dsh: use the native subagent tooling for parallel work.
-
-**1% Rule**: If there is even a 1% chance a skill applies to your task, invoke it before responding. If the skill turns out to be wrong for the situation, discard it and move on. The cost of loading a skill is trivial compared to the cost of a preventable mistake.
-
-**Red Flags** — if you think any of these, STOP. You are rationalizing:
-
-| You think | Reality |
-|-----------|---------|
-| "This is just a quick fix" | Quick fixes break things. A 3-line design check costs 30 seconds. |
-| "I already understand this code" | You are looking at one file. The blast radius may span 5 modules. |
-| "The skill is overkill for this" | Simple things become complex. Check for skills. |
-| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
-| "I can just read the file directly" | Skills have patterns and pitfalls you will not discover by reading. |
-| "I remember this skill content" | Skills evolve. Always load the current version. |
-| "I've explored enough, time to exit plan mode" | The exit_plan_mode tool is the verification gate. Have you loaded the logicprobe skill — or, if it is not installed, the built-in fallback fact-check skill? Every plan must pass this gate before exit. |
-| "This plan is too simple for logicprobe" | logicprobe auto-classifies depth; the fallback fact-check verifies every claim regardless. You don't decide. |
-| "I already read the code, I know the file paths are correct" | Load the logicprobe skill or the fallback fact-check skill, verify each claim, append the "## Plan Verification" block. |
-
-**Plan Verification Gate**: Before calling exit_plan_mode (or presenting a plan for approval), load the logicprobe skill (a separate plugin) — or, if it is missing from your skill catalog, load the built-in fallback fact-check skill for claim-by-claim verification, tell the user that behavioral/model claims degrade to manual confirmation, and recommend installing logicprobe. If neither is loaded, inform the user "此计划未经核查，是否需要我先做事实核查？" Silent skip is not an option.
-
-To load workflows and engineering policies: load the embedded-workbench skill.
-
-**Proactive features**: When you see state machines, protocol refactoring, behavioral claims ("always"/"never"), or multi-module tasks — suggest verification (logicprobe, or the built-in fact-check fallback if logicprobe is not installed), adversarial probing, or parallel subagents BEFORE the user asks. Most users do not know these exist.
-</EXTREMELY_IMPORTANT>`;
-export const Config = z.object({
-    enabled: z.boolean().default(true),
-    gateContent: z.string().default(DEFAULT_GATE_CONTENT),
-});
-function gateMessage(text) {
-    return createUserMessage({
-        content: [{ type: 'text', text }],
-        // `form` omitted — an undeclared context is the documented default.
-        source: { kind: 'plugin', plugin: GATE_PLUGIN_ID },
-    });
-}
-/**
- * Model-visible catalog entry (cordis_inspect_list / cordis_inspect_query):
- * lets the model read this plugin's runtime status without guessing. Mirrors
- * the registration pattern of the official dsh-tool-cordis host providers.
- */
-function inspectProvider(config) {
-    return {
-        manifest: {
-            id: 'embedded-workbench',
-            description: 'Session-start gate injection for the Embedded Workbench toolbox — folds the 1% Rule / Red Flags / Plan Verification Gate text into the first model step of every agent session.',
-            methods: [
-                {
-                    name: 'status',
-                    description: 'Read whether the gate injection is active and how large the injected gate text is.',
-                    inputSchema: {
-                        type: 'object',
-                        properties: {},
-                        additionalProperties: false,
-                    },
-                    outputSchema: {
-                        type: 'object',
-                        description: 'Gate-injection plugin status.',
-                        properties: {
-                            enabled: { type: 'boolean', description: 'Whether the gate folds into the first model step.' },
-                            gateContentLength: { type: 'integer', description: 'Length in characters of the injected gate text.' },
-                        },
-                        required: ['enabled', 'gateContentLength'],
-                        additionalProperties: false,
-                    },
-                },
-            ],
-        },
-        query: async (method) => {
-            if (method === 'status') {
-                return {
-                    enabled: config.enabled,
-                    gateContentLength: config.gateContent.length,
-                };
-            }
-            return null;
-        },
-    };
-}
-export function apply(ctx, config) {
-    // Catalog visibility is optional: register only when the inspect registry
-    // service is mounted, so headless assemblies without it keep the gate
-    // injection working. The registry may be provided AFTER this row applies
-    // (base-bundle rows can mount later), so registration is retried on the
-    // first agent/session-start — by then the app is fully booted.
-    let providerRegistered = false;
-    const registerProvider = () => {
-        if (providerRegistered)
-            return;
-        const inspect = ctx.get('cordisInspect');
-        if (inspect === undefined)
-            return;
-        try {
-            ctx.effect(() => inspect.register(inspectProvider(config)), 'embedded-workbench: inspect provider');
-            providerRegistered = true;
-        }
-        catch (err) {
-            console.warn('[embedded-workbench] inspect provider registration failed', err);
-        }
-    };
-    registerProvider();
-    // Ship the bundled skills through the registry: reuse the standard
-    // filesystem provider over this package's own `skills/` directory, so
-    // catalog discovery, frontmatter parsing, and SKILL.md loading behave
-    // exactly like project/user skills while the plugin stays self-contained.
-    // Registration lands in the global registry layer (this row mounts at the
-    // profile root), so every agent preset sees the skills. `registerProvider`
-    // returns the effect disposer; its teardown unregisters and invalidates.
-    ctx.skills.registerProvider((control) => {
-        return new FileSystemSkillProvider(ctx, control, {
-            providerName: 'embedded-workbench',
-            includeDefaultRoots: false,
-            customSkillDirs: [SKILLS_DIR],
-        });
-    });
-    if (!config.enabled)
-        return;
-    // Inject the gate once per session on the FIRST model step that runs,
-    // instead of at session-start: session-start injection lands in the agent's
-    // inbox, which a blank-session preset switch (agentPreset.select ->
-    // recompose) can clear before the first step - the gate would then be lost
-    // for the whole session. The pre-step decision is the durable path a
-    // first-step injection takes: the gate is appended to the first step's
-    // decision and enters session history there, so every later step (and a
-    // resume) skips it. Anchored/bootstrap presets that strip first-step
-    // injected reminders (skill catalog, AGENTS.md, gate plugins) simply defer
-    // this message to the first step after their promotion - the history guard
-    // re-injects it there, so the gate still lands exactly once per session.
-    ctx.on('agent/pre-step', async ({ agent }, next) => {
-        const decision = await next();
-        if (decision.kind === 'reject')
-            return decision;
-        registerProvider();
-        if (gateInHistory(agent.session))
-            return decision;
-        return {
-            kind: 'enter',
-            messages: [...decision.messages, gateMessage(config.gateContent)],
-        };
-    });
-}
-/**
- * Whether the gate already entered this session's durable history. The
- * pre-step listener re-appends the gate until it does; once a step committed
- * it, every later step (and a resume of a session that kept it) skips the
- * injection. A session whose gate was dropped before any step ran (e.g. an
- * inbox cleared by a blank-session preset switch) simply re-injects on the
- * first step that runs.
- */
-function gateInHistory(session) {
-    return session.events.some((event) => {
-        if (event.type !== 'user/message')
-            return false;
-        const source = event.data.source;
-        return source.kind === 'plugin' && source.plugin === GATE_PLUGIN_ID;
-    });
-}
+/**
+ * embedded-workbench — DeepSeek Harness native plugin for the Embedded
+ * Workbench toolbox. Injects the session-start gate text (1% Rule, Red
+ * Flags, Plan Verification Gate, skills roster) into the first model step
+ * of every agent session, mirroring the SessionStart hook the Claude Code
+ * plugin installs. The 8 skills ship in this package's `skills/` directory
+ * and are registered at apply time into dsh's `ctx.skills` registry through
+ * the standard filesystem provider, so they appear in every session catalog
+ * without a manual copy step.
+ *
+ * Injection listens on agent/pre-step and appends the gate to the FIRST
+ * model step that runs, once per session (guarded by the session's durable
+ * history). Session-start inbox injection was dropped: a blank-session preset
+ * switch (agentPreset.select -> recompose) can clear the inbox before the
+ * first step, losing the gate for the whole session. The pre-step decision is
+ * the durable path - anchored/bootstrap presets that strip first-step injected
+ * reminders (skill catalog, AGENTS.md, gate plugins) simply defer this message
+ * to the first step after their promotion, and the history guard re-injects it
+ * there. The default gate text is the dsh-native adaptation of
+ * `hooks/session-start-content.md`: behavior rules
+ * (1% Rule / Red Flags / Plan Verification Gate) stay in sync, while
+ * presentation is adapted to dsh's native skill catalog — no roster table
+ * (the model sees skills in its catalog) and no install instructions (those
+ * live in `.dsh/INSTALL.md`). Deployments override via Config.
+ *
+ * @module embedded-workbench-dsh
+ */
+import { fileURLToPath } from 'node:url';
+import z from '@deepseek-ai/schemastery';
+import { createUserMessage } from '@deepseek-ai/dsh-llm';
+import { FileSystemSkillProvider } from '@deepseek-ai/dsh-skill-filesystem';
+export const name = 'embedded-workbench';
+// Skills are contributed through the registry service, which dsh-base always
+// mounts before bundle rows such as this one apply.
+export const inject = ['skills'];
+// Absolute path of the package's shipped skills directory. `lib/index.js`
+// lives one level below the package root, so `../skills` from the module URL
+// lands on `<package>/skills` regardless of where the package was installed.
+const SKILLS_DIR = fileURLToPath(new URL('../skills', import.meta.url));
+const GATE_PLUGIN_ID = 'embedded-workbench';
+const DEFAULT_GATE_CONTENT = `<EXTREMELY_IMPORTANT>
+Plugin embedded-workbench is active. You have embedded C/C++ firmware development skills — names and "Use when" triggers are in your skill catalog; load them with the skill tool. No custom agents in dsh: use the native subagent tooling for parallel work.
+
+**1% Rule**: If there is even a 1% chance a skill applies to your task, invoke it before responding. If the skill turns out to be wrong for the situation, discard it and move on. The cost of loading a skill is trivial compared to the cost of a preventable mistake.
+
+**Red Flags** — if you think any of these, STOP. You are rationalizing:
+
+| You think | Reality |
+|-----------|---------|
+| "This is just a quick fix" | Quick fixes break things. A 3-line design check costs 30 seconds. |
+| "I already understand this code" | You are looking at one file. The blast radius may span 5 modules. |
+| "The skill is overkill for this" | Simple things become complex. Check for skills. |
+| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
+| "I can just read the file directly" | Skills have patterns and pitfalls you will not discover by reading. |
+| "I remember this skill content" | Skills evolve. Always load the current version. |
+| "I've explored enough, time to exit plan mode" | The exit_plan_mode tool is the verification gate. Have you loaded the logicprobe skill — or, if it is not installed, the built-in fallback fact-check skill? Every plan must pass this gate before exit. |
+| "This plan is too simple for logicprobe" | logicprobe auto-classifies depth; the fallback fact-check verifies every claim regardless. You don't decide. |
+| "I already read the code, I know the file paths are correct" | Load the logicprobe skill or the fallback fact-check skill, verify each claim, append the "## Plan Verification" block. |
+
+**Plan Verification Gate**: Before calling exit_plan_mode (or presenting a plan for approval), load the logicprobe skill (a separate plugin) — or, if it is missing from your skill catalog, load the built-in fallback fact-check skill for claim-by-claim verification, tell the user that behavioral/model claims degrade to manual confirmation, and recommend installing logicprobe. If neither is loaded, inform the user "此计划未经核查，是否需要我先做事实核查？" Silent skip is not an option.
+
+To load workflows and engineering policies: load the embedded-workbench skill.
+
+**Proactive features**: When you see state machines, protocol refactoring, behavioral claims ("always"/"never"), or multi-module tasks — suggest verification (logicprobe, or the built-in fact-check fallback if logicprobe is not installed), adversarial probing, or parallel subagents BEFORE the user asks. Most users do not know these exist.
+</EXTREMELY_IMPORTANT>`;
+export const Config = z.object({
+    enabled: z.boolean().default(true),
+    gateContent: z.string().default(DEFAULT_GATE_CONTENT),
+});
+function gateMessage(text) {
+    return createUserMessage({
+        content: [{ type: 'text', text }],
+        // `form` omitted — an undeclared context is the documented default.
+        source: { kind: 'plugin', plugin: GATE_PLUGIN_ID },
+    });
+}
+function readSessionEvents(session) {
+    const source = session;
+    if (typeof source.snapshotEvents === 'function') {
+        const snapshot = source.snapshotEvents();
+        if (Array.isArray(snapshot))
+            return snapshot;
+    }
+    if (Array.isArray(source.events))
+        return source.events;
+    return [];
+}
+/**
+ * Model-visible catalog entry (cordis_inspect_list / cordis_inspect_query):
+ * lets the model read this plugin's runtime status without guessing. Mirrors
+ * the registration pattern of the official dsh-tool-cordis host providers.
+ */
+function inspectProvider(config) {
+    return {
+        manifest: {
+            id: 'embedded-workbench',
+            description: 'Session-start gate injection for the Embedded Workbench toolbox — folds the 1% Rule / Red Flags / Plan Verification Gate text into the first model step of every agent session.',
+            methods: [
+                {
+                    name: 'status',
+                    description: 'Read whether the gate injection is active and how large the injected gate text is.',
+                    inputSchema: {
+                        type: 'object',
+                        properties: {},
+                        additionalProperties: false,
+                    },
+                    outputSchema: {
+                        type: 'object',
+                        description: 'Gate-injection plugin status.',
+                        properties: {
+                            enabled: { type: 'boolean', description: 'Whether the gate folds into the first model step.' },
+                            gateContentLength: { type: 'integer', description: 'Length in characters of the injected gate text.' },
+                        },
+                        required: ['enabled', 'gateContentLength'],
+                        additionalProperties: false,
+                    },
+                },
+            ],
+        },
+        query: async (method) => {
+            if (method === 'status') {
+                return {
+                    enabled: config.enabled,
+                    gateContentLength: config.gateContent.length,
+                };
+            }
+            return null;
+        },
+    };
+}
+export function apply(ctx, config) {
+    // Catalog visibility is optional: register only when the inspect registry
+    // service is mounted, so headless assemblies without it keep the gate
+    // injection working. The registry may be provided AFTER this row applies
+    // (base-bundle rows can mount later), so registration is retried on the
+    // first agent/session-start — by then the app is fully booted.
+    let providerRegistered = false;
+    const registerProvider = () => {
+        if (providerRegistered)
+            return;
+        const inspect = ctx.get('cordisInspect');
+        if (inspect === undefined)
+            return;
+        try {
+            ctx.effect(() => inspect.register(inspectProvider(config)), 'embedded-workbench: inspect provider');
+            providerRegistered = true;
+        }
+        catch (err) {
+            console.warn('[embedded-workbench] inspect provider registration failed', err);
+        }
+    };
+    registerProvider();
+    // Ship the bundled skills through the registry: reuse the standard
+    // filesystem provider over this package's own `skills/` directory, so
+    // catalog discovery, frontmatter parsing, and SKILL.md loading behave
+    // exactly like project/user skills while the plugin stays self-contained.
+    // Registration lands in the global registry layer (this row mounts at the
+    // profile root), so every agent preset sees the skills. `registerProvider`
+    // returns the effect disposer; its teardown unregisters and invalidates.
+    ctx.skills.registerProvider((control) => {
+        return new FileSystemSkillProvider(ctx, control, {
+            providerName: 'embedded-workbench',
+            includeDefaultRoots: false,
+            customSkillDirs: [SKILLS_DIR],
+        });
+    });
+    if (!config.enabled)
+        return;
+    // Inject the gate once per session on the FIRST model step that runs,
+    // instead of at session-start: session-start injection lands in the agent's
+    // inbox, which a blank-session preset switch (agentPreset.select ->
+    // recompose) can clear before the first step - the gate would then be lost
+    // for the whole session. The pre-step decision is the durable path a
+    // first-step injection takes: the gate is appended to the first step's
+    // decision and enters session history there, so every later step (and a
+    // resume) skips it. Anchored/bootstrap presets that strip first-step
+    // injected reminders (skill catalog, AGENTS.md, gate plugins) simply defer
+    // this message to the first step after their promotion - the history guard
+    // re-injects it there, so the gate still lands exactly once per session.
+    ctx.on('agent/pre-step', async ({ agent }, next) => {
+        const decision = await next();
+        if (decision.kind === 'reject')
+            return decision;
+        registerProvider();
+        if (gateInHistory(agent.session))
+            return decision;
+        return {
+            kind: 'enter',
+            messages: [...decision.messages, gateMessage(config.gateContent)],
+        };
+    });
+}
+/**
+ * Whether the gate already entered this session's durable history. The
+ * pre-step listener re-appends the gate until it does; once a step committed
+ * it, every later step (and a resume of a session that kept it) skips the
+ * injection. A session whose gate was dropped before any step ran (e.g. an
+ * inbox cleared by a blank-session preset switch) simply re-injects on the
+ * first step that runs.
+ */
+function gateInHistory(session) {
+    return readSessionEvents(session).some((event) => {
+        if (event.type !== 'user/message')
+            return false;
+        const source = event.data?.source;
+        return source?.kind === 'plugin' && source.plugin === GATE_PLUGIN_ID;
+    });
+}

package/lib/types/index.d.ts

@@ -1,43 +1,43 @@
-/**
- * embedded-workbench — DeepSeek Harness native plugin for the Embedded
- * Workbench toolbox. Injects the session-start gate text (1% Rule, Red
- * Flags, Plan Verification Gate, skills roster) into the first model step
- * of every agent session, mirroring the SessionStart hook the Claude Code
- * plugin installs. The 8 skills ship in this package's `skills/` directory
- * and are registered at apply time into dsh's `ctx.skills` registry through
- * the standard filesystem provider, so they appear in every session catalog
- * without a manual copy step.
- *
- * Injection listens on agent/pre-step and appends the gate to the FIRST
- * model step that runs, once per session (guarded by the session's durable
- * history). Session-start inbox injection was dropped: a blank-session preset
- * switch (agentPreset.select -> recompose) can clear the inbox before the
- * first step, losing the gate for the whole session. The pre-step decision is
- * the durable path - anchored/bootstrap presets that strip first-step injected
- * reminders (skill catalog, AGENTS.md, gate plugins) simply defer this message
- * to the first step after their promotion, and the history guard re-injects it
- * there. The default gate text is the dsh-native adaptation of
- * `hooks/session-start-content.md`: behavior rules
- * (1% Rule / Red Flags / Plan Verification Gate) stay in sync, while
- * presentation is adapted to dsh's native skill catalog — no roster table
- * (the model sees skills in its catalog) and no install instructions (those
- * live in `.dsh/INSTALL.md`). Deployments override via Config.
- *
- * @module embedded-workbench-dsh
- */
-import type { Context } from '@deepseek-ai/cordis';
-import z from '@deepseek-ai/schemastery';
-export declare const name = "embedded-workbench";
-export declare const inject: string[];
-export interface Config {
-    enabled: boolean;
-    gateContent: string;
-}
-export declare const Config: z<Schemastery.ObjectS<{
-    enabled: z<boolean, boolean>;
-    gateContent: z<string, string>;
-}>, Schemastery.ObjectT<{
-    enabled: z<boolean, boolean>;
-    gateContent: z<string, string>;
-}>>;
-export declare function apply(ctx: Context, config: Config): void;
+/**
+ * embedded-workbench — DeepSeek Harness native plugin for the Embedded
+ * Workbench toolbox. Injects the session-start gate text (1% Rule, Red
+ * Flags, Plan Verification Gate, skills roster) into the first model step
+ * of every agent session, mirroring the SessionStart hook the Claude Code
+ * plugin installs. The 8 skills ship in this package's `skills/` directory
+ * and are registered at apply time into dsh's `ctx.skills` registry through
+ * the standard filesystem provider, so they appear in every session catalog
+ * without a manual copy step.
+ *
+ * Injection listens on agent/pre-step and appends the gate to the FIRST
+ * model step that runs, once per session (guarded by the session's durable
+ * history). Session-start inbox injection was dropped: a blank-session preset
+ * switch (agentPreset.select -> recompose) can clear the inbox before the
+ * first step, losing the gate for the whole session. The pre-step decision is
+ * the durable path - anchored/bootstrap presets that strip first-step injected
+ * reminders (skill catalog, AGENTS.md, gate plugins) simply defer this message
+ * to the first step after their promotion, and the history guard re-injects it
+ * there. The default gate text is the dsh-native adaptation of
+ * `hooks/session-start-content.md`: behavior rules
+ * (1% Rule / Red Flags / Plan Verification Gate) stay in sync, while
+ * presentation is adapted to dsh's native skill catalog — no roster table
+ * (the model sees skills in its catalog) and no install instructions (those
+ * live in `.dsh/INSTALL.md`). Deployments override via Config.
+ *
+ * @module embedded-workbench-dsh
+ */
+import type { Context } from '@deepseek-ai/cordis';
+import z from '@deepseek-ai/schemastery';
+export declare const name = "embedded-workbench";
+export declare const inject: string[];
+export interface Config {
+    enabled: boolean;
+    gateContent: string;
+}
+export declare const Config: z<Schemastery.ObjectS<{
+    enabled: z<boolean, boolean>;
+    gateContent: z<string, string>;
+}>, Schemastery.ObjectT<{
+    enabled: z<boolean, boolean>;
+    gateContent: z<string, string>;
+}>>;
+export declare function apply(ctx: Context, config: Config): void;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "dsh-embedded-workbench",
-    "version": "0.8.2",
+    "version": "0.8.3",
     "description": "Embedded C/C++ firmware development toolbox — 4 agents, 8 skills covering FreeRTOS, ISR, NVM storage, Keil MDK, ARMCLANG, HardFault, state machines, architecture, LVGL patterns, and claim fact-checking. Ships a native DeepSeek Harness (dsh) bundle that injects the session-start gate into the first model step.",
     "type": "module",
     "main": "lib/index.js",
@@ -32,14 +32,15 @@
             "patch": "./cordis.patch.yml"
         },
         "compatibility": {
-            "dsh": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.2 || ^0.1.2-alpha.3",
+            "dsh": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.2 || ^0.1.2-alpha.3 || ^0.1.2-alpha.4",
             "dshReleases": {
                 "0.1.0-rc.7": "compatible",
                 "0.1.0-rc.8": "compatible",
                 "0.1.1-rc.1": "compatible",
                 "0.1.1-rc.2": "compatible",
                 "0.1.2-alpha.2": "compatible",
-                "0.1.2-alpha.3": "compatible"
+                "0.1.2-alpha.3": "compatible",
+                "0.1.2-alpha.4": "compatible"
             },
             "profiles": [
                 "headless"