Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| Host and Client job control: the roster one session can see and one job's retained output, mirrored to the browser without touching the model's consuming cursor, and a kill on a human's behalf. | package-reference |
Job Controller
English | 中文
Summary
@deepseek-ai/dsh-api-job-controller owns the Host ctx.jobController service and the generated Client ctx.remote.job namespace. Its two Remote streams are projections of ctx.jobs: job.list mirrors the jobs one session can see as whole-set frames, and job.follow delivers one job's retained output from an absolute byte offset; its one command, job.kill, stops a job on a human's behalf. The Client half installs ctx.jobs, the reference-counted service whose rosters and accumulated views the session-header job list renders and whose kill its stop control calls. Neither stream touches the model's consuming cursor or its completion notices, and a human kill is not the model's own.
Table of Contents
Use this package
The Host controller requires the live Agent registry and the job registry (dsh-jobs-local in the shipped compositions) and fails to load without them. job.list({ sessionId }) yields the session's visible set — its own jobs plus every unowned job — once on open and again after each coalesced burst of lifecycle commits (registration, progress, stopping, settlement, removal); output appends never refresh the roster, since a settled projection already carries the final byte count. job.follow({ sessionId?, jobId, from? }) passes sessionId to registry get and readAt — an unowned job needs no session — and yields one opened anchor carrying the job projection, coalesced output frames, then one terminal status once the job has settled and its ring is drained, after which the stream closes normally; a removal announced mid-stream (the owner's teardown) closes it with the removed job's terminal projection. Both reads are non-consuming: the model's job_output cursor and notice state never observe them.
job.kill({ sessionId, jobId }) cancels one job the session can see with the reason cancelled by the user, which the registry merges into the killed job's detail. It is not a kill the model requested — dsh-tool-jobs withholds a notice only for the model's own job_kill and for settlements a live wait collected — so the owning agent's completion notice stays due, reason included, and a shell tool still waiting on that job reads the reason as [stopped: cancelled by the user] in its own result. It answers { outcome: 'requested' } or { outcome: 'already-finished' } and rejects an id the session cannot see as job/not-found; the registry's owner fence is the only access rule, so a child session's own jobs are killable from its list like any other.
The Client entry installs ctx.jobs (IJobs), backed by the package-internal ClientJobsModel. kill(sessionId, jobId) forwards to job.kill and returns the Remote result for the caller's admission verdict. watchRows(sessionId) keeps one roster stream open per watched session however many viewers hold it and drops the rows after the last release; a reconnect's first frame is already the whole truth. observe(sessionId, jobId) opens one Gateway stream per job however many viewers expand it, keeps a bounded render tail per job with gapBefore marking eviction or resume gaps, closes the view on the terminal frame or records a stream failure on it, and drops the view after the last viewer releases. The plugin resolves the Gateway stream factory and the job namespace while its own context is current, because stream (re)opens run on caller stacks whose dynamic context has not declared remote.job.
Config
| Field | Default | Meaning |
|---|---|---|
observeFlushMs |
100 |
Coalescing window after a registry commit before the next rows or output read, in milliseconds |
observeMaxFrameBytes |
65,536 |
Soft byte budget per observation output frame; one larger chunk ships whole |
The generated configuration catalog is the exhaustive source for accepted fields and their JSDoc.
Model Experience
None, as job observation is browser and Host control state; it registers no prompt, tool, or session event. The model's own view of the same work stays with dsh-tool-jobs.
KV Cache effect
No direct effect; observation reads never touch model requests.
Known Limitations and Deferred Work
- The ring is a best-effort live preview, not a terminal transcript: producers' pull sources are copied per poll round, so two streams' writes inside one poll window land stdout first, and the client concatenates chunks regardless of
channel. - Both streams are process-local: a Host restart loses every ring and roster; a resumed observation then anchors on an empty registry, and a re-opened roster starts empty.
- Per-session fencing is enforced by the caller argument of each registry read; the Remote layer itself serves any connected browser.
Dev Note
Working context for maintainers — click to expand
None.