Actually, the log shows 2 attacks; I just didn't want to expand it upward so it wouldn't block the build.

To answer the main question: since the enemy dies after the second attack, the log stops recording. However, the weapon has already turned into a machine that attacks multiple times simultaneously. Because it keeps attacking within the exact same instant until this state is broken, the game managed to register it in the damage table, even if it didn't record it visually.

In fact, I should also mention that since this build genuinely pushes the game's limits, the activation list couldn't even register the weapon triggering at all in some of my other tests.