Does the chunked streaming protocol have future secrecy?

[handpickencounter]

Does age employ ratcheting of the symmetric key for its chunked stream format?

Suppose we have longlived-secret-stream | age -r ... > enc.age and the machine is compromised and snapshotted.
Is enc.age compromised from beginning to end or only the most recent chunk prior to snapshotting? aka future secrecy.

[FiloSottile]

The STREAM key remains the same throughout the stream, with only the non-secret nonce changing, so there is no future secrecy.

age is made for encrypting files, not long-lived streams. Even many TLS implementations don't provide future secrecy within a single connection (despite rekey being supported by the protocol). For this, you might want to use Noise with Rekey or TLS with forced KeyUpdates.

[handpickencounter]

Would it not have been easy to make age rekey on every chunk? Can it still be done without breaking backward compatibility? ECC operation on every chunk may not be advisable, hence why I suggested ratcheting.

age is made for encrypting files

According to the unix philosophy everything is a file, and age can be part of a pipe.

Edit:
I believe it can be done with backward compatibility. Employ trial decryption. If decrypting with the ratchet fails fall back to try and decrypt he old way before failing with AEAD failure error.