docs: record where the M/O annotation goes, and lowercase hex

The annotation moves above the key, which is both what it means and what
survives Prettier. Prettier also lowercases hex digits, so the id
examples follow.

Author: RobinBol

AGENTS.md

@@ -172,7 +172,8 @@ const COMMANDS = {
   // --- Client to Server Commands ---
 
   // Description from spec.
-  commandName: { // Mandatory
+  // Mandatory
+  commandName: {
     id: 0x0000,
     args: {
       argName: ZCLDataTypes.uint8,
@@ -186,7 +187,8 @@ const COMMANDS = {
   // --- Server to Client Commands ---
 
   // Description from spec.
-  notificationName: { // Optional
+  // Optional
+  notificationName: {
     id: 0x0020, // 32
     direction: Cluster.DIRECTION_SERVER_TO_CLIENT,
     args: {
@@ -224,11 +226,13 @@ module.exports = ExampleCluster;
 1. **Description placement**: ABOVE the attribute/command
 2. **M/O marker placement**:
    - Single-line: at END of line (`attrName: { ... }, // Mandatory`)
-   - Multi-line: on OPENING brace (`attrName: { // Mandatory`)
+   - Multi-line: on its own line ABOVE the key (`// Mandatory` then `attrName: {`),
+     below the description if there is one. Not on the opening brace: Prettier pulls a
+     comment there inside the braces, where it reads as if it belongs to `id`.
    - NEVER on closing brace
 3. **Copy exactly**: Text from spec, 1-on-1
 4. **Skip if >5 sentences**: Skip and only refer to section in spec
-5. **Line wrap**: Respect 100 char limit (ESLint)
+5. **Line wrap**: Respect 100 char limit (Prettier `printWidth`); run `npm run format:write`
 6. **M/O source for attrs**: Server-side column in spec table
 7. **M/O source for cmds**:
    - Server "receives" → server-side M/O
@@ -252,15 +256,15 @@ pirUnoccupiedToOccupiedDelay: { id: 0x0011, type: ZCLDataTypes.uint16 }, // 17,
 
 | Field | Format | Notes |
 |-------|--------|-------|
-| `id` | Hex (`0x0000`) | Always 4-digit format (0x0000); add decimal comment if > 9 |
+| `id` | Hex (`0x0000`) | Always 4-digit format (0x0000), lowercase digits; add decimal comment if > 9 |
 | `type` | `ZCLDataTypes.*` | See type reference below |
 | M/O | Inline comment | `// Mandatory`, `// Optional`, or `// Conditional` |
 
 #### Hex with Decimal Comments
 
 For hex values > 9 (where hex differs from decimal), add decimal in comment:
 ```javascript
-id: 0x000A, // 10
+id: 0x000a, // 10
 id: 0x0010, // 16
 id: 0x0100, // 256
 ```
@@ -271,9 +275,10 @@ id: 0x0000,
 id: 0x0009,
 ```
 
-For multi-line definitions, decimal goes on the `id:` line, M/O on opening brace:
+For multi-line definitions, decimal goes on the `id:` line, M/O above the key:
 ```javascript
-operatingMode: { // Optional
+// Optional
+operatingMode: {
   id: 0x0025, // 37
   type: ZCLDataTypes.enum8({
     normal: 0,
@@ -300,7 +305,7 @@ attr3: { ... },
 
 | Field | Required | Notes |
 |-------|----------|-------|
-| `id` | Yes | Always 4-digit hex format (0x0000); add decimal comment if > 9 |
+| `id` | Yes | Always 4-digit hex format (0x0000), lowercase digits; add decimal comment if > 9 |
 | `args` | If has params | Object with typed fields |
 | `response` | If expects response | Has own `id` and `args` |
 | `encodeMissingFieldsBehavior` | Controls the behavior of missing fields when encoding the struct | Set to `skip` if some fields are optional, omit if all fields are mandatory |
@@ -313,7 +318,8 @@ attr3: { ... },
 lockDoor: { id: 0x0000, ... }, // Mandatory
 
 // --- Server to Client Commands ---
-operationEventNotification: { // Optional
+// Optional
+operationEventNotification: {
   id: 0x0020, // 32
   direction: Cluster.DIRECTION_SERVER_TO_CLIENT,
   ...