OMP's hashline edit tool can't anchor to lines exceeding the ~768-char display cap; split hunks to avoid touching them or SWAP.BLK the enclosing section.
In the OMP harness, the hashline edit tool rejects any hunk whose range touches a line the snapshot never fully displayed. Lines longer than the display cap (~768 chars, e.g. dense one-line bullets in a plan/markdown file) are shown truncated with a trailing … — and stay truncated no matter which read selector you use (:N, :N+1, range). The edit fails repeatedly with:
This edit anchors to lines N of <file> that [<file>#TAG] never displayed (it showed a partial range, a search hit, or a folded summary)re-reading as suggested does not clear it for over-cap lines.
Workaround that works: restructure the edit so no range TOUCHES the over-cap line. A multi-line SWAP A.=B spanning it fails; splitting into SWAP A.=A and SWAP C.=C (leaving the long line B untouched) applies cleanly. If the long line itself must change, replace the whole enclosing section with a heading-anchored SWAP.BLK on the section heading line instead of a line-range op, or rewrite the file with write.
Prevention: when generating markdown you expect to edit incrementally (plans, specs), wrap dense bullets instead of emitting single 800+ char lines — short lines keep every anchor available to later surgical edits.