Home /Modules/debugger/CONFORMANCE.md

CONFORMANCE.md

debugger/CONFORMANCE.md · 36 line(s) · markdown

SLeeLa Debugger — Conformance Suite

Version: 0.8.0

The conformance suite turns the 1-2-3-4 lifecycle into a machine-checkable release contract.

Lifecycle

  1. Model — contract and data model exist.
  2. Implement — behavior exists in source.
  3. Integrate — connected to the execution/backend path.
  4. Verify — executable evidence demonstrates the behavior.

A capability must not be reported as production-ready merely because its API exists.

Capability matrix

CapabilityModelImplementIntegrateVerify
BreakpointsRequiredRequiredBackend-dependentRequired
WatchpointsRequiredRequiredBackend-dependentRequired
ThreadsRequiredRequiredBackend-dependentRequired
Symbols/sourceRequiredRequiredDWARF/PDB/etc.Required
MemoryRequiredRequiredBackend-dependentRequired
Crash evidenceRequiredRequiredPlatform-dependentRequired
ReplayRequiredRequiredBackend-dependentDeterministic test
SanitizersRequiredRequiredAdapter-dependentFixture test
CoverageRequiredRequiredTest integrationReport test
DAPRequiredInterfaceAdapterProtocol suite

Native truth

Portable domain state is not equivalent to native operating-system support. The conformance result must identify platform, backend, executable identity, source revision, and test evidence.

Release gate

A release candidate requires passing conformance records for every capability advertised at its declared status.