I4008 — A push that only deletes refs runs no plan in the pre-push hook

○READY wave 0 · p1 · implementation profile · parallel safe

Part of a-session-proceeds-through-the-mesh — A session proceeds through the mesh: it finds the work, claims it once, runs it watched and stops when the intent is met.

Objective

A push whose every ref is a deletion runs no plan in the pre-push hook, by the reasoning of the refs/majordomus/* exemption: no source travels.

Why

Deleting a merged branch runs the whole pre-push plan, which takes tens of minutes on a loaded machine and judges nothing.

Current state

Not built: this issue is planned by the milestone a-session-proceeds-through-the-mesh and nothing of it exists.

Desired state

The acceptance criteria below hold and case 4008 proves them.

Scope

• .githooks/pre-push
• apps/majordomus-cli/src/hooks
• docs/HOOKS.md
• test/cases/4008_a_push_that_only_deletes_runs_no_plan.sh
• .ai/repo/project/issues/I4008.yaml

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• A push of only deletions runs no plan and exits 0
• A push of any non-deletion ref runs the plan as before
• The exemption is declared data beside the refs/majordomus/* one

Validation

• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 4008_a_push_that_only_deletes_runs_no_plan

Evidence required

• case_4008_a_push_that_only_deletes_runs_no_plan

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I4008.yaml. Read it back with majordomus plan show I4008.