🐛 Bug Report: `create_row` with `transaction_id` fails — Pydantic Row model requires $createdAt / $updatedAt but transactional responses omit them

[arkountos]

👟 Reproduction steps

• Create a transaction via TablesDB.create_transaction()
• Call TablesDB.create_row(...) with a transaction_id
• The SDK's Pydantic Row model fails to deserialize the response

👍 Expected behavior

create_row() to work inside a transaction?

👎 Actual Behavior

Throws this error when calling create_row()

2 validation errors for Row
$createdAt
  Field required [type=missing, input_value={'$id': '69c435146902e250...ns': [], '$sequence': 0}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.12/v/missing
$updatedAt
  Field required [type=missing, input_value={'$id': '69c435146902e250...ns': [], '$sequence': 0}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.12/v/missing

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

Appwrite version: 16.0.0
Python 3.12
Ubuntu-24.04, self-hosted, function ran locally with appwrite run functions

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct