[Task]: Add repository smoke tests for example scenarios

[rian-be]

Summary

Add repository smoke tests that validate the example scenarios shipped under Examples/Core and Examples/Governance.

Goal

Keep the executable examples aligned with the public API and runtime behavior by running lightweight validation pass over the scenarios that act as documentation and usage samples.

Problem

The repository includes substantial set of example projects that show how the runtime, governance layer, and Redis provider are intended to be used. Those examples are valuable, but they can drift from the real API over time if they are only exercised manually or during broad solution builds.

A smoke test layer gives the repo focused check that the samples still compile and execute their intended scenario paths. This helps catch broken examples early without turning the examples into second full test suite.

Scope

• Add smoke coverage for the example projects under Examples/Core
• Add smoke coverage for the example projects under Examples/Governance
• Validate the primary scenario entrypoints for each example project
• Keep the smoke tests lightweight and focused on example viability rather than exhaustive behavior
• Reuse example local helpers where they already exist instead of inventing shared cross example abstraction
• Make it clear which example project failed when smoke check breaks
• Keep the smoke test layer separate from the regular unit test projects

Design Expectations

• Smoke tests should verify that the examples still reflect the intended public usage.
• The checks should stay fast enough to run regularly in CI.
• Example coverage should remain readable and map back to the sample projects themselves.
• The smoke layer should prefer explicit sample entrypoints or scenario runners rather than generic reflection.
• The implementation should not require examples to become test projects if that is not already the right shape for the repo.

Suggested Coverage Surface

• Examples/Core/BillingQuotas
• Examples/Core/FeatureFlags
• Examples/Core/IamRoles
• Examples/Core/WorkflowApprovals
• Examples/Governance/ApprovalWorkflow
• Examples/Governance/GovernedExecution
• Examples/Governance/DecisionTaxonomy
• Examples/Governance/Queries
• Examples/Governance/RedisQueries
• Examples/Governance/RequestLifecycle
• Examples/Governance/VersionedResolution

Acceptance Criteria

• The repository can run lightweight smoke validation for the shipped examples
• Example scenario failures are reported with enough context to identify the broken sample quickly
• The smoke layer covers the main example groups in Examples/Core and Examples/Governance
• The solution remains easy to extend when new example projects are added
• Smoke validation stays separate from the main unit test suites

Non-Goals

• This issue does not replace the normal unit or integration test suites
• This issue does not change runtime behavior
• This issue does not require every scenario to be exhaustively asserted twice
• This issue does not redesign the example projects unless that is required for smoke validation

Notes

This is sample health and compatibility issue. The intent is to keep the examples trustworthy as executable documentation.