Finalizer task input can be destroyed with Configuration Cache enabled

[bamboo]

Current Behavior

A finalizer task with inputs produced by other tasks can have its inputs destroyed by another task before execution.

Expected Behavior

Gradle should prevent other tasks from destroying the finalizer task inputs before the finalizer task has been executed.

Context (optional)

No response

Steps to Reproduce

In the example below, Gradle should not allow the clean task to run between :b and :c (the producer task and the finalizer / consumer task) but that's not what happen when the Configuration Cache feature is enabled:

plugins {
    id 'java'
}

abstract class TaskReader extends DefaultTask {
    @InputFile abstract RegularFileProperty getFile()
    @TaskAction def action() {}
}

abstract class TaskWriter extends DefaultTask {
    @OutputFile abstract RegularFileProperty getFile()
    @TaskAction def action() {
        file.get().asFile.text = "foo"
    }
}

tasks.register("a", DefaultTask) {
    finalizedBy("b")
}

def taskWriter = tasks.register("c", TaskWriter) {
    file = project.layout.buildDirectory.file("output.txt")
}

tasks.register("b", TaskReader) {
    file = taskWriter.get().file
}

Gradle version

8.10

Build scan URL (optional)

No response

Your Environment (optional)

No response