v1.0.0: dev.uapf.semantic-document-analysis

UAPF v1.1 SSOT-conformant Level 4 process package — reusable semantic
document analysis, shareable across DMS / intake / mailroom systems.

Structure:
- uapf.yaml (kind: uapf.package, level 4) + manifest.json engine-compat
- bpmn/semantic-document-analysis.bpmn.xml — 3 service tasks invoking
  reserved UAPF-IP capabilities ai.redact@1, ai.extract@1, event.emit@1
- resources/mappings.yaml — task->target bindings with I/O contracts
- resources/schemas/vdvc-semantic-summary.schema.json — output contract
- resources/guardrails.yaml — GDPR + EU AI Act constraints
- metadata/ownership.yaml + metadata/lifecycle.yaml
- docs/, fixtures/, tests/eval-set.json

Validates clean against UAPFormat/UAPF-specification schemas.

docs/02-integration.md

@@ -0,0 +1,21 @@
+# Integration with UAPF-conformant runtimes
+
+This package validates against the UAPF v1.1 SSOT schemas:
+- `uapf.yaml` → `uapf-manifest.schema.json`
+- `metadata/ownership.yaml` → `ownership.schema.json`
+- `metadata/lifecycle.yaml` → `lifecycle.schema.json`
+- `resources/mappings.yaml` → `resource-mapping.schema.json`
+
+It conforms to UAPF Conformance Checklist §"Level 4 requirements":
+- ✓ uapf.yaml present
+- ✓ ≥1 BPMN file (`bpmn/semantic-document-analysis.bpmn.xml`)
+- ✓ `resources/mappings.yaml` present
+- ✓ `metadata/ownership.yaml` + `metadata/lifecycle.yaml` present
+- ✓ Cornerstones declared correctly (bpmn + resources)
+
+## Engine compatibility notes
+
+`uapf-engine@1.0.0` only reads `manifest.json` (pre-v1.1 file naming).
+This package ships both `uapf.yaml` (SSOT-mandated) and `manifest.json`
+(byte-identical-semantics JSON copy) for compatibility until upstream
+engine supports YAML.