Skip to content

fix: order lake build after session cleanup in save refusals - #415

Draft
ejgallego wants to merge 4 commits into
mainfrom
codex/issue256-trace-fresh-deps-20261103
Draft

ejgallego wants to merge 4 commits into
mainfrom
codex/issue256-trace-fresh-deps-20261103

Conversation

@ejgallego

Copy link
Copy Markdown
Collaborator

This PR makes every save refusal that suggests lake build also say to stop the session first. Agents following a stale-dependency recovery plan reach save, and for batch-only moreLeanArgs, deferred compilation, a compiler-revision mismatch, or a stale save trace, Beam told them to "run lake build" without mentioning the live session. Building while the session was live left Beam's history marking the dependency as needing a save, so every later sync of an importer failed with a plan that could not be followed, as reported in #256.

Save refusals that suggest `lake build` (batch-only moreLeanArgs, deferred
compilation, compiler-revision mismatch, stale save traces) did not say to stop
the session first. Following them while the session was live left the broker's
history marking the dependency as needing a save, so later importer syncs failed
with a recovery plan that could not be followed (#256). Share one external-build
procedure across these messages and the sync-barrier message, and document it.
@ejgallego ejgallego added this to the 0.2.1 milestone Nov 3, 2026
The 10,000-byte limit was a round number rather than a measured bound,
and the skill body is now within 100 bytes of it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant