As Forte is introducing new transaction primitives (system txns, scheduled txns), there will be API changes required to support.
Initially, these appeared more significant. However, these have been mostly abstracted into the access node now, and the only applicable change appears to remain as adding a block_id field to the getTransactionStatus query, so that in rare cases that users must disambiguate system txns, they can do so (as they do not posess some of the same uniqueness guarantees).
Related: onflow/flow#1638