fix: add docs for 10 commits starting from 9ad2b8ca (2026-06-17) (#1011)

Author: lulululu-debug

docs/application/dynamic-client-registration.md

@@ -75,6 +75,14 @@ Your registration request needs at least one redirect URI. Everything else is op
 
 Applications created through DCR get a 7-day token expiration and are tagged with `dcr` for easy identification in the admin interface.
 
+## Managing a registered client
+
+Casdoor also implements [RFC 7592](https://datatracker.ietf.org/doc/html/rfc7592) so a client can read, update, or delete its own registration at `/api/oauth/register/{client_id}`:
+
+- `GET /api/oauth/register/{client_id}` — read the client's current metadata.
+- `PUT /api/oauth/register/{client_id}` — update the client's metadata.
+- `DELETE /api/oauth/register/{client_id}` — delete the client.
+
 ## Controlling DCR Per Organization
 
 Organizations control whether DCR is available through the `dcrPolicy` setting on the organization configuration page. Two values are supported:

docs/provider/faceid/overview.md

@@ -11,5 +11,7 @@ Casdoor supports Face ID as a sign-in method. Only enable it when you can ensure
 
 1. Open the Casdoor admin UI → **Providers** → **Add**.
 2. Set **Category** to **Face ID**.
-3. Choose the **Type** (e.g. Alibaba Cloud FaceBody).
-4. Fill in the required fields (e.g. **Client ID**, **Client Secret**, **Endpoint** as needed) and save.
+3. Choose the **Type**:
+   - **Alibaba Cloud Facebody** — cloud face recognition (requires the provider's credentials/endpoint).
+   - **Local UniFace** — on-device face recognition using the [UniFace](https://github.com/yakhyo/uniface) model, with no external service.
+4. Fill in the required fields (e.g. **Client ID**, **Client Secret**, **Endpoint** for cloud types) and save.