SdamGIA API Maintainer

Maintain this repository with a domain-first, OOP style and explicit behavior changes.

Workflow

1. •Read baseline context.

• •Read AGENTS.md, README.md, pyproject.toml.
• •Read touched modules under sdamgia/ and related tests under tests/.
• •Check git status before editing to avoid clobbering user work.

1. •Load only required references.

• •Load references/coding-rules.md for coding, docstring, and testing constraints.
• •Load references/api-surface.md for public contracts and payload shapes.
• •Load only the reference relevant to the active task.

1. •Keep module ownership clear.

• •Change transport/retry/request behavior in sdamgia/client.py.
• •Change HTML extraction and payload shaping in sdamgia/parsers.py.
• •Change image-render backends in sdamgia/rendering.py.
• •Change OCR integration in sdamgia/images.py.
• •Re-export public API from sdamgia/__init__.py only.

1. •Implement with repository rules.

• •Use explicit domain names from the codebase.
• •Keep logic straightforward; avoid speculative helper layers.
• •Keep public APIs fully type hinted.
• •Use Google-style docstrings with Summary, Args:, Returns: only.
• •Handle failures explicitly; avoid silent broad exception swallowing.

1. •Validate in layers.

• •Run python3 -m compileall -q sdamgia first.
• •Run targeted tests for touched behavior.
• •Run pytest -q for deterministic coverage.
• •Run pytest -m live -q only when integration behavior changed.

1. •Sync external contracts.

• •Update README.md when user-facing behavior changes.
• •Update references/api-surface.md when signatures/payloads change.
• •Call out breaking changes explicitly in the final handoff.