I’m still not 100% sure about the official status of bypass_bump in the API docs — it doesn’t appear anywhere obvious.
But when I look at the logs from Ethsim12’s Python sync script, they’re instructive. The script tries to call the API with bypass_bump=true. If that parameter were ignored or invalid, the only thing that would prevent unnecessary bumps is the fallback they added: a manual call to
/t/{topic_id}/reset-bump-date
So the log output itself becomes strong evidence. If the log shows topics being updated without appearing in /latest (and without needing the reset fallback), that’s pretty good proof bypass_bump is alive and working. If the log always falls back to reset-bump-date, then maybe it isn’t.
In other words: the logs from this script go a long way toward confirming whether bypass_bump exists and is actually respected by Discourse.