mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-14 04:01:35 +00:00
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
2.1 KiB
2.1 KiB
description, kind
| description | kind |
|---|---|
| The jobs group map: background-job control — the registry contract, process-local storage, and the model-facing job tools — for users and maintainers navigating the group. | package-group |
jobs/ — background-job capability family
English | 中文
Summary
The jobs group is the background-work capability family: tools that run long work register it as a job, and the owning agent can read, wait on, list, and cancel it without blocking its own turn. Jobs belong to the agent session that started them, so one agent never sees another's work, and completion is delivered to the owning agent in-session instead of polled. The group splits into the registry contract (jobs), its process-local storage (jobs-local), and the model-facing control tools with completion notices (tool-jobs).
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
jobs |
Defines the background-job contract: ids, ownership, lifecycle, and completion listeners | ctx.jobs |
jobs-local |
Runs and stores jobs in this process, fenced per owner | registers on ctx.jobs |
tool-jobs |
Lets the model read, list, and kill jobs and delivers completion notices | registers on ctx.tools |
Related documentation
- Background task runtime subsystem — the job types, snapshot fields, and the
ctx.jobsAPI. - Generic long-running tool runtime Agent Note — the design behind the background-job runtime.
- job-registry seam Agent Note — the owner-fenced registry contract and its rationale.
Dev Note
Working context for maintainers — click to expand
None.