0.59.0

Added

• A tree store (aep.project/3) renders its projection as format: aep.planning-md/2, which the planning-document parser reads; an aep.project/2 store keeps rendering /1. validate holds each document to the render of its own tag (S5), so an existing tree projection stays valid until aep plan artifact render or the next write re-renders every document in the new tag. Each repository on a tree store gets that re-render as its own commit.
• aep plan store export --fixup <file> takes a JSON object of literal replacements and applies each to every string it carries over, after the derived identities and before the home paths. The map it writes records them, and the projection comparison reads them as explained.

Changed

• On a tree store (aep.project/3), aep plan artifact evidence records an Entity Runtime observation at the artifact's current revision instead of an edit of it, and so does any other write that leaves the artifact's revision unchanged, such as a relation starting at it. Evidence on one branch and a move on another now merge into one artifact instead of a fork that validate reports as S3. move, explain, history and show count evidence from the observations and from the edits a tree store recorded before, so existing stores read as they did. The projection's bytes do not change: the rendered revision is AEP's, which evidence never advanced.
• Entity Runtime is pinned at 0.22.0 (9ee145e8), whose tree stores make only decisions heads. Eventlog stays at 0.4.0.

Fixed

• aep plan store export rewrites inside the legacy bytes an aep.project/2 store keeps hex-encoded as migration provenance — the exact journal lines and the raw capture of the markdown store — and binds each rewritten line to a new envelope digest through its coordinate and the reservation roster. Before, home paths and fixup literals survived there verbatim.
• The export comparison replaces inside each string rather than in serialized JSON, so a path that JSON escapes is no longer reported as a difference, and a difference now names its JSON pointer and the text around it.
• Two aep plan artifact validate runs on one tree store at once no longer fail each other. Each staged its render of the projection in a directory named by the authority snapshot alone, so one removed the stage the other was reading and reported every artifact as unrendered, or refused with NotPublished. A stage directory now also carries the process and a counter.
• aep plan artifact validate --against <revision> on a tree store skips V2 when the revision holds no tree store, such as the aep.project/2 commit a cutover pull request is measured against, and prints V2 skipped: <revision> holds no tree store (<path>). Before, every file of the /2 store was reported as a deleted committed file. A revision Git cannot read is still refused.