feat(schemas): add reserve scenario report contract for software operational risk

[mdheller]

Summary

Adds the first reserve/report envelope for the software operational risk lane:

• schemas/ReserveScenarioReport.json
• examples/reservescenarioreport.json
• docs/software-oprisk-reserve-envelope.md

Why here

Before writing, the current upstream main head was re-checked. The earlier machine-readable incident/watchlist lane has already merged via PR #24, so this PR extends that typed contract family with a financially legible output object rather than mutating the earlier branch.

Purpose

This contract gives the stack a typed object for:

• expected annual loss
• benchmark reserve
• scenario reserve
• suggested reserve
• current-versus-target control deltas
• scenario-level reserve contributions

Follow-on

• add scenario-run / model-metadata envelopes
• add explicit typed references to incident/watchlist inputs
• expose the report family through OpenAPI / AsyncAPI when first consumers are ready

[mdheller]

Follow-up added on the same branch after re-checking current upstream state:

• schemas/SoftwareOperationalScenarioRun.json
• examples/softwareoperationalscenariorun.json
• docs/software-oprisk-scenario-run.md

This extends PR #47 from a reserve/report envelope into a fuller typed report family by adding explicit scenario-run lineage from typed incident and watchlist inputs to typed reserve/report outputs.

[mdheller]

Follow-up added on the same branch:

• schemas/SoftwareOperationalAnalysisBundle.json
• examples/softwareoperationalanalysisbundle.json
• docs/software-oprisk-analysis-bundle.md
• schemas/SoftwareOperationalScenarioRun.json
• examples/softwareoperationalscenariorun.json
• docs/software-oprisk-scenario-run.md

This deepens PR #47 from a reserve/report envelope into a fuller typed report family with explicit run→report lineage and an additive bundle object that binds them together.