Markitect boundary and reuse tests

workplans/KONT-WP-0010-observability-export-enterprise-readiness.md

@@ -38,6 +38,14 @@ ports, services, audit model, and export package model described in
 `docs/architecture-blueprint.md`. Export and observability must preserve policy
 checks and must not require direct storage access.
 
+## markitect-tool Boundary Remark
+
+Observability and export should surface Markitect adapter provenance, snapshot
+identity, selector references, context-package manifests, and operation
+provenance where markdown-backed assets depend on them. Export formats remain
+engine-owned and should include Markitect payloads as documented adapter
+sections, not as the whole portability model.
+
 ## E10.1 - Expose operational metrics events and job inspection
 
 ```task
@@ -138,6 +146,8 @@ Acceptance:
   status, policy exceptions, derived artifact creation, and review decisions.
 - Storage, index, queue, workflow, AI, and model backend abstractions remain
   externally semantic-preserving.
+- Markitect adapter contract tests are part of the extension compatibility
+  posture for markdown-related engine capabilities.
 
 ## E10.6 - Capture retrieval AI cost and quality signals