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

64 lines
2 KiB
JSON
Raw Normal View History

Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
{
"name": "@deepseek-ai/dsh-tool-fs",
"description": "Model-facing filesystem tools (read, write, edit) over the DeepSeek Harness filesystem seam (ctx.fs)",
"version": "0.0.1",
"private": true,
"type": "module",
"main": "lib/index.js",
Merge remote-tracking branch 'origin/master' into fs-tool-clean # Conflicts: # docs/architecture.md # docs/cordis-catalog/events-and-services.md # docs/core-data-structures/core.md # docs/module-graph.md # packages/README.md # scripts/type-equiv.manifest.json # tsconfig.base.json # tsconfig.typecheck.json
2026-06-28 17:24:45 +08:00
"types": "lib/types/index.d.ts",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"exports": {
".": {
Merge remote-tracking branch 'origin/master' into fs-tool-clean # Conflicts: # docs/architecture.md # docs/cordis-catalog/events-and-services.md # docs/core-data-structures/core.md # docs/module-graph.md # packages/README.md # scripts/type-equiv.manifest.json # tsconfig.base.json # tsconfig.typecheck.json
2026-06-28 17:24:45 +08:00
"types": "./lib/types/index.d.ts",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"default": "./lib/index.js"
},
feat(invariants): require package-owned companions
2026-07-19 22:13:50 +08:00
"./invariant": {
"types": "./lib/types/invariant.d.ts",
"default": "./lib/invariant.js"
},
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"./src/*": "./src/*",
"./package.json": "./package.json"
},
"files": [
refactor(tool-fs): drop per-tool subpath plugins; adopt single-tsconfig build Adapt the four fs packages to master's single-tsconfig build convention (lib/types outDir + types path + files allowlist), brought in by the merge. While doing so, drop dsh-tool-fs's /read//write//edit subpath plugins. They were the only subpath-export package in the tree and forced bespoke tsdown, tsconfig path, package.json files, and workspace-constraint handling that no sibling tool package (e.g. dsh-tool-bash) carries, for a focused-deployment use case no consumer needed. dsh-tool-fs is now a single root plugin that registers read/write/edit, mirroring dsh-tool-bash; the per-tool registration helpers stay internal modules the root composes. The file-context event-gate RFC is amended to record the narrowed scope.
2026-06-28 17:43:29 +08:00
"lib/index.js",
feat(invariants): require package-owned companions
2026-07-19 22:13:50 +08:00
"lib/invariant.js",
refactor(tool-fs): drop per-tool subpath plugins; adopt single-tsconfig build Adapt the four fs packages to master's single-tsconfig build convention (lib/types outDir + types path + files allowlist), brought in by the merge. While doing so, drop dsh-tool-fs's /read//write//edit subpath plugins. They were the only subpath-export package in the tree and forced bespoke tsdown, tsconfig path, package.json files, and workspace-constraint handling that no sibling tool package (e.g. dsh-tool-bash) carries, for a focused-deployment use case no consumer needed. dsh-tool-fs is now a single root plugin that registers read/write/edit, mirroring dsh-tool-bash; the per-tool registration helpers stay internal modules the root composes. The file-context event-gate RFC is amended to record the narrowed scope.
2026-06-28 17:43:29 +08:00
"lib/types/**/*.d.ts",
"lib/types/**/*.d.ts.map",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"src"
],
"license": "BSD-3-Clause",
feat(tool-fs): result-time applied-hunk diffs for write/edit fs write/edit now emit a result-time contextual-diff tool_call_update (the applied hunk with ±3 context lines, one hunk per replace_all site), matching what claude-agent-acp sends and what makes an editor render the change in place. The call-time snippet diff stays; the result hunk supersedes it (ACP content-replace). Mechanism: - A persisted tool-private `meta` channel: execute may return `{ content, meta }`; `meta` (JsonValue) rides on the tool/result event and is handed back to presentResult, so the diff reproduces on replay (event-sourced). JsonValue is now exported from dsh-session. - The backend returns raw before/after text (storage facts) on FsWriteOutcome/FsEditOutcome; the tool computes the hunk via the npm `diff` package's structuredPatch. A create has no before → no result diff; a failed/aborted mutation carries no meta. - ToolResultView gains a DiffResultView; the bridge's result-side switch renders it as {type:'diff'} content blocks. RFC: docs/rfc/implemented/architecture/2026-07-02-result-time-applied-hunk-diffs.md (justifies the npm `diff` runtime dep over vendoring and the meta channel); the render-intent-union RFC's Non-goal is updated to record this shipped. All fs snapshot goldens re-recorded; edit/overwrite gain the contextual result diff, create/read/policy-reject unchanged in structure.
2026-07-03 17:12:00 +08:00
"dependencies": {
Expose audited hardcoded tunables as plugin config The audit swept every packages/*/* plugin for the new AGENTS.md convention (no hardcoded tunables in plugins) and exposes each finding as a defaulted, validated Config field. Defaults are the previously hardcoded values throughout, so no deployment or golden changes. - tool-fs (had NO Config): readLimit, readMaxLineLength, readMaxBytes, readStreamMinSize. The caps thread through ReadToolCaps/ReadWindow — read-render already documented that the consumer applies the caps, so they become explicit per-request fields. - tool-web: searchMaxResults (WEB_SEARCH_MAX_RESULTS stays as the schemastery default). Also fixes the stale GREP_LIMIT references in search.ts and the web-capability-seam RFC (no such constant exists). - bash-local: graceMs (SIGTERM->SIGKILL escalation grace). The RunInternals.graceMs test seam is gone: graceMs is now a required SpawnSpec field filled from config, so tests exercise the real config path and the defaults live in exactly one place. - subagent-acp: disposeEofGraceMs / disposeGraceMs. The AcpRunSpec fields become required for the same one-defaulting-layer reason. - session-persistence-sqlite: journalMode ('wal' default; the rollback-journal modes serve filesystems where WAL's shared-memory files do not work, e.g. network mounts). - hooks-claude + hooks-codex: stderrSummaryMaxChars for the persisted hook/result stderr summary. The duplicated summarize() helpers merge into hook-protocol's summarizeStderr(stderr, maxChars), beside the HookResultRecord field it feeds, with the bound parameterized the same way runHook's defaultTimeoutMs already is. - compact-basic: charsPerToken for the token estimator (default 4, the English-text heuristic; CJK-heavy deployments need ~1-2 or compaction fires far too late). Also corrects the BasicCompactService class doc, which claimed defaults the required-field config never had. - fs-local: deletes the dead STREAM_MIN_SIZE constant and the dead FsIoInternals.streamMinSize seam — the read-routing bound lives in the consumer (tool-fs), where it is now config. This is item 1 of the proposed prune-write-only-fs-surface RFC, annotated accordingly. Every new field gets range validation (following the existing assertPositiveFinite pattern), a README row, and tests covering the configured behavior, the schema default, and load-time rejection.
2026-07-04 17:37:23 +08:00
"diff": "^9.0.0",
"schemastery": "^3.18.0"
feat(tool-fs): result-time applied-hunk diffs for write/edit fs write/edit now emit a result-time contextual-diff tool_call_update (the applied hunk with ±3 context lines, one hunk per replace_all site), matching what claude-agent-acp sends and what makes an editor render the change in place. The call-time snippet diff stays; the result hunk supersedes it (ACP content-replace). Mechanism: - A persisted tool-private `meta` channel: execute may return `{ content, meta }`; `meta` (JsonValue) rides on the tool/result event and is handed back to presentResult, so the diff reproduces on replay (event-sourced). JsonValue is now exported from dsh-session. - The backend returns raw before/after text (storage facts) on FsWriteOutcome/FsEditOutcome; the tool computes the hunk via the npm `diff` package's structuredPatch. A create has no before → no result diff; a failed/aborted mutation carries no meta. - ToolResultView gains a DiffResultView; the bridge's result-side switch renders it as {type:'diff'} content blocks. RFC: docs/rfc/implemented/architecture/2026-07-02-result-time-applied-hunk-diffs.md (justifies the npm `diff` runtime dep over vendoring and the meta channel); the render-intent-union RFC's Non-goal is updated to record this shipped. All fs snapshot goldens re-recorded; edit/overwrite gain the contextual result diff, create/read/policy-reject unchanged in structure.
2026-07-03 17:12:00 +08:00
},
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"peerDependencies": {
"@deepseek-ai/dsh-fs": "^0.0.1",
feat(invariants): require package-owned companions
2026-07-19 22:13:50 +08:00
"@deepseek-ai/dsh-invariants": "^0.0.1",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"@deepseek-ai/dsh-llm": "^0.0.1",
feat(sandbox): cross-family file sandbox — one policy home, sandboxed fs provider, fs escalation parity Extend SandboxMode enforcement from bash to the filesystem tools, the sandbox RFC's deferred cross-family phase. - dsh-sandbox-policy (new, ctx.sandboxPolicy): the single home for the deployment default mode + workspaceRoot and the per-session override event, renamed bash/sandbox-mode -> sandbox/mode and moved here with its fold/setter. Decouples the bash seam from dsh-session. - dsh-fs-sandbox (new): SandboxedFileSystem extends LocalFileSystem and fences write/edit by the per-call mode (read-only denies, workspace-write contains to the workspace + temp roots via the shared writableRoots, danger passes through); reads pass through. Structured FS_SANDBOX_DENIED; in-lock parent re-canonicalization. A policy fence in trusted code, not a kernel boundary. - dsh-sandbox: the shared escalation kit (writableRoots, the strictly-wider ladder, denial/hint markers, approveEscalation) both tool families use; approveEscalation takes a structural approver so dsh-sandbox gains no approval/agent dependency, and both tools stay duplication-free. - tool-fs: write/edit advertise sandbox_permissions/justification under a confining ctx.fs, map FS_SANDBOX_DENIED to the shared [sandbox: ...] marker, and resolve the same one-approved-wider retry. - examples/acp-agent: composes sandbox-policy + fs-sandbox, drops the gating that disabled the fs stack under confined modes. RFC docs/rfc/implemented/feature/2026-07-14-cross-family-fs-sandbox.md; the old sandbox RFC's In-process/deferred/FAQ sections updated to shipped fact.
2026-07-14 20:05:57 +08:00
"@deepseek-ai/dsh-sandbox": "^0.0.1",
"@deepseek-ai/dsh-sandbox-policy": "^0.0.1",
feat(tool-fs): result-time applied-hunk diffs for write/edit fs write/edit now emit a result-time contextual-diff tool_call_update (the applied hunk with ±3 context lines, one hunk per replace_all site), matching what claude-agent-acp sends and what makes an editor render the change in place. The call-time snippet diff stays; the result hunk supersedes it (ACP content-replace). Mechanism: - A persisted tool-private `meta` channel: execute may return `{ content, meta }`; `meta` (JsonValue) rides on the tool/result event and is handed back to presentResult, so the diff reproduces on replay (event-sourced). JsonValue is now exported from dsh-session. - The backend returns raw before/after text (storage facts) on FsWriteOutcome/FsEditOutcome; the tool computes the hunk via the npm `diff` package's structuredPatch. A create has no before → no result diff; a failed/aborted mutation carries no meta. - ToolResultView gains a DiffResultView; the bridge's result-side switch renders it as {type:'diff'} content blocks. RFC: docs/rfc/implemented/architecture/2026-07-02-result-time-applied-hunk-diffs.md (justifies the npm `diff` runtime dep over vendoring and the meta channel); the render-intent-union RFC's Non-goal is updated to record this shipped. All fs snapshot goldens re-recorded; edit/overwrite gain the contextual result diff, create/read/policy-reject unchanged in structure.
2026-07-03 17:12:00 +08:00
"@deepseek-ai/dsh-session": "^0.0.1",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"@deepseek-ai/dsh-system-prompt": "^0.0.1",
"@deepseek-ai/dsh-tools": "^0.0.1",
feat(sandbox): cross-family file sandbox — one policy home, sandboxed fs provider, fs escalation parity Extend SandboxMode enforcement from bash to the filesystem tools, the sandbox RFC's deferred cross-family phase. - dsh-sandbox-policy (new, ctx.sandboxPolicy): the single home for the deployment default mode + workspaceRoot and the per-session override event, renamed bash/sandbox-mode -> sandbox/mode and moved here with its fold/setter. Decouples the bash seam from dsh-session. - dsh-fs-sandbox (new): SandboxedFileSystem extends LocalFileSystem and fences write/edit by the per-call mode (read-only denies, workspace-write contains to the workspace + temp roots via the shared writableRoots, danger passes through); reads pass through. Structured FS_SANDBOX_DENIED; in-lock parent re-canonicalization. A policy fence in trusted code, not a kernel boundary. - dsh-sandbox: the shared escalation kit (writableRoots, the strictly-wider ladder, denial/hint markers, approveEscalation) both tool families use; approveEscalation takes a structural approver so dsh-sandbox gains no approval/agent dependency, and both tools stay duplication-free. - tool-fs: write/edit advertise sandbox_permissions/justification under a confining ctx.fs, map FS_SANDBOX_DENIED to the shared [sandbox: ...] marker, and resolve the same one-approved-wider retry. - examples/acp-agent: composes sandbox-policy + fs-sandbox, drops the gating that disabled the fs stack under confined modes. RFC docs/rfc/implemented/feature/2026-07-14-cross-family-fs-sandbox.md; the old sandbox RFC's In-process/deferred/FAQ sections updated to shipped fact.
2026-07-14 20:05:57 +08:00
"@deepseek-ai/dsh-user-approval": "^0.0.1",
pkg: update vendor dep
2026-07-15 11:28:45 +08:00
"cordis": "^4.0.0-rc.7"
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
},
"devDependencies": {
"@deepseek-ai/dsh-agent": "workspace:^",
test(fs): close abort/concurrency/observed coverage gaps + with-key e2e Behavioral gaps from the coverage audit (line coverage was already 100%; these close BEHAVIOR gaps): - fs-local: service-level writeText/editText pre-abort → FS_ABORTED (file unchanged); concurrent guarded-write race and mixed write-vs-edit race (one wins, one FS_STALE_VERSION, locks released); edit→edit version refresh at the provider; the replaceIfVersion post-write version matches a fresh stat. fsio: a mid-stream abort → FS_ABORTED (previously only pre-abort was covered). - fs-policy: the agent-without-session owner rung ({agent:{}} → no owner → createIfAbsent / FS_NOT_OBSERVED); fs/write-intent first-wins (symmetric to the existing edit-intent test). - tool-fs: abort-through-the-tool for read/write/edit (isError FS_ABORTED, file unchanged); a deterministic tool-tier concurrent-edit race via a shared read; the throwing-fs/observed contract (a throwing listener surfaces as isError but the mutation already hit disk); the replace_all edit message; parseReadArgs rejects fractional/NaN offset and zero/negative limit. - dsh-fs: FsError chains a cause through ErrorOptions. New with-key e2e (packages/fs/tool-fs/tests/fs-tools.e2e.ts, self-skips without DEEPSEEK_API_KEY): a real model drives the real read/write/edit tools to create → read → edit a file, verified on disk; a second test proves a relative path resolves against the per-session cwd (factory meta.cwd) not config.cwd. Booted via a plain tests/harness.ts. Added dsh-agent-loop + dsh-llm-deepseek devDeps.
2026-07-02 20:38:06 +08:00
"@deepseek-ai/dsh-agent-loop": "workspace:^",
test(support): add shared AgentLoop testkit
2026-07-16 17:39:53 +08:00
"@deepseek-ai/dsh-agent-loop-testkit": "workspace:^",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"@deepseek-ai/dsh-fs": "workspace:^",
"@deepseek-ai/dsh-fs-local": "workspace:^",
feat(invariants): require package-owned companions
2026-07-19 22:13:50 +08:00
"@deepseek-ai/dsh-fs-policy": "workspace:^",
"@deepseek-ai/dsh-invariants": "workspace:^",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"@deepseek-ai/dsh-llm": "workspace:^",
test(fs): close abort/concurrency/observed coverage gaps + with-key e2e Behavioral gaps from the coverage audit (line coverage was already 100%; these close BEHAVIOR gaps): - fs-local: service-level writeText/editText pre-abort → FS_ABORTED (file unchanged); concurrent guarded-write race and mixed write-vs-edit race (one wins, one FS_STALE_VERSION, locks released); edit→edit version refresh at the provider; the replaceIfVersion post-write version matches a fresh stat. fsio: a mid-stream abort → FS_ABORTED (previously only pre-abort was covered). - fs-policy: the agent-without-session owner rung ({agent:{}} → no owner → createIfAbsent / FS_NOT_OBSERVED); fs/write-intent first-wins (symmetric to the existing edit-intent test). - tool-fs: abort-through-the-tool for read/write/edit (isError FS_ABORTED, file unchanged); a deterministic tool-tier concurrent-edit race via a shared read; the throwing-fs/observed contract (a throwing listener surfaces as isError but the mutation already hit disk); the replace_all edit message; parseReadArgs rejects fractional/NaN offset and zero/negative limit. - dsh-fs: FsError chains a cause through ErrorOptions. New with-key e2e (packages/fs/tool-fs/tests/fs-tools.e2e.ts, self-skips without DEEPSEEK_API_KEY): a real model drives the real read/write/edit tools to create → read → edit a file, verified on disk; a second test proves a relative path resolves against the per-session cwd (factory meta.cwd) not config.cwd. Booted via a plain tests/harness.ts. Added dsh-agent-loop + dsh-llm-deepseek devDeps.
2026-07-02 20:38:06 +08:00
"@deepseek-ai/dsh-llm-deepseek": "workspace:^",
feat(sandbox): cross-family file sandbox — one policy home, sandboxed fs provider, fs escalation parity Extend SandboxMode enforcement from bash to the filesystem tools, the sandbox RFC's deferred cross-family phase. - dsh-sandbox-policy (new, ctx.sandboxPolicy): the single home for the deployment default mode + workspaceRoot and the per-session override event, renamed bash/sandbox-mode -> sandbox/mode and moved here with its fold/setter. Decouples the bash seam from dsh-session. - dsh-fs-sandbox (new): SandboxedFileSystem extends LocalFileSystem and fences write/edit by the per-call mode (read-only denies, workspace-write contains to the workspace + temp roots via the shared writableRoots, danger passes through); reads pass through. Structured FS_SANDBOX_DENIED; in-lock parent re-canonicalization. A policy fence in trusted code, not a kernel boundary. - dsh-sandbox: the shared escalation kit (writableRoots, the strictly-wider ladder, denial/hint markers, approveEscalation) both tool families use; approveEscalation takes a structural approver so dsh-sandbox gains no approval/agent dependency, and both tools stay duplication-free. - tool-fs: write/edit advertise sandbox_permissions/justification under a confining ctx.fs, map FS_SANDBOX_DENIED to the shared [sandbox: ...] marker, and resolve the same one-approved-wider retry. - examples/acp-agent: composes sandbox-policy + fs-sandbox, drops the gating that disabled the fs stack under confined modes. RFC docs/rfc/implemented/feature/2026-07-14-cross-family-fs-sandbox.md; the old sandbox RFC's In-process/deferred/FAQ sections updated to shipped fact.
2026-07-14 20:05:57 +08:00
"@deepseek-ai/dsh-sandbox": "workspace:^",
"@deepseek-ai/dsh-sandbox-policy": "workspace:^",
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
"@deepseek-ai/dsh-session": "workspace:^",
"@deepseek-ai/dsh-system-prompt": "workspace:^",
"@deepseek-ai/dsh-tools": "workspace:^",
feat(sandbox): cross-family file sandbox — one policy home, sandboxed fs provider, fs escalation parity Extend SandboxMode enforcement from bash to the filesystem tools, the sandbox RFC's deferred cross-family phase. - dsh-sandbox-policy (new, ctx.sandboxPolicy): the single home for the deployment default mode + workspaceRoot and the per-session override event, renamed bash/sandbox-mode -> sandbox/mode and moved here with its fold/setter. Decouples the bash seam from dsh-session. - dsh-fs-sandbox (new): SandboxedFileSystem extends LocalFileSystem and fences write/edit by the per-call mode (read-only denies, workspace-write contains to the workspace + temp roots via the shared writableRoots, danger passes through); reads pass through. Structured FS_SANDBOX_DENIED; in-lock parent re-canonicalization. A policy fence in trusted code, not a kernel boundary. - dsh-sandbox: the shared escalation kit (writableRoots, the strictly-wider ladder, denial/hint markers, approveEscalation) both tool families use; approveEscalation takes a structural approver so dsh-sandbox gains no approval/agent dependency, and both tools stay duplication-free. - tool-fs: write/edit advertise sandbox_permissions/justification under a confining ctx.fs, map FS_SANDBOX_DENIED to the shared [sandbox: ...] marker, and resolve the same one-approved-wider retry. - examples/acp-agent: composes sandbox-policy + fs-sandbox, drops the gating that disabled the fs stack under confined modes. RFC docs/rfc/implemented/feature/2026-07-14-cross-family-fs-sandbox.md; the old sandbox RFC's In-process/deferred/FAQ sections updated to shipped fact.
2026-07-14 20:05:57 +08:00
"@deepseek-ai/dsh-user-approval": "workspace:^",
pkg: update vendor dep
2026-07-15 11:28:45 +08:00
"cordis": "^4.0.0-rc.7"
Add filesystem capability seam and tools
2026-06-22 10:48:41 +08:00
}
}
Reference in a new issue Copy permalink