Amend A-293: a later done end deletes the refused key a failed end wrote

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md

@@ -440,5 +440,6 @@ the principle that settles it, cited as "design 47 G A-n".
   on a build that will never be done; a queued or running build stays unpublished. A placed module's newest build is
   the last trunk build-ended event (one naming no branch) the engine heard for that module, from the builder's
   build-ended events read whole at start and then followed, as the assigner hears them (A-181, §556): a failed end
-  writes the refused key `<node>.<module>.<fp>` with the event's words, a later done end of the module supersedes
-  it, and an end naming a branch moves nothing.
+  writes the refused key `<node>.<module>.<fp>` with the event's words, a later done end of the module (at any
+  fingerprint) deletes the refused key such an end wrote, so the state never says refused for a done build, and an
+  end naming a branch moves nothing.