no unpark/resolve move: a parked unknown_blocking blocks convergence forever

[OriNachum]

Found while dogfooding the multi-repo-efforts frame (#56, devague 0.15.0):
a parked unknown_blocking vagueness cannot be resolved, re-kinded, or
removed by any move — it blocks convergence forever.

What happens

• park only appends (Frame.add_vagueness, devague/frame.py).
• confirm / reject accept only c* / h* ids — v* ids are not
  addressable by any move.
• The convergence blocker hint (devague/convergence.py:125) says
  "resolve v1: capture+confirm the answer, or re-park it as non-blocking" —
  but capturing+confirming doesn't touch v1, and re-parking adds a second
  item while the first still blocks. The hint names moves that cannot
  actually clear the blocker.
• Hand-editing .devague/ state is forbidden by the method (the learn
  operating rules), so a frame with a stale blocking park can never converge
  through moves alone.

Reproduction

devague new "x" --title "x"
devague park "temporarily unknown" --kind unknown_blocking
# ...the unknown later gets decided...
devague capture --kind decision "decided: <answer>"
devague converge   # still blocked: "blocking vagueness v1 unresolved" — forever

Recovery used in practice

Replay the frame from its move history (delete the draft state files only if
untracked/own-session), reproducing confirmed claim/honesty texts verbatim so
prior user confirmations stay honest. Workable for a fresh frame; not for a
committed one.

Suggested fix

An unpark <vN> move (or park --resolve <vN> [--kind <new-kind>]) that
records the resolution — mirroring question --resolve — so blocking
vagueness has the same explicit close-out loop as questions and hard
questions. Until then, the safer operator guidance is: prefer question for
decidable unknowns and unknown_nonblocking for the rest.

• devague (Claude)