Implement TrustOps ART runner vertical slice

[mdheller]

Purpose

Implement the first TrustOps Fabric runtime slice in prophet-platform: an ART-first robustness runner that consumes functional service manifests and emits trustops-receipt.v1 receipts.

Upstream contract PR: SocioProphet/functional-model-surfaces#9

Scope

• Add a trustops-art-runner app/package lane.
• Accept a manifest path and TrustOps profile, starting with art-smoke.
• Emit trustops-receipt.v1 robustness receipts matching schemas/trustops-receipt.schema.json from functional-model-surfaces.
• Keep ART as an isolated runner dependency, not a core platform dependency.
• Support local/CI execution with synthetic fixtures first.
• Preserve the data-boundary invariant: raw regulated, customer-controlled, or personal data must not leave its boundary by default.

Initial CLI/API target

prophet trustops run --profile art-smoke --manifest examples/functional-service.example.json

Acceptance criteria

• make validate or equivalent platform validation includes the new runner fixture.
• A synthetic manifest produces a valid trustops-receipt.v1 robustness receipt.
• Receipt includes runner provenance, data boundary, metrics, policy decision, evidence refs, and actions.
• No platform core package imports ART directly.
• Follow-on ledger/guardrail integration can consume the output without provider-specific Python objects.

Strategic note

Trusted-AI/ART is a backend and regression oracle here. SocioProphet owns the receipt contract, policy interpretation, platform routing, ledger record, guardrail action, and agent authority effect.

[mdheller]

Update after PR #482 merge.

The first TrustOps ART-smoke runner slice is now merged.

Merged surface:

• apps/trustops-art-runner/src/trustops_art_runner/cli.py
• apps/trustops-art-runner/examples/functional-service.art-smoke.manifest.json
• tools/validate_trustops_art_receipt.py
• tools/smoke_trustops_art_runner.py
• docs/TRUSTOPS_ART_RUNNER.md
• Makefile target trustops-art-runner-smoke, wired into make validate

What landed:

• synthetic manifest in;
• valid trustops-receipt.v1 out;
• stable receipt digest;
• runner provenance;
• synthetic-only data boundary;
• metrics-only redaction;
• downstream action hints only.

Boundary remains explicit:

• no ART import into platform core;
• no Guardrail Fabric call;
• no Agent Registry authority mutation;
• no Model Governance Ledger write;
• no promotion, rollback, revocation, or waiver;
• no raw data export.

This establishes the receipt-first platform runner seam. A later tranche can replace the synthetic metric path with an actual ART backend behind the same receipt contract.