docs: say that Stalwart 1.0.0 serves JMAP Metadata in the folder and Sieve property comments

src/api/email.ts

@@ -35,11 +35,10 @@ export const EMAIL_FULL_PROPERTIES = [
   'messageId', 'inReplyTo', 'references', 'headers',
 ];
 
-// The Mailbox properties the folder list reads (RFC 8621 §2), which is also
-// the default list on 0.16 and 1.0. Stalwart 1.0 advertises JMAP Metadata
-// but its handlers are still `todo!()`: a get that selects `metadata` or
-// `privateMetadata` panics on the server. An explicit list keeps them out
-// even if a later release adds them to the default.
+// The Mailbox properties the folder list reads (RFC 8621 §2), the default
+// list on 0.16. Stalwart 1.0.0 adds JMAP Metadata's `metadata` and
+// `privateMetadata` to the default (the pre-release's handlers panicked on
+// them); the app reads neither, so an explicit list keeps them out.
 export const MAILBOX_PROPERTIES = [
   'id', 'name', 'parentId', 'role', 'sortOrder', 'totalEmails', 'unreadEmails',
   'totalThreads', 'unreadThreads', 'myRights', 'isSubscribed',

src/api/sieve.ts

@@ -9,8 +9,8 @@ import type { SieveScript, SieveCapabilities } from '../lib/sieve/types';
 
 const SIEVE_USING = [CAPABILITIES.CORE, CAPABILITIES.SIEVE];
 
-// SieveScript properties (RFC 9661 §2), explicit so a default that grows to
-// include Stalwart 1.0's unfinished JMAP Metadata can't reach the get.
+// SieveScript properties (RFC 9661 §2), explicit so JMAP Metadata, which
+// Stalwart 1.0 serves, stays out of a get that does not read it.
 const SIEVE_SCRIPT_PROPERTIES = ['id', 'name', 'blobId', 'isActive'];
 
 function requireSession() {