Name: Pptx Tests
Author: jphittell

Read AGENTS.md, conftest.py, and the relevant service module before editing tests.

Preserve

Test public contracts and service boundaries first.
Keep schema validation explicit, including extra-field rejection and required-field enforcement.
Reuse tests/conftest.py for shared factories, fixture paths, and deterministic helpers.
Keep ingestion tests focused on provenance, chunk metadata, redaction, deduplication, and vector-store round trips.
Keep schema tests focused on validators such as uniqueness, word caps, enum constraints, and export status rules.
Prefer local fixtures under tests/fixtures/; avoid network access in tests.
Prefer updating the nearest existing service test file first, including the current API, assets, CLI, pipeline, planning, renderer, and schema suites.
Add new test files by service area only when the implementation genuinely introduces a new boundary that is not already covered.

Avoid

Read AGENTS.md, conftest.py, and the relevant service module before editing tests.

Test public contracts and service boundaries first.
Keep schema validation explicit, including extra-field rejection and required-field enforcement.
Reuse tests/conftest.py for shared factories, fixture paths, and deterministic helpers.
Keep ingestion tests focused on provenance, chunk metadata, redaction, deduplication, and vector-store round trips.
Keep schema tests focused on validators such as uniqueness, word caps, enum constraints, and export status rules.
Prefer local fixtures under tests/fixtures/; avoid network access in tests.
Prefer updating the nearest existing service test file first, including the current API, assets, CLI, pipeline, planning, renderer, and schema suites.
Add new test files by service area only when the implementation genuinely introduces a new boundary that is not already covered.