Signing key expiration exists for the same reason certificate expiration exists: we create keys that are infeasible to discover with current methods, and create replacements as techniques advance. This encourages us to create stronger keys over time.
Had you failed to notice a key expiration from the 80s, you would assume the signature is valid - but most computing devices these days could have just generated the signature without the original key.
>Had you failed to notice a key expiration from the 80s, you would assume the signature is valid ...
If the algorithm is broken then the implementation should not support verification using that algorithm no matter the expiration date. An attacker can update the key's expiration date to whatever they want if the algorithm is broken.
Certificates have an expiration date because keys can be compromised, and cryptographic algorithms can become weak and be broken. The expiration date imposes a time limit for possible fraudulent use of the key.
When using certificates, it’s also the certificate that expires, not the key. A new certificate for the same key can be issued (certificate renewal).
Implementations should probably just ignore the expiry of a key used for signing when checking a signature...