the "ok" comment is already used by other warnings (low memory access, fake instruction, and something else) and I'm thinking about making it general mechanism for *all* warnings in v2.x
I will think about the choice of the word, but:
a) I don't expect that many accidental "ok" in comments of assembly source (you can search all your sources and tell me if you did find some?)
b) if you know about sjasmplus using it to suppress warnings, it's even less likely you will write it by accident

The longer words will eat more comments space, and warning-specific words will be difficult to remember (what to use to suppress the warning), so I did like "ok" for this, but I'm taking a note and will think about it more.

about searching your sources:
The regex for search can be like "(;|//)\s*ok", that may find few false positives like some string or full-line comment, but you could easily tell which is serious. I did run it over sjasmplus directory, and there are two lines "DB #FF ; OK" in BS-ROM bios source code, other "ok" comments were in tests, testing the warning suppression mechanism. Looks to me quite ok, I'm not worried about causing too much damage by this, but if few more people can search through their code base and report how many end-line comments with "ok" they have in old sources, it may change my mind.