# Wind Kit Diagnostics Contracts documentation

> Wind Kit Diagnostics Contracts lets debug tools and AI agents read wind_kit widget state and counters without depending on wind_kit. Pure contracts, no UI.

## Getting Started

- [Installation](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/getting-started/installation.md): Add wind_kit_diagnostics_contracts to a package that reads or serves wind_kit widget state, and know when you do not need it.

## The Basics

- [WindDebugRegistry](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/basics/registry.md): The process-global registry that connects the side that implements the contracts (wind_kit) to the side that reads them (a debug tool).
- [WindDebugResolver](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/basics/debug-resolver.md): Read the resolved wind_kit state of any Element: class name, breakpoint, brightness, platform, states and colours.
- [WindPerfResolver](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/basics/perf-resolver.md): Read process-wide wind_kit performance counters (cache hits, build counts, inherited-widget reads) that belong to no single element.

## Guides

- [Testing](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/guides/testing.md): Test a debug tool that reads wind_kit state without wind_kit: register a fake resolver and reset the registry between tests.
- [Versioning](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/guides/versioning.md): What counts as a breaking change in this package, so a reader and an implementer know what the 1.x line promises.

## Optional

- [Wind Kit Diagnostics Contracts](https://anilcancakir.com/wind_kit_diagnostics_contracts): the package landing page
- [Full documentation](https://anilcancakir.com/wind_kit_diagnostics_contracts/docs/llms-full.txt): every page in one file