What is the limit on Queueable jobs enqueued from a Transaction Finalizer's finalize method in Salesforce?

When a Queueable class implements the Finalizer interface, the finalize method runs after the Queueable job completes and can enqueue additional Queueable jobs. It is not documented whether these enqueues are subject to the same per‑transaction limit that applies to Queueable jobs added directly from synchronous code or from the Queueable execute method.

Understanding this behavior is important for designing reliable chaining patterns that avoid unexpectedly hitting the Queueable job limit, especially when processing large data sets across multiple asynchronous steps.

Does the finalize method execute in the same transaction as the original Queueable job? If it runs in a separate transaction, does it inherit its own Queueable job limit? What is the practical impact on chaining Queueable jobs via finalizers when aiming to stay within governor limits?