# Leftover — autopilot dead-code clippy gate

- **Timestamp**: 2026-05-20T05:30:00Z
- **Source**: discovered during batch 12 (`AZ-657` + `AZ-682`)
- **Origin**: commit `69c0629` — `[AZ-643] [AZ-665] [AZ-672]
  mavlink+mapobjects+vlm batch 4`
- **Blocked operation**: `cargo clippy --workspace --all-targets --
  -D warnings`

## Symptom

```
error: method `vlm_provider_name` is never used
  --> crates/autopilot/src/runtime.rs:84:12
   |
58 | impl Runtime {
   | ------------ method in this implementation
...
84 |     pub fn vlm_provider_name(&self) -> &'static str {
   |            ^^^^^^^^^^^^^^^^^
   |
   = note: `-D dead-code` implied by `-D warnings`
```

`Runtime::vlm_provider_name` is only called from `#[cfg(test)]` code in the
same file (`runtime.rs:215`, `runtime.rs:228`). Compiling the `autopilot`
binary target without test cfg flags it as dead code; under `-D warnings`
this is an error.

## Why not fixed in batch 12

Per `.cursor/rules/coderule.mdc`:

> Pre-existing lint errors should only be fixed if they're in the modified
> area.

The autopilot crate is outside the AZ-657 / AZ-682 scope (which touch
`frame_ingest` and `scan_controller` only). Fixing this would expand scope
and obscure the batch-12 diff. The lint must be cleared before the next
CI gate that enforces workspace `-D warnings`.

## Recommended fix

Pick the smallest of:

1. `#[cfg(test)]` on the method (it's only called from tests).
2. `#[allow(dead_code)]` on the method.
3. Add a real (non-test) caller — e.g. expose it through the `/health`
   JSON so the field becomes load-bearing.

Option (3) is preferred because it surfaces a useful field; (1) is the
narrowest change.

## Replay

This leftover requires no Jira write — it is a code-quality gate. Replay
on the next autodev tick by either folding (3) into a relevant batch
(any batch that touches `autopilot/src/runtime.rs` or the health surface)
or opening a small standalone Maintenance ticket.
