adventure: let a player back out from the web, not only in Matrix

Three verbs to match gogobee's: call off an expedition, turn back out of
somebody else's party, send the pet sitter home. Which one this page
offers is derived here rather than pushed — leadership is already legible
in the party seats and the sitter's standing is already in the babysit
offer, so nothing new crosses the wire.

Two things running it turned up that no test would have. An applied
abandon left "Pull out of the run" sitting under a verdict saying the
expedition was over, so an applied verb now also hides the other verbs it
just made untrue. And a party member was being offered that same button
in the first place, beside the one that actually works — Pete knows from
the seat it just read that gogobee would refuse it, so it is withheld.

Also: heal the Matrix handle onto push rows stored before the column
existed, on its own endpoint rather than through the subscribe upsert,
which resets both watermarks and would have silenced the digest for
anybody who reads the site regularly. And stack the board row below sm —
four flex columns that wrapped to six lines on a phone, pre-existing.

internal/storage/schema.go

@@ -403,12 +403,18 @@ CREATE INDEX IF NOT EXISTS idx_equip_orders_owner ON equip_orders(owner_sub, cre
 --
 -- The status ladder:
 --
---   pending -> applied                  (it happened; detail says what)
---           -> rejected_not_running     (extract: no expedition to leave)
---           -> rejected_not_leader      (extract: a party member can't call it)
---           -> rejected_no_siege        (siege_join: nothing camped outside town)
---           -> rejected_already_fought  (siege_join: today's bout is already spent)
---           -> rejected_unavailable     (no character, or dead)
+--   pending -> applied                     (it happened; detail says what)
+--           -> rejected_not_running        (extract/abandon/leave: no expedition)
+--           -> rejected_not_leader         (extract/abandon: a member can't call it)
+--           -> rejected_is_leader          (leave: the leader's row IS the expedition)
+--           -> rejected_no_siege           (siege_join: nothing camped outside town)
+--           -> rejected_already_fought     (siege_join: today's bout is already spent)
+--           -> rejected_busy               (already out, seated, or has a sitter)
+--           -> rejected_insufficient_funds (could not cover the cost)
+--           -> rejected_zone_locked        (expedition_start: not open at this level)
+--           -> rejected_nothing_to_resume  (nothing extracted, or the window closed)
+--           -> rejected_nothing_to_cancel  (babysit_cancel: no sitter is engaged)
+--           -> rejected_unavailable        (no character, dead, or an unsold argument)
 --
 -- Like the equip queue, the underlying game action is NOT idempotent — an extract
 -- ends an expedition and a bout spends a day — so gogobee short-circuits on the