New "security" tag — make your security fixes impossible to missnew

Security fixes are the one kind of entry readers genuinely need to find. So they now get their own tag, everywhere tags exist:

• Pick security on the post form (or send tag=security via API / CLI)
• Readers can filter to just security entries: ?tag=security on your public page
• The badge gets its own color in both widget themes, so it stands out in the embed too

# ship the fix, then tell people — straight from your release script
wakelog post "Fixed session fixation in login flow" \
  -t security -b "All sessions rotated. No action needed. Details in 30 days."

Why a dedicated tag instead of just "fix"? Because a security fix has a different reader: someone deciding how fast they need to upgrade, or auditing whether your product patches things at all. A filtered your-page?tag=security link is a clean answer to a security questionnaire — an unbroken history of handled issues.

If you want the full playbook (what to say on ship day vs. advisory day, when you need a CVE, how vague is too vague), we wrote it up: Security advisories vs changelog.