Add Aegis SDK public API compatibility matrix

[El-swaggerito]

Description

Difficulty: Hard

Type: Documentation

Summary

Add a public API compatibility matrix for Aegis SDK modules.

Current Behaviour

SDK exports may drift from dashboard and contract expectations.

Expected Behaviour

The SDK should document exported modules, method stability, contract dependencies, dashboard consumers, and breaking-change rules.

Suggested Implementation

Create compatibility matrix documentation and README links.

Files or Areas Likely Affected

• docs/
• README.md
• src/

Acceptance Criteria

• Public API compatibility matrix is added.
• Major SDK exports are listed.
• Contract dependencies are documented.
• Dashboard consumers are referenced.
• Breaking-change guidance is included.
• README links to the matrix.

Additional Notes

This reduces cross-repo drift.

[CleanDev-Fix]

Hi, I'd like to work on this. I'll add a source-backed public API compatibility
matrix covering the root and testing entry points, module stability, current
companion-contract dependencies and drift, the dashboard adapter target, and
pre-1.0 breaking-change rules, then link it from the README.

I'll keep the patch documentation-only and verify relative links, export
coverage, table consistency, and the repository release gate. One boundary:
repository contract docs describe the expected interface but do not prove a
particular deployment, so the matrix will state that explicitly.

Does that scope match what you want for #152?

[Carlys17]

I'd like to work on this. I'll add a source-backed public API compatibility matrix covering root and testing entry points,
module stability, contract dependencies, dashboard consumers, and pre-1.0 breaking-change rules, then link it from the
README.