_Kerman
107e05e79b
The mount-local baseline guard was seeded from "a baseline already exists in the log", which a resumed session and a hot plugin remount both satisfy. That made a resume skip its baseline, so offline AGENTS.md edits or removals never reached the first resumed request — violating the documented resume contract. Distinguish the two by agent/session-start: a startup or resume emits it before the first step, while a remount attaches to an already-live session and never witnesses it. Only a remount (no witnessed start, baseline already logged) keeps the single logged baseline and skips; a resume falls through and re-composes from current files. Adds a regression that resumes a session with an offline baseline edit and asserts the fresh baseline reflects it.
context/ — request-context extensions
English | 中文
Product plugins that add model-visible request context without defining a tool. workspace-context is included by the default dsh-agent-spine-demo bundle and can be disabled through bundle config; time-context is opt-in, while the standard TUI bundle composes session-reference explicitly.
| Package | Role | ctx key |
|---|---|---|
session-reference/ |
Bounded current-surface snapshots of other sessions | ctx.sessionReferences |
time-context/ |
Durable per-step current time and elapsed-time context | (none) |
workspace-context/ |
AGENTS.md/CLAUDE.md workspace context loader |
(listens on agent/step + tools/post-execute) |
The workspace-context decision record explains its per-agent/session isolation and lifecycle split.