Update Kicksecure / Whonix status to reflect current plans

distros.html

@@ -102,14 +102,18 @@ <h3>As of March 2026</h3>
       <div class="distro-row">
         <div class="distro-name">Kicksecure / Whonix</div>
         <div class="distro-detail">
-          Aaron Rainbolt is actively working on a compliance path. Proposed the
-          cross-distro D-Bus interface. Plans to store only age bracket data, not
-          birthdates, with user-triggered updates when they cross bracket boundaries.
-          Privacy researchers <a href="citations.html#bellovin">have questioned</a>
-          whether any age verification mechanism is compatible with
-          privacy-focused operating systems.
+          Aaron Rainbolt started work on a compliance path, but this has been put on
+          hold following public discussion. <a
+          href="https://www.kicksecure.com/wiki/Age-api#status">Most recent
+          public statement</a> is that "Kicksecure and Whonix are currently unlikely
+          to implement an age API. This may later be updated to 'highly unlikely' or
+          'no changes planned'." Original plans were to store only age bracket data,
+          not birthdates, with user-triggered updates when they crossed bracket
+          boundaries. Privacy researchers
+          <a href="citations.html#bellovin">have questioned</a> whether any age
+          verification mechanism is compatible with privacy-focused operating systems.
         </div>
-        <div class="distro-status" style="color:var(--green);">COMPLYING</div>
+        <div class="distro-status" style="color:var(--accent);">WATCHING</div>
       </div>
 
       <div class="distro-row">