Beagle SCM

BE-014 HIGH: DELETE ignores the Host slot — be delete //origin?feat tombstones the LOCAL branch

verbs/delete/delete.js:318 never inspects the Host slot of a delete arg, so be delete //origin?feat (meant to delete the REMOTE branch) resolves ?feat locally and writes a LOCAL tombstone — the opposite of the intent, and silent. Other verbs route a Host slot to the wire (post/put push forms); delete has no such arm. From the 2026-07-07 be/ review (BE/REVIEW), CONFIRMED. Method Issues.

Input

Context

• A Host-slot delete either pushes a remote ref-delete (receive-pack zero-sha update) or refuses loudly (DIS-011-style log-only if no push subsystem) — it must NEVER silently retarget to the local branch.
• Kin: SUBS-039 notes the DELETE arm lacks the sub-crossing split; this is the sibling Host-slot gap.

Goals

• A Host-slot delete pushes the remote ref-delete, or refuses with a code (e.g. DELPUSH) if wire-delete is out of scope; never a local tombstone.
• Slot precedence matches post/put (Host > Query > Path).

Constraints

• Repro-first (be delete //origin?feat → remote delete or loud refusal, local branch untouched); URI slots via the URI class.

WIP

Design decisions

• (pending — wire ref-delete vs loud refusal ruling)

TODOs

• Repro: Host-slot delete does not touch the local branch.
• Route Host slot to wire/refusal; suite green.

Blockers and bummers

• None known.

Outcome

• (pending)