you do know the rules got softened right!!.
its how junk data (extra bytes) get to be in the blockchain without causing nodes to reject the junk..
nodes dont validate every byte meets a purpose/format/function of a transaction. they instead see an opcode that just says "yea its valid, just accept it, dont check it"
emphasis bitcoin full nodes used to VALIDATE .. EVERY.. BYTE.
every byte used to have a purpose becasue previous generation of devs actually cared about lean transactions
Then what is the difference between an archival full node and a pruned full node? Remember, you seemed to have taken issue with labelling pruned nodes as full nodes, while retaining that term exclusively for full nodes which stores the entire blockchain. So what gives? Don't both of them act in a similar manner?
the difference is YOU are foolishly adding in the word FULL to nodes that are not full
there are full nodes..... (do all network services)
then there are archival vs pruned nodes (DONT do all network services)
and then if they dont do validation then they are software/wallets (just communicate to network or server then to network)
the emphasis is the word FULL means FULL
YOU imply something less then full service is still full