v0.1.0-rc4

Fourth release candidate. Deleting a document is now an event that can be undone, retractions retract, failed jobs come back, and CI runs every database test.

Library

• Deleting a document is an event on the recording axis, not a hole in the database. The document gets a tombstone, its chunks are marked superseded, and nothing is cleared. Only facts whose every source is deleted are retired; a fact another live document vouches for stays. The toast offers Undo, a sync that meets the tombstone while the source still has the file revives it, and re-uploading the same content revives it too. The evidence panel says "source deleted" on a quote whose document is gone. (#273, #268)
• The privacy policy and the cleanup dialog describe what deletion actually does. (#273)

Review and graph

• "Retract" on a contradiction retracts the fact you point at, and a resolved violation whose promise did not hold reopens. (#257)
• A burst of graph events refetches the graph once, not once per event. (#263)
• The administration page has one name, and the empty graph points at it. (#272)

Sources and jobs

• A failed job finds its way back to the queue: a knowledge base can rerun its failed jobs, the alert for a model that is out of credit or unreachable offers "Run those again", and an admin can requeue across bases. (#258)
• The Notion client waits out a rate limit instead of failing the sync. (#269)

Search and chat

• An agent can read a whole document after a search hit. (#265)
• A search keeps its query in the URL. (#264)
• Switching knowledge base lands on the same page, not the same conversation. (#262)
• Two live answers no longer write into one store. (#259)

Also

• CI runs every database test, and a missing database fails instead of skipping. (#260, #266)
• Decision record 0019, "The second clock can be rewound", is planned: an as-of on the recording axis. (#271)
• README Community wording, by @Danmushu. (#250)
• Compose defaults to this tag. (#274)

Image: ghcr.io/deeplethe/utopia:0.1.0-rc4