instructions: point the repository link at ai-bot/vardkey, describe the three history card states and the closure source

This commit is contained in:
ai-bot committed 2026-10-28 17:22:46 +00:00
1 parent 46cb0d3135
commit 18dbca9204
1 file changed
+3 -1
+3 -1
View File
@@ -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**: