remake: aborts written as the user who asks; no abort by time

Review 2, N3: 1150 let any member write an abort decision once a remake
had expired a grace period ago, judged by the change's own time, the
writer's word. A member could race the coordinator's legitimate commit
with an abort dated as it liked; both taken, Automerge shows
one, and nodes that acted on the commit split from those that didn't.

The two writers of such aborts are operator requests whose endpoints
already need write on _continuum/remakes: aborting an expired remake
(DELETE /admin/remakes/{id}) and superseding one (POST
/admin/remakes?force=supersede). Both now commit as the user who asks
(the proposal and its vote with them, for a supersede), which the rules
take as one who may write the decision. The clause judging an abort by
its time goes, and with it the time the rules carried. An expired
remake is still aborted through any member, by an operator.

1 files changed, 3 insertions, 2 deletions

diff --git a/docs/remakes.md b/docs/remakes.md
index fc938c7..ab808e5 100644
--- a/docs/remakes.md
+++ b/docs/remakes.md
@@ -255,8 +255,9 @@ aborts it itself, under three conditions that keep it from crossing a late commi
   Clocks): whether the remake expired is judged by it, and a node ahead would abort a
   remake its coordinator may still commit. Otherwise `409`, unless `?force=clock`.
 
-With a policy ([`access.md`](access.md)), the other nodes take that abort by the time
-it says it was written: a grace period after the expiry at least.
+The abort is written as the user who asks, who may write remakes: with a policy
+([`access.md`](access.md)), the other nodes take a decision from the coordinator or
+from such a user only.
 
 A member that saw a remake expire before it voted for it says so in its log, once
 (`Didn't vote for a remake`, warn if its clock is off: it then misses remakes others