# ApiVault v1.3.3 — SavedVariables Runtime Probe + Bridge Report Fix

## Problem

`C_AddOns.GetAddOnMetadata(addonName, "SavedVariables")` is not a reliable source for `.toc` SavedVariables directives.

The client may expose metadata such as Title, Notes, Author, Version or custom `X-...` fields, while not exposing `SavedVariables` or `SavedVariablesPerCharacter` through this API.

Therefore this logic is wrong:

```text
GetAddOnMetadata(addon, "SavedVariables") is nil
=> addon has no SavedVariables
```

## Correct model

ApiVault now uses:

```text
1. Runtime global probes
2. Public Developer API SavedVariables reports
3. Known/inferred DB name hints
4. Optional GetAddOnMetadata diagnostic context
```

## Example

For StockVault, ApiVault probes:

```text
StockVaultDB
StockVaultCharDB
StockVaultCharacterDB
StockVaultSavedVariables
```

and shows:

```text
Runtime global probe
Public Developer API reports
Expected file: WTF/Account/<Account>/SavedVariables/StockVault.lua
```

## Recommended addon bridge report

Integrated addons should call:

```lua
AV:ReportSavedVariables({
    name = "StockVaultDB",
    initialized = type(StockVaultDB) == "table",
    schemaVersion = type(StockVaultDB) == "table" and StockVaultDB.schemaVersion or nil,
    scope = "account",
    expectedFile = "WTF/Account/<Account>/SavedVariables/StockVault.lua",
    source = "StockVault ApiVaultBridge",
})
```

## Commands

```text
/av savedvariables
/av schema
/av sv
```

## Safety

```text
- read-only global probes
- no file-system reads
- no SavedVariables mutation
- no protected/secure execution
```
