eagent v0.5.1

A working directory that persists

Each actor now has a working directory. It starts at the project root, and a cd inside a command moves it for that actor's later commands: the shell reports where it ended up, the log records the move as a cwd.change event, the tool result says so, the steer names the directory while it differs from the project root, and the phone's thread chips (cwd, branch, and a new project key) and the web UI follow it. A worker starts where the orchestrator was when it delegated and keeps its own. File tools resolve relative paths against it and may write there.

A narrator that answers with the orchestrator, not ahead of it

The narrator's reply to a message you send is held until the orchestrator has reacted, or fifteen seconds have passed. For a message that asks a question, only the orchestrator's answer (a note with answer: true) or the end of its turn counts, and only from a turn that actually had your message in view. The steer then says which case applies: relay the answer faithfully, say what started, or one line that the message landed. Questions about the work or about eagent itself are answered by the orchestrator in a marked note that the narrator relays; every actor's prompt now carries the same short description of how eagent works (FACTS.md), so those answers are grounded rather than guessed. A narrator message that names the machinery (orchestrator, dossier, subsession, and so on) is sent back once to be rewritten as "I".

v0.5.0 was tagged with two stale test expectations and did not publish; this release is the same change with those fixed.

Full changelog: v0.4.0...v0.5.1