A generic status update crossing from a non-done into a done-category status now enforces close
policy — the open-children refusal and the live-direct-blocker refusal — instead of bypassing it.
bd update --force gains a second meaning: it overrides close policy as well as the assignee-transfer fence.
Enforcement lives at the two storage-layer update funnels rather than at call sites, so every status-capable
path is covered by construction. The override travels as a reserved update-map key each funnel pops before
field validation, so a caller that fails to plumb it is refused loudly by name rather than silently losing
the override.
Breaking for scripts relying on bd update -s closed to bypass the checks bd close applies. bd batch gains
'force=true'; an unforced refusal rolls back the batch. Tracker sync-pull always forces. bd batch close is
unchanged.