Quests, not pull requests
A pull request is a conversation about a diff. Self-driving software needs something longer-lived: a record that starts when production reports an error and ends only after a fix has survived a watch window.
Ephyra calls that record a quest. A quest moves through evidence, a failing reproduction, a plan, a patch, proof, a landing and a watch. Each step is written to git under refs/ephyra/trails/<id>, so the quest travels with the repository to any forge: Radicle, Tangled, plain git, or a Sapling stack.
Humans stay at three checkpoints. A asks whether the hypothesis is the right thing to chase, B approves the plan once the bug reproduces, and C approves landing once proof passes. Everything between the checkpoints is the machine's job, and everything it did is in the journal.
This is a design note. Ephyra is pre-alpha, and nothing here claims a production track record yet.