From 41bb6efcda85802143dfa60de1f73d682b2180c5 Mon Sep 17 00:00:00 2001 From: Joseph Spiker Date: Tue, 6 Oct 2026 05:09:22 -0400 Subject: [PATCH] docs: correct spikersoft-backend in the beta README spikersoft-backend@master SpikerSoft.EventHandlers.Scheduler/TaskRunners/ProfileCompletionReminderTaskRunner.cs:13 Co-authored-by: Cursor --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f861625..b2c2065 100644 --- a/README.md +++ b/README.md @@ -1309,6 +1309,7 @@ When a child account user's age naturally progresses past the child threshold, t - **Interest Profiles**: Both parents and children maintain interest profiles with star ratings across dynamically managed areas of interest (e.g., Hiking, Robotics, Photography) that inform curriculum and experience recommendations. - **Withdraw Pending Requests**: Parents can withdraw (cancel) pending child account requests before staff reviews them. The request is permanently deleted. Available from both the parent dashboard and the profile's Children tab. - **Remove Linked Children**: Parents can remove an approved child account. This deletes the child's Keycloak user, deletes their provisioned email mailbox (via PostfixAdmin), removes their profile from MongoDB, and revokes the original request. The parent's `IsParent` flag is preserved (once a parent, always a parent). If the email mailbox deletion fails (e.g., database offline), a `DeleteEmailMailbox` provisioning task is created for staff to retry or manually resolve from the System Issues page. +- **Student Git repository**: Approving a child creates a Gitea repository when Gitea is configured. If that create fails, staff get a `GiteaStudentRepository` provisioning task and approval still succeeds. No task is created when Gitea is not configured. ### Role-Based Access @@ -2437,7 +2438,7 @@ SpikerSoft uses a distributed event handler architecture. The .NET workers are s | **Ocr** | Passport-OCR RPC lane (`ocr.passport.*`) | | **PhotographProcessor** | Photo pipeline: receive → scan → metadata extract → move (see [Photography & Gallery](#photography--gallery)) | | **QuizGeneration** | LLM-powered quiz generation from book content (GPU-scheduled) | -| **Scheduler** | Scheduled task execution (GeoIP updates, HTTP callbacks) | +| **Scheduler** | Scheduled task execution: GeoIP updates, HTTP callbacks, profile-completion reminders, calendar feed refresh, climbing-catalog refresh, region-species refresh, and calendar reminder scheduling | | **SecurityMonitor** | Redis-backed stateful detectors over `system.events` producing security alerts | | **SecurityScanner** | Uploaded content security scanning | | **SystemRemediation** | Rule engine over system events: dedupes incidents and alerts operators. Shipped posture is recommend-only; a SAFE command is dispatched only when `Remediation:Mode` is `auto` and `DispatchCommands` is true | @@ -2455,6 +2456,8 @@ The queue set is code-derived and grows with the handler fleet — treat the han | `book.create.requests`, `image.extraction`, `metadata.extraction.requests`, `quiz.generation`, `upload.lifecycle`, `file.operations`, `security.scan.requests` | Book/upload processing pipeline | | `game.events` (+ `game.events.dlx`), `game.persistence.events` (+ dlq) | Game server persistence | | `art.asset.*`, `art.model.*` | Art Studio stage dispatch + per-model queues + lifecycle events | +| `qr.art.*` | QR Art stylization on `qr.art.lifecycle` (worker queue `qr.art.generate.requests`) | +| `photograph.autotag.*` | Florence-2 photo auto-tag on `photograph.autotag.lifecycle` (worker queue `photograph.autotag.requests`) | | `gpu.lease.*` | GPU coordinator lease protocol | | `photograph.*` | Photo pipeline | | `decompile.*`, `ocr.passport.*` | Direct-reply-to RPC lanes | @@ -2630,7 +2633,7 @@ Skill definitions with per-user awards (`SkillsController`): award-by-interest l ### Calendar & availability -A `/calendar` route and `CalendarController` store the events. In deduce mode the profile **Schedule** tab rolls those events up into a weekly Free/Limited/Busy grid; direct mode uses the weeks the user paints. Reminders dispatch through the `CalendarReminders` handler. +A `/calendar` route and `CalendarController` store the events. In deduce mode the profile **Schedule** tab rolls those events up into a weekly Free/Limited/Busy grid; direct mode uses the weeks the user paints. Reminders dispatch through the `CalendarReminders` handler. Signed-in users can subscribe to a webcal or http(s) `.ics` feed at `api/Calendar/subscriptions`; the scheduler re-polls those feeds and imports the events. ### Geography explorer globe