DIS-061 DONT: be/ JS post advances the tracked branch on EVERY commit superseded by DIS-071 (the track-URI model); live defects refiled as DIS-076 (the split + ref mis-keying), DIS-072 (pins), DIS-074 (bare post)

Now
DONT

trees (AUTHORITATIVE) separates the two motions, made UNIFORM by ruling 2026-07-13: a commit moves only the worktree (it goes "ahead"), fast-forwarding the tracked branch is a SEPARATE explicit post ?branch no commit-time FF for any branch shape (supersedes the 2026-07-12 tip==base sub-ruling AND overrules the post's own example-6 line "A regular branch would advance on commit", trees.mkd:211). The be/ JS does the opposite, by prior ruling: postOne FF-advances cur's attached branch atomically with every commit (post.js:719-721, gated only on !att.detached), so a sub commit moves its pin-branch with no parent commit anywhere (submount.js:319-320, SUBS-040 I2; wiki Worktree:12 "post advances the tip"). The post overturns that ruling; this ticket carries the flip plus the adjacent bare-post/own-branch/normalization defects.

Input

Context

Goals

Constraints

WIP

Design decisions

TODOs

Blockers and bummers

Outcome