flashdb-integrationlisted

# FlashDB Integration ## Overview Use this skill to integrate FlashDB as an embedded key-value or time-series database. The agent should confirm storage mode, flash/file backend, sector geometry, erase policy, and data-retention requirements before formatting or deleting database sectors. ## When To Use Use this skill when: - The user wants to add FlashDB KVDB or TSDB for parameters, configuration, logs, events, or time-series records. - The issue involves init failure, sector size, erase errors, lost keys, database full, migration, blob values, timestamps, or flash wear. - The project mentions FlashDB, `fdb_kvdb`, `fdb_tsdb`, KVDB, TSDB, `fdb_cfg`, or `fdb_port`. Do not use this skill for raw filesystem work without FlashDB. Use `littlefs-integration` or storage-specific skills instead. ## First Questions Ask for: - Database type: KVDB, TSDB, or both. - Backend: raw flash, FAL partition, filesystem, or vendor storage layer. - Sector size, partition size, erase value, write alignment, and flash driver status. - RTOS or bare-metal environment and locking requirements. - Whether existing database data must be preserved. - Current error log, assert, return code, or database output. ## Integration Checklist 1. Confirm database purpose. Use KVDB for named settings and TSDB for append-style time records. Do not force both if one is enough. 1. Confirm storage backend. Identify whether FlashDB talks to raw flash, FAL, filesystem, or a custom port. 1. Match sector g