From 18dbca92044e91769f3a3743443519df169b946e Mon Sep 17 00:00:00 2001 From: ai-bot Date: Wed, 28 Oct 2026 17:22:46 +0000 Subject: [PATCH] instructions: point the repository link at ai-bot/vardkey, describe the three history card states and the closure source --- instructions.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/instructions.md b/instructions.md index 0b1e27d..9f31fcd 100644 --- a/instructions.md +++ b/instructions.md @@ -2,7 +2,7 @@ ## Documentation -- [VardKey repository](https://gitea.sondreolav.com/ai-bot/helsesjekk) — the application source, its HTTP API reference, and the development notes. +- [VardKey repository](https://gitea.sondreolav.com/ai-bot/vardkey) — the application source, its HTTP API reference, and the development notes. ## What you get on StartOS @@ -24,6 +24,8 @@ The dashboard shows the keys with their next due date and any open alerts, plus The health check form has six sections, in this order: 01 Schedule, 02 Key, 03 Compatibility, 04 External research, 05 Contact confirmation, 06 Notes. One submission records one key, and the check date may be today or earlier — never a future date. A key with an open alert cannot be checked until that alert is closed. +The history list carries one entry per saved check, with the date and the key it was recorded for, and a short status: `All OK` when the check raised nothing, `Needs follow-up` while something is still open, and `Follow-up closed` once everything that was raised has been closed. Opening a check shows the follow-up that was closed on it, with the source of each alert, so a key alert and a software alert of the same kind can be told apart. + ### Actions & Config Two actions are available on the service page, under **Actions & Config**: