>> +When the value is `permanent', the mark will not be deactivated
>> +by any subsequent point motion key that was not shift-translated.
>
> This is a negative description, which tells half of the story, and
> leaves it to the reader to guess the other half (how to deactivate the
> mark in this case).  How about describing both, and in a positive way?
> For example:
>
>   When the value is `permanent', the mark will be deactivated by any
>   action which normally does that, but not by motion keys that were
>   not shift-translated.

Fixed in the new patch.

> And finally, a question: is it enough to have this as a user option?
> That is, what if the user wants this only temporarily, for the next
> sequence of commands that extend the region?  Should we perhaps have a
> better solution for that use case?  More generally, perhaps this
> feature is almost always wanted only for a sequence of commands, never
> globally for extended periods of time?  In that case, a user option is
> not the best solution; it is better to have some minor mode that could
> be turned on and off with a simple key sequence.

It would be very surprising if someone might want something more complicated.
But everyone is welcome to extend this feature when such a need will arise.

>>  See `this-command-keys-shift-translated' for the meaning of
>>  shift-translation."
>> -  :type 'boolean
>> +  :type '(choice (const :tag "Off" nil)
>> +                 (const :tag "Permanent" permanent)
>> +                 (other :tag "On" t))
>> +  :version "28.1"
>>    :group 'editing-basics)
>
> This would also need a NEWS entry, if we eventually decide to do it
> this way.

This patch also adds a NEWS entry: