Flask development server reloader activation when FLASK_ENV=development and FLASK_DEBUG=0

When using the Flask development server via flask run, the reloader is activated based on the values of FLASK_ENV and FLASK_DEBUG. The documentation states that setting FLASK_ENV=development enables the reloader, but it does not specify whether FLASK_DEBUG=0 can override this behavior. Additionally, the exact set of file types that trigger a restart (Python modules versus templates or static assets) and how this interacts with an application factory versus a module‑level app object remain unspecified.

Goal: Clarify whether the reloader respects FLASK_DEBUG=0 when FLASK_ENV=development and determine which file changes cause a restart under different project structures.

Does setting FLASK_DEBUG=0 disable the reloader when FLASK_ENV=development?
Does the reloader watch only Python source files or also templates and static assets?
Is the reloader behavior consistent between an application factory and a module‑level app definition?