Repository Reality

This repository currently contains only 软件系统说明.docx; no source code, package manifest, lockfile, CI workflow, or existing agent instruction files were present when this file was written.
Treat the Word document as the only verified source of truth. Do not invent build, test, lint, deploy, or startup commands until executable config is added to the repo.
If code appears later, re-audit the repo and update this file from executable config before relying on the document alone.

Verified System Scope

Product scope from 软件系统说明.docx: a WeChat Mini Program connects to a beauty device over BLE 5.0 GATT, cloud services run on Tencent Cloud IoT + SCF + MySQL + Redis, and the admin console is uniapp + Vue 3 + uView Plus deployed as H5/static hosting.
Mini Program side is described as WeChat native (WXML / WXSS / JS), not uniapp.
Admin console is separate from the Mini Program. Do not merge those frontend assumptions when future code is added.

BLE frame format in the document: header 0xAA 0x55, then length, type, payload, XOR checksum.
BLE services in the document: FFE0 device info, FFE1 data communication, FFE2 OTA.
MQTT topics in the document: $iot/{product_id}/{device_name}/telemetry and $iot/{product_id}/{device_name}/event.
Cloud data model names called out in the document: users, devices, bindings, subscriptions, sessions, treatment_records, pd_data, operation_logs.

When asked to implement code in this repo, first confirm whether source files have been added since this file was created; right now there is nothing to edit except documentation.
If implementation details are needed beyond the document, state that they are unspecified instead of guessing architecture, package layout, or command lines.
Prefer updating this file only after verifying new facts from checked-in config or code, not from assumptions.