It might have served me well to have read this, before I did a test (commenting out the notifymsg and exporting again), which indeed confirmed the source of the problem. :)
Thing is: I am fairly certain I originally DID have the notifier address commentary_001_act and could never get that to work.
When it finally worked, with the name of the python file (...or of the class), in place of the pythonfilemod name, that was after lots of blind trying similarly wierd things.
So... My referencing a non-existent pythonfilemod, leads to the automatic creation of a new, blank one... Intresting, in its own right, I guess. :)
I'll try again, with correct references, because I can't truly remember any longer, whether I really, really did try it with the extra preceding callback message, which assures the notify message event waits for a later callback ID than the responder's first one.
Actually; Perhaps this is what neccessitates that practice in the first place...
Maybe, somehow, the notification goes right to the blank pythonfilemod (and, of course, fails) if it's first and goes fishing for a real one, within the same logicmod, otherwise...
But now I am apparently off for a bit of evening work - damn phone. :P
I'll report any results and hope for continued advice. :)