# Outils

`VERIFIED IN CODE` · **PARTIEL** · `#tools` · `SCREENSHOT REQUIRED`

## 1. Purpose

Flush cache, health, connection test (`ToolsPage`). WP-CLI `wp alya-hs` is the CLI equivalent.

## 2. Screenshot

`SCREENSHOT REQUIRED`

## 3. Navigation

`#tools` · WP-admin tools submenu if present: SCREENSHOT REQUIRED.

## 4. Fields

Health / connection output: NOT DETERMINED FROM CURRENT EVIDENCE this pass (WP-CLI not run).

## 5. Buttons

Flush cache, health, connection test — as implemented on ToolsPage. Exact labels: SCREENSHOT REQUIRED.

## 6. Filters

None documented from live capture.

## 7. Actions

Cache purge can be destructive (LiteSpeed). **Not clicked** this documentation pass.

## 8. Workflow

Administrator opens Tools → run health or flush as needed.

## 9. REST/API

Ops: `/alya/v1/ops/health`, snapshot, uptime (staff). WP-CLI `wp alya-hs health`: `REQUIRES ACCESS`.

## 10. Database

Flush may clear caches (`alya_hs_hotels` / transients) — exact keys NOT DETERMINED FROM CURRENT EVIDENCE without running flush.

## 11. Permissions

Administrator / tools caps. Staff: typically no purge.

## 12. Business meaning

Ops diagnostics, not a booking module.

## 13. Limitations

Live health stdout not captured. Do not invent a PASS from health warnings.

## 14. Evidence status

`VERIFIED IN CODE` · visual `REQUIRES ACCESS`