_Kerman 107e05e79b fix(workspace-context): recompose the baseline on resume, skip only on remount ...

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.

2026-07-27 01:35:36 +08:00

..

workspace-context.e2e.ts

refactor(agent): unify sourced message delivery

2026-07-24 22:38:50 +08:00

workspace-context.spec.ts

fix(workspace-context): recompose the baseline on resume, skip only on remount

2026-07-27 01:35:36 +08:00