# ApiVault v1.3.4 — Stability, Lazy Data and BugGrabber Direct Adapter

## Scope

```text
- lazy-load generated metadata
- implement direct BugGrabber callback/buffer adapter
- replace primary slash dispatcher with command table and legacy fallback
- centralize C_AddOns runtime adapter
- reset AppShell panel lifecycle correctly
- keep SafeRunner/security behavior unchanged
```

## Lazy data

Moved heavy generated metadata into LoadOnDemand companion addons:

```text
ApiVault_Data_Symbols
ApiVault_Data_Widgets
ApiVault_Data_Catalogs
```

These are loaded through `ApiVault.LazyData:Ensure(group)` when relevant tools are opened.

## BugGrabber direct adapter

ApiVault now uses the direct adapter when BugGrabber is available:

```text
BugGrabber.RegisterCallback(...)
BugGrabber.errors
BugGrabberDB.errors
```

The WoW error-handler mirror remains fallback only.

## Command registry

The primary `/av` routing now uses `ApiVault.CommandRegistry`. The old dispatcher remains as fallback for compatibility.

## Safety

```text
- no runtime source file reads
- no protected/secure execution
- no SafeRunner policy changes
- BugGrabber buffers are read-only
- LoadOnDemand uses C_AddOns through AddOnRuntime adapter
```
