Add the activity capability seam: ctx.activities is a pure observation
plane where long-running work (background bash/pwsh, workflow runs) opens a
handle, appends transient output into a byte-offset ring buffer, and settles
exactly once. Nothing model-visible changes: reads are non-consuming and
lossy-by-design (absolute UTF-8 offsets survive eviction and report gaps),
correlation carries {callId, jobId}, and visibility is owner-fenced like jobs.
The seam is strictly optional. Producers tap it through ctx.get('activities')
and contain every observation failure, so an unregistered or broken registry
never affects the underlying job (proven by broken-registry tests).
Ship the full path in one change:
- @deepseek-ai/dsh-activity: Service Definition, pumpActivityOutput pull
substrate, invariant companion; dsh-activity-local: ring-buffer provider
with retention config and owner cleanup.
- shell: ShellProcess.observed exposes non-consuming stdout/stderr readers;
tool-bash/tool-pwsh mirror background jobs into activities.
- tool-workflow: phase/log/agent lines mirrored as a workflow activity.
- api-activity-controller: Typert Remote control (roster baseline+buckets)
and observe (opened/output/status frames, coalesced and byte-capped)
streams plus the client feed service with reference-counted observation.
- ui-activity: session-header action rendering live output through
TerminalBlock, which now shows output while a command is still running.
Docs: activity subsystem page, architecture row, regenerated catalogs, and
the Agent Note (2026-08-24-activity-observation-seam), all bilingual. A
keyless web e2e replays a real run_in_background stream to ARIA goldens.
workflow/ — dynamic-workflow capability family
English | 中文
This family runs model-authored orchestration workflows over subagents and exposes general and fixed-policy tools to the model.
| Package | Role | ctx key |
|---|---|---|
workflow/ |
Defines workflow execution and lifecycle events | ctx.workflowEngine |
workflow-worker-thread/ |
Runs workflow scripts in worker threads | registers on ctx.workflowEngine |
tool-workflow/ |
Exposes general workflow execution to the model | registers on ctx.tools |
tool-ralph/ |
Exposes the fixed fresh-agent Ralph workflow | registers on ctx.tools |
Worker threads isolate workflow execution from the host event loop but are not a security boundary. See the dynamic-workflow and Ralph tool decisions.
The subsystem reference — start requests, WorkflowMeta, results, live runs, workflow/* events — is docs/subsystems/workflow.md; decisions in the dynamic-workflows and Ralph consumer Agent Notes.