checkpoint: route committed writes through refs.Primary

Five write sites in committed.go and the getSessionsBranchRef helper in parse_tree.go now use s.refs.Primary instead of the v1 branch literal. At today's resolver Primary is the v1 branch, so behavior is unchanged. A new test asserts the property directly: writes against a synthetic Primary advance that ref, not v1.