Clarify Kopf behavior on startup: event type for existing resources from initial LIST

[devfinwiz]

I found this from documentation:

"Please note that the event handlers are invoked for every event received from the watching stream. This also includes the first-time listing when the operator starts or restarts.

It is the developer’s responsibility to make the handlers idempotent (re-executable with no duplicating side-effects)."

And while interacting with Claude, I came across -
"Initial listing: When Kopf starts, it performs an initial listing of all resources matching the label selector. Each resource generates a MODIFIED event (not ADDED!) because Kopf considers them "already existing" rather than "newly created.""

I need clarity from official documentation or community members if the above said statement (Claude) is true or not. I feel it is incorrect. Kindly revert back on this once free. Thanks.

[nolar]

I highly recommend reading the documentation in the original form, not in the paraphrased form. This understanding is a mistake made by AI. The documentation is very clear on types of handlers, specifically on low-level vs. high-level handlers.