v0.2.0

The assistant can work on relationships. Asked to connect two characters that
already exist, it used to invent a third one to hang the connection on —
because a relationship's starting point could only ever be an entity from the
same draft. Relationships are now a first-class thing the agent proposes,
changes and removes, and external MCP clients can do the same.

Added

• manage_relationships skill. Ask the assistant to link, re-type,
  reverse or unlink entities that already exist and it proposes exactly that —
  no invented entities, and far cheaper than routing the request through lore
  generation.
• Relationship operations in review. A proposal can now create, change or
  remove connections, each shown with what it does and, for a change, what the
  connection says today. A proposal may consist of nothing but these.
• Contradiction warnings at review. Proposing enemy_of for a pair the
  world already records as ally_of is flagged, as is proposing a connection
  that already exists. Both are warnings, not refusals — a falling-out is a
  legitimate story beat and only you can tell it from a mistake.
• MCP relationship tools: list_edges, update_edge, delete_edge and
  update_entity; get_entity_graph now returns each relationship's id.

Changed

• Both ends of a relationship are now equal. Either side may be an entity
  from the draft or one that already exists. Previously only the target side
  could be an existing entity.
• Existing relationships reach the assistant with their ids, and no longer
  only when a graph entity is in focus — a search-driven run used to see none
  of them at all, which is exactly when it guessed at connections that were
  already recorded.
• MCP delete policy. Entities and projects still cannot be deleted through
  MCP. Removing a relationship now can be: it destroys no text, only a link
  that can be recreated, and withholding it while allowing re-typing was a
  pretense. Write tools still require your client to confirm with you first —
  do not enable auto-approve.

Fixed

• "Request changes" on a proposed entity edit ran the lore generator over it
  instead of the editor.
• The graph view kept showing old connections after a commit that only changed
  relationships.

Migration

None. Sessions interrupted mid-review under 0.1.0 resume normally — the draft
format was extended, not broken.