kevchess15/deepseek-harness
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
deepseek-harness/packages/plan/plan-mode/package.json

78 lines
2.3 KiB
JSON
Raw Normal View History

feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
{
refactor(plan): remove generic mode abstraction
2026-07-22 16:57:23 +08:00
"name": "@deepseek-ai/dsh-plan-mode",
"description": "Logged per-agent plan mode with deployment guidance, a direct slash command, and a user-reviewed exit",
release(dsh): 0.1.1-rc.2
2026-08-21 19:48:58 +08:00
"version": "0.1.1-rc.2",
build(release): make the release set publishable under the private scope Every package under packages/, apps/, and vendor/ drops "private": true and declares publishConfig.access "restricted": the repository now states which packages it publishes instead of deciding it at publish time. Each one also declares its repository and directory, which is how a consumer of a private package reaches its source. The Landlock packages move to restricted with them. They have never been published, so nothing anonymous depends on them today, and the whole @deepseek-ai scope stays private. The workspace constraint that required every package to be private now applies to non-members only, and asserts the publishable trio on each release member.
2026-08-11 00:02:53 +08:00
"publishConfig": {
build(release): publish the dsh family publicly Every release member now declares publishConfig.access: public, so the scope no longer mixes levels: the 221 packages/*/* and apps/* manifests join the vendored framework and the native packages. check-workspace-constraints drops the per-sequence expectation and holds every release member to public, which is what stops a member from drifting back. Access is a property of the package, not of a version: the dsh packages already published as restricted become world-readable at their next publication.
2026-08-13 18:05:10 +08:00
"access": "public"
build(release): make the release set publishable under the private scope Every package under packages/, apps/, and vendor/ drops "private": true and declares publishConfig.access "restricted": the repository now states which packages it publishes instead of deciding it at publish time. Each one also declares its repository and directory, which is how a consumer of a private package reaches its source. The Landlock packages move to restricted with them. They have never been published, so nothing anonymous depends on them today, and the whole @deepseek-ai scope stays private. The workspace constraint that required every package to be private now applies to non-members only, and asserts the publishable trio on each release member.
2026-08-11 00:02:53 +08:00
},
"repository": {
"type": "git",
"url": "git+https://github.com/deepseek-ai/deepseek-harness.git",
"directory": "packages/plan/plan-mode"
},
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"type": "module",
"main": "lib/index.js",
"types": "lib/types/index.d.ts",
"exports": {
".": {
"types": "./lib/types/index.d.ts",
"default": "./lib/index.js"
},
Merge remote-tracking branch 'origin/master' into feat/plan-mode Master arrivals re-grafted onto the plan-mode surfaces: - Package invariant runtime contracts: every package owns ./invariant — added the dsh-mode companion (mode/set payload validation: non-empty trimmed name), its unit spec, exports/peer wiring, and the mode group in the tsconfig invariant paths glob. - Interception waterfalls gained an AbortSignal parameter (agent/prompt-submit, agent/turn-continuation) and ToolExecutionInput.signal became required: listeners and test dispatch updated; the exit tool now forwards exec.signal unconditionally. - TUI question dialog: master's position/unanswered header layout kept, the plan-review detail block re-grafted between question and answers. - LSP capability family arrived: lsp tool joins the catalog pin, dsh-lsp examples deps beside dsh-mode; lsp-definition snapshot refreshed with the mode command and modes advertisement. - docs/architecture.md and packages/README.md regenerated tables re-grafted (ctx.modes row, mode package row) and condensed within word ceilings. - examples/acp-agent cordis.yml: kept the deployment-owned plan instructions (incl. the conversational-agreement sentence) beside master's routed-model compaction comment; snapshot expected outputs refreshed keyless and noise fixtures restored.
2026-07-22 02:13:39 +08:00
"./invariant": {
"types": "./lib/types/invariant.d.ts",
"default": "./lib/invariant.js"
},
feat(plan): register the plan session-projection unit plan-mode contributes the RFC's complete double-event example: command/run records named plan set the wanted target (off -> false, else true), plan/mode commits and clears it, and view derives {active, pending}. Pending is thereby a pure replay quantity recovered from the log alone. The plan key merges into SessionProjectionMap from src/types.ts, served through the new ./types and ./client outlets (session-title template); compositions without the registry are unaffected.
2026-07-28 20:46:46 +08:00
"./types": {
"types": "./lib/types/types.d.ts",
"default": "./lib/types/types.js"
},
"./client": {
"types": "./lib/types/client.d.ts",
"default": "./lib/types/client.js"
},
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"./src/*": "./src/*",
"./package.json": "./package.json"
},
"files": [
"lib/index.js",
Merge remote-tracking branch 'origin/master' into feat/plan-mode Master arrivals re-grafted onto the plan-mode surfaces: - Package invariant runtime contracts: every package owns ./invariant — added the dsh-mode companion (mode/set payload validation: non-empty trimmed name), its unit spec, exports/peer wiring, and the mode group in the tsconfig invariant paths glob. - Interception waterfalls gained an AbortSignal parameter (agent/prompt-submit, agent/turn-continuation) and ToolExecutionInput.signal became required: listeners and test dispatch updated; the exit tool now forwards exec.signal unconditionally. - TUI question dialog: master's position/unanswered header layout kept, the plan-review detail block re-grafted between question and answers. - LSP capability family arrived: lsp tool joins the catalog pin, dsh-lsp examples deps beside dsh-mode; lsp-definition snapshot refreshed with the mode command and modes advertisement. - docs/architecture.md and packages/README.md regenerated tables re-grafted (ctx.modes row, mode package row) and condensed within word ceilings. - examples/acp-agent cordis.yml: kept the deployment-owned plan instructions (incl. the conversational-agreement sentence) beside master's routed-model compaction comment; snapshot expected outputs refreshed keyless and noise fixtures restored.
2026-07-22 02:13:39 +08:00
"lib/invariant.js",
feat(plan): register the plan session-projection unit plan-mode contributes the RFC's complete double-event example: command/run records named plan set the wanted target (off -> false, else true), plan/mode commits and clears it, and view derives {active, pending}. Pending is thereby a pure replay quantity recovered from the log alone. The plan key merges into SessionProjectionMap from src/types.ts, served through the new ./types and ./client outlets (session-title template); compositions without the registry are unaffected.
2026-07-28 20:46:46 +08:00
"lib/types/**/*.js",
fix(packages): omit source publication payloads
2026-08-04 22:06:32 +08:00
"lib/types/**/*.d.ts"
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
],
Adopt MIT for DSH packages
2026-08-13 01:46:57 +08:00
"license": "MIT",
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"peerDependencies": {
build(release): reference workspace members through the workspace protocol 1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
2026-08-11 00:16:45 +08:00
"@deepseek-ai/dsh-agent": "workspace:^",
"@deepseek-ai/dsh-commands": "workspace:^",
"@deepseek-ai/dsh-invariants": "workspace:^",
"@deepseek-ai/dsh-llm": "workspace:^",
"@deepseek-ai/dsh-session": "workspace:^",
"@deepseek-ai/dsh-session-projection": "workspace:^",
"@deepseek-ai/dsh-system-prompt": "workspace:^",
"@deepseek-ai/dsh-tools": "workspace:^",
refactor: apply repository naming contract Apply the accepted pre-release package, service, type, directory, and role renames as one repository-wide change.
2026-08-13 00:36:22 +08:00
"@deepseek-ai/dsh-user-questions": "workspace:^",
build(release): reference workspace members through the workspace protocol 1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
2026-08-11 00:16:45 +08:00
"@deepseek-ai/cordis": "workspace:^"
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
},
refactor(mode): move exit-tool visibility onto the registry restriction layer; register /mode; drop unconsumed surfaces The master merge brought the tool registry's per-scope restriction layer (tools.restrict), which makes dsh-mode's prepend assemble filter a duplicate enforcement shape: it re-implemented the registry's SDK-section rendering (renderToolsSdk + the RUN_CODE_NAME exclusion) and hid the exit tool from prompts only — dispatch stayed open and the execute-time re-check was the real gate. The service now reconciles a per-agent deny restriction on agent.ctx at agent/created and at every boundary flush, so wire schemas, the Code Mode tools:sdk section, AND dispatch resolve exit_plan_mode through the one registry view (a default-mode call answers UNKNOWN_TOOL, byte-identical to a no-dsh-mode deployment). The execute-time folded-mode re-check stays as defense in depth for a direct foreign mode/set append no boundary has reconciled yet. Two zero-consumer surfaces removed per the pre-release stance: - AgentOptions.mode creation seeding (declaration merge + agent/created listener); a caller selects through set() before the first turn, and the deferred subagent inheritance returns together with its consumer. - The dropped-definition boundary notice (droppedNoticed + narration): custom mode definitions have no production consumer, so nothing can be dropped; fold-to-default degradation is unchanged. The stdio removal had left plan mode ACP-only while docs still claimed a /mode command. dsh-mode now registers /mode on the plugin-owned command registry through an optional ctx.inject(['commands']) child (type-only peer edge on dsh-commands), so the TUI and the ACP slash-command surface both gain it; examples/tui-agent composes dsh-mode. ACP/TUI expected outputs refreshed keyless for the available_commands_update delta. Docs updated in place (mode READMEs, the plan-mode Agent Note's realization sections); catalogs and graphs regenerated.
2026-07-21 11:11:35 +08:00
"peerDependenciesMeta": {
"@deepseek-ai/dsh-commands": {
"optional": true
}
},
feat(plan): register the plan session-projection unit plan-mode contributes the RFC's complete double-event example: command/run records named plan set the wanted target (off -> false, else true), plan/mode commits and clears it, and view derives {active, pending}. Pending is thereby a pure replay quantity recovered from the log alone. The plan key merges into SessionProjectionMap from src/types.ts, served through the new ./types and ./client outlets (session-title template); compositions without the registry are unaffected.
2026-07-28 20:46:46 +08:00
"dependencies": {
"zod": "^4.4.3"
},
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"devDependencies": {
"@deepseek-ai/dsh-agent": "workspace:^",
"@deepseek-ai/dsh-agent-loop": "workspace:^",
fix(mode): run_code passes both layers as a transport — Code Mode composes with plan mode Review finding, valid: under the registry's Code Mode the assembly's only wire tool is run_code, which the plan allowlist filtered out — leaving the model with NO tools at all, the exit review included. The composition exists today (the acp-agent example ships a code-mode overlay), so plan mode bricked it outright. run_code is a transport, not a capability: every bridged sub-call is serialized back through ToolRegistry.execute() carrying the same agent, so tools/pre-execute judges each capability individually — exactly like native calls. Both layers now exempt it by name: the filter keeps it visible (tests pin plan-mode Code Mode assembly = ['run_code']) and the gate passes the wrapper while the same run's write sub-call still denies with the plan-mode reason. Documented residual, same class as the prepend-after-load one: the SDK section renders from the registry's store, so a plan-mode program may be offered bindings whose dispatch the gate then denies — nothing runs that a native call could not.
2026-07-10 20:26:59 +08:00
"@deepseek-ai/dsh-code-runtime": "workspace:^",
refactor(mode): move exit-tool visibility onto the registry restriction layer; register /mode; drop unconsumed surfaces The master merge brought the tool registry's per-scope restriction layer (tools.restrict), which makes dsh-mode's prepend assemble filter a duplicate enforcement shape: it re-implemented the registry's SDK-section rendering (renderToolsSdk + the RUN_CODE_NAME exclusion) and hid the exit tool from prompts only — dispatch stayed open and the execute-time re-check was the real gate. The service now reconciles a per-agent deny restriction on agent.ctx at agent/created and at every boundary flush, so wire schemas, the Code Mode tools:sdk section, AND dispatch resolve exit_plan_mode through the one registry view (a default-mode call answers UNKNOWN_TOOL, byte-identical to a no-dsh-mode deployment). The execute-time folded-mode re-check stays as defense in depth for a direct foreign mode/set append no boundary has reconciled yet. Two zero-consumer surfaces removed per the pre-release stance: - AgentOptions.mode creation seeding (declaration merge + agent/created listener); a caller selects through set() before the first turn, and the deferred subagent inheritance returns together with its consumer. - The dropped-definition boundary notice (droppedNoticed + narration): custom mode definitions have no production consumer, so nothing can be dropped; fold-to-default degradation is unchanged. The stdio removal had left plan mode ACP-only while docs still claimed a /mode command. dsh-mode now registers /mode on the plugin-owned command registry through an optional ctx.inject(['commands']) child (type-only peer edge on dsh-commands), so the TUI and the ACP slash-command surface both gain it; examples/tui-agent composes dsh-mode. ACP/TUI expected outputs refreshed keyless for the available_commands_update delta. Docs updated in place (mode READMEs, the plan-mode Agent Note's realization sections); catalogs and graphs regenerated.
2026-07-21 11:11:35 +08:00
"@deepseek-ai/dsh-commands": "workspace:^",
Merge remote-tracking branch 'origin/master' into feat/plan-mode Master arrivals re-grafted onto the plan-mode surfaces: - Package invariant runtime contracts: every package owns ./invariant — added the dsh-mode companion (mode/set payload validation: non-empty trimmed name), its unit spec, exports/peer wiring, and the mode group in the tsconfig invariant paths glob. - Interception waterfalls gained an AbortSignal parameter (agent/prompt-submit, agent/turn-continuation) and ToolExecutionInput.signal became required: listeners and test dispatch updated; the exit tool now forwards exec.signal unconditionally. - TUI question dialog: master's position/unanswered header layout kept, the plan-review detail block re-grafted between question and answers. - LSP capability family arrived: lsp tool joins the catalog pin, dsh-lsp examples deps beside dsh-mode; lsp-definition snapshot refreshed with the mode command and modes advertisement. - docs/architecture.md and packages/README.md regenerated tables re-grafted (ctx.modes row, mode package row) and condensed within word ceilings. - examples/acp-agent cordis.yml: kept the deployment-owned plan instructions (incl. the conversational-agreement sentence) beside master's routed-model compaction comment; snapshot expected outputs refreshed keyless and noise fixtures restored.
2026-07-22 02:13:39 +08:00
"@deepseek-ai/dsh-invariants": "workspace:^",
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"@deepseek-ai/dsh-llm": "workspace:^",
"@deepseek-ai/dsh-session": "workspace:^",
feat(plan): register the plan session-projection unit plan-mode contributes the RFC's complete double-event example: command/run records named plan set the wanted target (off -> false, else true), plan/mode commits and clears it, and view derives {active, pending}. Pending is thereby a pure replay quantity recovered from the log alone. The plan key merges into SessionProjectionMap from src/types.ts, served through the new ./types and ./client outlets (session-title template); compositions without the registry are unaffected.
2026-07-28 20:46:46 +08:00
"@deepseek-ai/dsh-session-projection": "workspace:^",
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
"@deepseek-ai/dsh-system-prompt": "workspace:^",
"@deepseek-ai/dsh-tools": "workspace:^",
refactor: apply repository naming contract Apply the accepted pre-release package, service, type, directory, and role renames as one repository-wide change.
2026-08-13 00:36:22 +08:00
"@deepseek-ai/dsh-user-questions": "workspace:^",
build(release): reference workspace members through the workspace protocol 1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
2026-08-11 00:16:45 +08:00
"@deepseek-ai/cordis": "workspace:^"
feat(mode): the session-mode core — logged per-agent policy state (@deepseek-ai/dsh-mode) Plan mode's stage 1 (RFC 2026-07-07-plan-mode): a new packages/mode/ group with one product package owning the mode/set SessionEventMap vocabulary (log-only, non-surface, whole-value replace), the pure foldMode, and the ctx.modes service (list/get/set). User flips are pending intents flushed at turn/start / step/end — turn enclosure makes an idle append illegal — with one coalesced context/message notice when the flushed mode differs from what the last logged request header told the model; a folded mode the config no longer defines reads as default plus one boundary notice. Enforcement is two covering layers: a system-prompt/assemble wrapper filters the RETURNED assembly's tools to the mode's allowlist (and shows exit_plan_mode IFF the folded mode is plan) beside the mode:policy section at order 50, and a tools/pre-execute gate denies deny-by-default against the same allowlist, judging by the logged mode only. The default mode is the absence of policy — assemblies stay byte-identical to a no-dsh-mode deployment. AgentOptions.mode (declaration-merged) seeds a child's initial mode through the same flush on agent/created; the stdio app gains /mode (print/switch, never sent to the model) over an opportunistic ctx.get('modes'). Config is an explicit resolve step: the built-in plan definition (read-only allowlist; bash/subagent excluded until the sandbox family lands) merges unless overridden, 'default' as a key throws at load, unknown names throw at set() time.
2026-07-10 01:38:39 +08:00
}
}
Reference in a new issue Copy permalink