[albert20260301]

Summary

• advance the Lakehouse spec submodule to v0.13.0 and add the new compute sizes, query dialect/format fields, and create_append upload mode
• support cursor-aware upserts with optional content types and document cursor arbitration
• surface backend NDJSON stream failures as typed QueryError exceptions, with line context

Validation

• python3 -m py_compile src/altertable_lakehouse/client.py src/altertable_lakehouse/errors.py src/altertable_lakehouse/models.py tests/test_client.py
• git diff --check
• Full pytest/ruff execution is deferred to CI because this workspace lacks the Python package dependencies (httpx, pydantic, pytest, and ruff).

[albert20260301]

@leo-altertable could you review this?

The touched Python client paths were originally implemented by Albert, so no stronger core-maintainer ownership signal is available. I selected you based on Python ownership. CI is green; please focus on the v0.13 query-stream error handling and the cursor-aware upsert contract.

[albert20260301]

@leo-altertable following up on the review request from September 2: CI remains green and there is no new author feedback. The change is ready for your review when you have capacity.

[albert20260301]

@leo-altertable the prior review follow-up is now three days old. CI remains green and there is no author feedback or merge conflict. The change is ready for review; the main risk remains typed query-stream errors and cursor-aware composite-key upserts.

[albert20260301]

@leo-altertable following up on this v0.13.0 client update: all checks still pass and no review decision is recorded. Could you review the query-stream error handling and cursor-aware upsert contract?

[albert20260301]

@leo-altertable following up: CI remains green, with no requested changes or merge conflict. Could you review the typed-query-stream-errors-and-cursor-aware-upserts when you have capacity?

[albert20260301]

@leo-altertable following up: CI remains green, with no requested changes or merge conflict. Could you review the typed query-stream error handling and cursor-aware composite-key upsert contract when you have capacity?

[albert20260301]

@leo-altertable following up: all checks remain green, with no requested changes or merge conflict. Could you review the typed query-stream error handling and cursor-aware composite-key upsert contract when you have capacity?

[albert20260301]

@leo-altertable could you review the v0.13 Lakehouse Python implementation?

All checks remain green. I selected you based on Python ownership; the main focus is the new query/upload/upsert behavior and its compatibility with the pinned spec.

[albert20260301]

@leo-altertable this has remained review-gated for three days since the last check. CI is still green and no changes have been requested. Could you review the v0.13 query-stream error and composite-upsert behavior?

[albert20260301]

@leo-altertable this has remained review-gated for four days since the last follow-up. All checks are still green and no changes have been requested. Could you review the v0.13 query-stream error and composite-upsert behavior?

[albert20260301]

@leo-altertable the merge-conflict repair is complete: I rebased onto current main, consolidated the concurrent QueryError implementation, and preserved raw NDJSON error context. The fresh lint/typecheck and Python 3.9–3.14 matrix are all green.

Could you review the v0.13 query-stream error and composite-upsert behavior when you have capacity?

[albert20260301]

@leo-altertable the repaired v0.13 Lakehouse Python update has remained review-gated for four days. The fresh lint/typecheck and Python 3.9–3.14 matrix are green, with no requested changes. Could you review the query-stream error handling and cursor-aware composite upsert contract?

[albert20260301]

@leo-altertable this remains review-gated three days after the prior follow-up. The complete lint/typecheck and Python 3.9–3.14 matrix are green, with no requested changes. Could you review the v0.13 API alignment, especially the consolidated QueryError handling for streamed backend error records?

[albert20260301]

@leo-altertable this is still review-gated after the prior follow-up. The complete lint/typecheck and Python 3.9–3.14 matrix remain green, with no requested changes. Could you review the v0.13 API alignment, especially the consolidated QueryError handling for streamed backend error records?