I am going to wait for others to share their thoughts. They probably need some time to catch up with us. This is my last reply for now.
also you say HTLC have nothing to do with revocation because revocation uses time lock..... you might want to check on what TL stands for in HTLC (spoiler: Time Lock)
the snippet of IF ELSE statements you referenced in bolt3 are the conditions of .. drum roll.. the HTLC contract
You might want to check what H stands for in HTLC. I can't see any hash in that locking script. HTLCs in commitment transactions are those two scripts that you ignore to comment for some reason.
alice and bob never put erics payment hash into a commitment
because eric has the secret
Again, you completely ignore two locking scripts which are used for HTLC outputs in commitment transactions. Eric can't spend those outputs with just a secret because he also needs valid HTLC signatures, but you don't want to acknowledge that even though you keep talking about HTLC-success and HTLC-timeout transactions.
(LN payment = invoice, aka onion_route_packet aka msat micropayment channel, aka millisat denominated HTLC)
If you don't see any difference between an invoice, onion_route_packet and HTLC then we really don't have anything to talk about.
I see that further discussion is pointless as you keep saying that I should read the specifications more carefully without quoting it to prove your statements.
Good night, franky1.