Enhancement [CAT-FR-CO-05] Docs: validation strategy cleanup + provenance cascade

[peleskek]

📦 [CAT-FR-CO-05] Docs: validation strategy cleanup + provenance cascade

🚀 Summary

Architecture docs catch up with the federated-catalogue cleanup PR:

1. SHACL executor removed from the diagrams and prose. ShaclValidationStrategy and SchemaValidationServiceImpl now evaluate SHACL directly via the TopBraid engine — no shared ShaclValidationExecutor indirection, no separate timeout/pool configuration paragraph.
2. Provenance cascade listener documented. The asset-deletion cascade section and the delete-participant runtime sequence note now list both ValidationResultCleanupListener and ProvenanceCleanupListener as @TransactionalEventListener(BEFORE_COMMIT) consumers of AssetDeletedEvent.

Requirement: CAT-FR-CO-05 — On-demand Validation of Assets against Schemas

This change is part of the Enhancement of XFSC Federated Catalogue. Details can be found here (permalink): https://github.com/eclipse-xfsc/docs/blob/f3c6e6b6fbcc87732a1dfe83f060fa58a9a97873/federated-catalogue/src/docs/CAT%20Enhancement/CAT_Enhancement_Specifications%20v1.0.pdf

✅ What's in this PR

• Documentation updated

Modified files:

• 05_building_block_view.adoc

  • On-Demand Asset Validation Service section: replace the "delegates to ShaclValidationExecutor" line and the "TopBraid SHACL in an isolated fixed-size thread pool + hard timeout" paragraph with a single line stating that both the upload-verification and on-demand paths invoke the TopBraid SHACL engine directly, on the request thread.
  • Asset Store section: extend the deleteAsset description to mention that the cascade cleans up associated provenance credentials in addition to validation results.
  • Validation Result Storage section: rewrite the asset-deletion cascade paragraph to document both @TransactionalEventListener(BEFORE_COMMIT) consumers — ValidationResultCleanupListener (rows + best-effort graph triples) and ProvenanceCleanupListener (provenance credential rows) — and clarify that all three deletions share the asset's transaction.

• 06_runtime_view.adoc

  • Delete-participant sequence Note over AssetStore now lists both listeners.
  • Verify-credential prose drops the trailing "both flows share the same ShaclValidationExecutor for SHACL evaluation" clause and replaces it with "both flows evaluate SHACL via the same TopBraid SHACL engine".

No ADR is needed — both changes adopt patterns already established by existing ADRs and by ValidationResultCleanupListener.

🔍 Related Issues

Related to PR federated-catalogue — CAT-FR-CO-05 cleanup work (feature/CAT-FR-CO-05-cleanup-work)
Documents the corresponding behaviour for CAT-FR-CO-05 (On-demand Validation of Assets against Schemas).

📋 Checklist

• I've updated documentation if necessary
• My changes follow the project's coding style

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud