This doesn't sound terribly realistic in terms of expected features. A user cannot (normally) disable a specific menu of a program just because he doesn't like it, and fossil running in local (not network) mode assumes the user knows what he's doing - it offers lots of chances for users to shoot themselves in the foot if they're not careful (e.g. irrevocably losing stashed changes via 'close'ing the repo). Such a feature also implies the addition of a --force (or similar) command to force execution of a disabled command. That, in turn, would give the user back his gun so that he could shoot himself in the foot again. It would also have side-effects on any commands which themselves use such a flag for other purposes.