Question: Is it valid for a remove action to reference a file path that has never been added to the table (i.e., no corresponding add action exists in any previous version)?

Context: The protocol clearly states that remove actions create tombstones and that invalid actions (like removes that cancel out adds) are handled during action reconciliation. However, it doesn't explicitly state whether a remove for a non-existent path is:

 - Invalid and should be rejected by readers/writers
 - Valid but ignored during action reconciliation (treated as a no-op)

What I've found in the protocol:
- The description implies removes follow adds ("removing a file that has been added")
- Tombstones are described as marking "files that were recently deleted"
- The dataChange=false case mentions removed records must be "contained in one or more add file actions"

But there's no explicit prohibition or guidance for the case where no prior add exists.

Use case: I'm implementing a Delta reader and want to ensure proper handling of edge cases and potentially malformed transaction logs.

Would appreciate any clarification on the expected behavior for both writers and readers in this scenario.

Thanks!