feat(ref-inspect): ancestry check via action=contains; blessed read verbs in the worktrees help #150

Merged

hexajon merged 1 commit from refs/pull/150/head into main

2026-07-16 05:08:57 +00:00

hexajon commented

2026-07-16 05:08:53 +00:00

(Migrated from codeberg.org)

Summary

Closes the gaps that kept pulling agents to raw git around the worktree lifecycle. madt_ref_inspect gains action=contains - a purely local ancestry check (ref= the commit to test, in= the branch that should contain it; both pre-validated so an unknown ref errors cleanly instead of reading as not-contained) answering the post-rebase and pre-finish "did my branch actually land on the base" question that previously had no madt equivalent and forced raw git merge-base --is-ancestor. The name follows git's own --contains vocabulary and the tool's existing predicate-style actions. madt_help topic=worktrees now enumerates the blessed READ verb for every lifecycle step (madt_status, madt_log, madt_ref_inspect diff/show/tree/grep/contains) with the post-rebase contains verification in the flow example, so the first reach is the right one. Remaining candidate read primitives (full-hunk diff over MCP, ahead/behind count vs an arbitrary base, merge-base sha, inverse containment, mid-operation state) are recorded on the issue trail as candidates rather than built speculatively.

Closes #126

## Summary Closes the gaps that kept pulling agents to raw git around the worktree lifecycle. madt_ref_inspect gains action=contains - a purely local ancestry check (ref= the commit to test, in= the branch that should contain it; both pre-validated so an unknown ref errors cleanly instead of reading as not-contained) answering the post-rebase and pre-finish "did my branch actually land on the base" question that previously had no madt equivalent and forced raw git merge-base --is-ancestor. The name follows git's own --contains vocabulary and the tool's existing predicate-style actions. madt_help topic=worktrees now enumerates the blessed READ verb for every lifecycle step (madt_status, madt_log, madt_ref_inspect diff/show/tree/grep/contains) with the post-rebase contains verification in the flow example, so the first reach is the right one. Remaining candidate read primitives (full-hunk diff over MCP, ahead/behind count vs an arbitrary base, merge-base sha, inverse containment, mid-operation state) are recorded on the issue trail as candidates rather than built speculatively. Closes #126