ai-bot
|
76f33b04b0
|
Take the security alert source from the row's own key id (32.8 point 6)
|
2026-10-24 10:19:46 +00:00 |
|
ai-bot
|
a5de2cd741
|
Security alerts: a key-sourced alert carries Key N: <name> (32.1)
|
2026-10-15 19:11:52 +00:00 |
|
ai-bot
|
2fe7937907
|
Rewrite the remaining alert messages (section 32.3)
|
2026-10-14 18:01:35 +00:00 |
|
ai-bot
|
4c67f5a899
|
Rewrite the key_unavailable alert message (section 32.3)
|
2026-10-14 17:51:06 +00:00 |
|
ai-bot
|
1152162db4
|
Section 27: the cloud-key software alert carries no removable settings entry
|
2026-10-09 09:08:24 +00:00 |
|
ai-bot
|
f98a39a0cd
|
Section 27: key-owned contact and cloud-software alerts, key-based alert identity
|
2026-10-09 09:05:14 +00:00 |
|
ai-bot
|
4a4b1015a7
|
Give every alert code its own closing actions (section 26.4)
|
2026-10-06 11:20:25 +00:00 |
|
ai-bot
|
d4ae1dec50
|
Address path mismatch alert, closing actions, acknowledgement filter (section 25.3)
|
2026-10-04 10:20:43 +00:00 |
|
ai-bot
|
4843be6dbd
|
Remove the BIP327/SLIP39 alerts (section 24.2)
|
2026-10-03 17:55:07 +00:00 |
|
ai-bot
|
f499c5c4b3
|
Read the new contact status in the follow-up alert (section 23.1)
|
2026-10-03 12:03:09 +00:00 |
|
ai-bot
|
622bffa274
|
Update file
|
2026-10-02 13:46:02 +00:00 |
|
ai-bot
|
d2bdacd662
|
alerts.py: one merged critical alert for an unavailable cloud key (section 20)
|
2026-10-02 12:24:39 +00:00 |
|
ai-bot
|
81a83a8f78
|
alerts.py: critical alert for a cloud provider problem
|
2026-10-02 09:10:28 +00:00 |
|
ai-bot
|
3024a6bb43
|
alerts.py: per-key alert rules and English security statuses (section 19)
|
2026-10-02 08:35:07 +00:00 |
|
ai-bot
|
97e734670a
|
Add alert rules for follow-up requirements
|
2026-10-02 05:20:26 +00:00 |
|