Matt

> These both have the insider knowledge built-in, and you can't even see it. If there are two commands, you have to figure out which to use, and the basis...

It's very clear to me now from talking to coworkers that while `diffmove` is popular name amongst jj developers for being technically correct, it's an absolutely terrible name for your...

> Maybe you can tackle `diffedit` and `interdiff`. Definitely outside the scope of this PR. That'd need to be a whole seperate discussion.

> Just to be sure, when you talked to your coworkers, did you explain that the command moves changes from one commit to another? I want to make sure that...

Could you clarify what `--readonly` does in more detail. The documentation says " ignore changes across multiple run invocations", and that seems like it *could* mean what I understand `--readonly`...

> if it's a good change to make, then it's a "fix" and belongs in jj fix This isn't necessarily true. IIUC, `jj fix` is optimized to run a single...

> We already have some "on push" behavior, namely signing. I had an old diff I never upstreamed that added a new flag called `on-push-behavior = ["..."]` to slightly generalize...

@PhilipMetzger I wrote a [design doc](https://docs.google.com/document/d/103KQCDSHoEFZxQ7W_YQt3945eOYVGp_F0k61Sz2NBj8/edit?tab=t.0) for hooks today

I've been writing design docs in google docs, since I just find that it's much better as a collaboration tool, with the intent of moving them to markdown once it...

Could you elaborate on what you mean by "don't want to have it in the CLI"? My line of thought, as I said above, was that: * The hooks would...