Markitect boundary and reuse tests

This commit is contained in:
2026-05-05 19:41:32 +02:00
parent 9f1b8da87a
commit ef8391e6a7
15 changed files with 490 additions and 6 deletions

View File

@@ -37,6 +37,14 @@ Implement ingestion through connector and extractor ports described in
access, `markitect-tool`, PDF/document libraries, and dataset readers must live
behind adapters, not in the domain core.
## markitect-tool Boundary Remark
Markdown ingestion must use `markitect-tool` for Markdown parsing,
frontmatter, headings, sections, selectors, includes, contract checks where
needed, and snapshot identity. The engine should normalize Markitect results
into its common representation and preserve source/adapter provenance rather
than rebuilding Markdown syntax behavior.
## I6.1 - Implement ingestion job model status and retry surface
```task
@@ -110,6 +118,8 @@ Acceptance:
- Plain text produces normalized text representation and source provenance.
- Markdown extraction delegates to `markitect-tool` when available.
- Missing adapter dependencies fail with structured adapter errors.
- Parser, selector extraction, and snapshot identity behavior are covered by
the Markitect integration contract tests.
## I6.5 - Implement PDF office document and dataset baseline adapters