From 42a5e42d0878332325d4fd11ce576031471fffd9 Mon Sep 17 00:00:00 2001 From: Franz Rolfsvaag Date: Wed, 22 Jul 2026 10:23:48 +0200 Subject: [PATCH] Refresh generated core route knowledge --- knowledge/core/lumi-core.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/knowledge/core/lumi-core.md b/knowledge/core/lumi-core.md index f7fdf7f..b9d0e89 100644 --- a/knowledge/core/lumi-core.md +++ b/knowledge/core/lumi-core.md @@ -146,6 +146,7 @@ Version: 0.2.25 - POST /admin/updates/snapshots/settings - POST /admin/updates/core/check - POST /admin/updates/core/apply +- POST /admin/updates/core/deploy-branch - POST /admin/updates/core/revert - POST /admin/updates/bot - POST /admin/updates/core/zip @@ -694,7 +695,7 @@ Version: 0.2.25 ### POST /admin/settings - Purpose: Saves core settings from the admin settings form. -- Inputs: body: `localhost_login_password`, `localhost_login_username` +- Inputs: body: `git_branch`, `localhost_login_password`, `localhost_login_username` - Response format: HTTP redirect after handling the request - Access: admin access expected - Side effects: writes or mutates server-side state; may restart or stop runtime processes @@ -1384,6 +1385,15 @@ Version: 0.2.25 - Side effects: writes or mutates server-side state; publishes or streams live WebUI events - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Errors are caught and usually returned as a flash message, JSON error, or error page. Most non-API POST routes are browser form submissions and usually redirect after completion. +### POST /admin/updates/core/deploy-branch + +- Purpose: Checks, applies, reverts, or reports update state for core or plugin updates. +- Inputs: body: `branch` +- Response format: Form/action response; exact format was not detected statically. +- Access: admin access expected +- Side effects: publishes or streams live WebUI events +- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Errors are caught and usually returned as a flash message, JSON error, or error page. Most non-API POST routes are browser form submissions and usually redirect after completion. + ### POST /admin/updates/core/revert - Purpose: Checks, applies, reverts, or reports update state for core or plugin updates.