@matter/types 0.13.1-alpha.0-20250508-047aa0277 → 0.13.1-alpha.0-20250511-74ef153aa

package/src/clusters/media-input.ts

@@ -84,7 +84,7 @@ export namespace MediaInput {
         index: TlvField(0, TlvUInt8),
 
         /**
-         * This field shall indicate the type of input
+         * ### This field shall indicate the type of input
          *
          * @see {@link MatterSpecification.v14.Cluster} § 6.9.5.2.2
          */
@@ -186,9 +186,8 @@ export namespace MediaInput {
 
         commands: {
             /**
-             * Upon receipt, this command shall change the media input on the device to the input at a specific
-             *
-             * index in the Input List.
+             * Upon receipt, this command shall change the media input on the device to the input at a specific index in
+             * the Input List.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.9.7.1
              */

package/src/clusters/media-playback.ts

@@ -75,10 +75,9 @@ export namespace MediaPlayback {
         /**
          * AudioAdvance (AA)
          *
-         * This feature is for a device or app that supports playing audio during fast and slow advance and
-         *
-         * rewind (e.g., while playback speed is not 1). A device that supports this feature may only support playing
-         * audio during certain speeds.
+         * This feature is for a device or app that supports playing audio during fast and slow advance and rewind
+         * (e.g., while playback speed is not 1). A device that supports this feature may only support playing audio
+         * during certain speeds.
          *
          * A cluster implementing AA shall implement AS.
          *
@@ -669,10 +668,9 @@ export namespace MediaPlayback {
             startTime: Attribute(0x1, TlvNullable(TlvEpochUs), { default: null }),
 
             /**
-             * Indicates the duration, in milliseconds, of the current media being played back
-             *
-             * or null when duration is not applicable (for example, in live streaming content with no known duration).
-             * This attribute shall never be 0.
+             * Indicates the duration, in milliseconds, of the current media being played back or null when duration is
+             * not applicable (for example, in live streaming content with no known duration). This attribute shall
+             * never be 0.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.10.6.3
              */
@@ -871,7 +869,6 @@ export namespace MediaPlayback {
 
             /**
              * Upon receipt, this shall start playback of the media in the forward direction in case the media is
-             *
              * currently playing in the backward direction or is not playing. If the playback is already happening in
              * the forward direction receipt of this command shall increase the speed of the media playback.
              *
@@ -939,10 +936,9 @@ export namespace MediaPlayback {
             /**
              * AudioAdvance
              *
-             * This feature is for a device or app that supports playing audio during fast and slow advance and
-             *
-             * rewind (e.g., while playback speed is not 1). A device that supports this feature may only support
-             * playing audio during certain speeds.
+             * This feature is for a device or app that supports playing audio during fast and slow advance and rewind
+             * (e.g., while playback speed is not 1). A device that supports this feature may only support playing audio
+             * during certain speeds.
              *
              * A cluster implementing AA shall implement AS.
              *
@@ -1002,8 +998,8 @@ export namespace MediaPlayback {
             previous: OptionalCommand(0x4, TlvNoArguments, 0xa, TlvPlaybackResponse),
 
             /**
-             * Upon receipt, this shall cause the handler to be invoked for "Next". User experience is context-
-             * specific. This will often Go forward to the next media playback item.
+             * Upon receipt, this shall cause the handler to be invoked for "Next". User experience is context-specific.
+             * This will often Go forward to the next media playback item.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 6.10.7.6
              */

package/src/clusters/messages.ts

@@ -561,11 +561,11 @@ export namespace Messages {
              * combination of a company name and friendly name, for example, ”Acme” or “Acme Streaming Service on
              * Alice’s Phone”.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * It is currently not specified where the friendly name label can be found on the node, meaning that
-             * clients SHOULD NOT rely on a certain method they happen to observe in a particular server instance, since
-             * other instances could employ a different method.
+             * > It is currently not specified where the friendly name label can be found on the node, meaning that
+             *   clients SHOULD NOT rely on a certain method they happen to observe in a particular server instance,
+             *   since other instances could employ a different method.
              *
              * The device SHOULD make it possible for the user to view which nodes have access to this cluster and to
              * individually remove privileges for each node.

package/src/clusters/microwave-oven-mode.ts

@@ -168,9 +168,8 @@ export namespace MicrowaveOvenMode {
          * specification of the derived cluster defines a namespace, the set of standard mode tags also includes the
          * mode tag values from that namespace.
          *
-         * Mode tags can help clients look for options that meet certain criteria, render the user interface, use
-         *
-         * the mode in an automation, or to craft help text their voice-driven interfaces. A mode tag shall be either a
+         * Mode tags can help clients look for options that meet certain criteria, render the user interface, use the
+         * mode in an automation, or to craft help text their voice-driven interfaces. A mode tag shall be either a
          * standard tag or a manufacturer specific tag, as defined in each ModeTagStruct list entry.
          *
          * A mode option may have more than one mode tag. A mode option may be associated with a mixture of standard and

package/src/clusters/mode-base.ts

@@ -162,9 +162,8 @@ export namespace ModeBase {
          * specification of the derived cluster defines a namespace, the set of standard mode tags also includes the
          * mode tag values from that namespace.
          *
-         * Mode tags can help clients look for options that meet certain criteria, render the user interface, use
-         *
-         * the mode in an automation, or to craft help text their voice-driven interfaces. A mode tag shall be either a
+         * Mode tags can help clients look for options that meet certain criteria, render the user interface, use the
+         * mode in an automation, or to craft help text their voice-driven interfaces. A mode tag shall be either a
          * standard tag or a manufacturer specific tag, as defined in each ModeTagStruct list entry.
          *
          * A mode option may have more than one mode tag. A mode option may be associated with a mixture of standard and
@@ -273,9 +272,7 @@ export namespace ModeBase {
     }
 
     /**
-     * This command is sent by the device on receipt of the ChangeToMode command. This command
-     *
-     * shall have the following data fields:
+     * This command is sent by the device on receipt of the ChangeToMode command.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 1.10.7.2
      */
@@ -289,9 +286,7 @@ export namespace ModeBase {
     });
 
     /**
-     * This command is sent by the device on receipt of the ChangeToMode command. This command
-     *
-     * shall have the following data fields:
+     * This command is sent by the device on receipt of the ChangeToMode command.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 1.10.7.2
      */

package/src/clusters/mode-select.ts

@@ -149,9 +149,7 @@ export namespace ModeSelect {
              * If this attribute is not present or is set to null, it shall NOT have an effect, otherwise the
              * CurrentMode attribute shall depend on the OnOff attribute of the On/Off cluster
              *
-             * The value of this field shall match the Mode field of one of the entries in the SupportedModes
-             *
-             * attribute.
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 1.9.6.6
              */
@@ -215,9 +213,7 @@ export namespace ModeSelect {
             /**
              * This attribute represents the current mode of the server.
              *
-             * The value of this field must match the Mode field of one of the entries in the SupportedModes
-             *
-             * attribute.
+             * The value of this field must match the Mode field of one of the entries in the SupportedModes attribute.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 1.9.6.4
              */
@@ -234,9 +230,7 @@ export namespace ModeSelect {
              * This behavior does not apply to reboots associated with OTA. After an OTA restart, the CurrentMode
              * attribute shall return to its value prior to the restart.
              *
-             * The value of this field shall match the Mode field of one of the entries in the SupportedModes
-             *
-             * attribute.
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
              *
              * If this attribute is not implemented, or is set to the null value, it shall have no effect.
              *
@@ -274,9 +268,7 @@ export namespace ModeSelect {
      * of a laundry machine.
      *
      * The server allows the client to set a mode on the server. A mode is one of a list of options that may be
-     * presented by a client for a user choice, or understood by the client, via the semantic tags on the
-     *
-     * mode.
+     * presented by a client for a user choice, or understood by the client, via the semantic tags on the mode.
      *
      * A semantic tag is either a standard tag within a standard category namespace, or a manufacturer specific tag,
      * within the namespace of the vendor ID of the manufacturer. If there is no semantic tag, the mode is anonymous,

package/src/clusters/network-commissioning.ts

@@ -116,7 +116,7 @@ export namespace NetworkCommissioning {
         NetworkNotFound = 5,
 
         /**
-         * Cannot find AP: Mismatch on band/channels/regulatory domain/ 2.4GHz vs 5GHz
+         * Cannot find AP: Mismatch on band/channels/regulato ry domain / 2.4GHz vs 5GHz
          */
         RegulatoryError = 6,
 
@@ -605,7 +605,7 @@ export namespace NetworkCommissioning {
         /**
          * See Breadcrumb for usage.
          *
-         * Effect when received
+         * ### Effect when received
          *
          * If the Networks attribute does not contain a matching entry, the command shall immediately respond with
          * NetworkConfigResponse having NetworkingStatus status field set to NetworkIdNotFound.
@@ -625,7 +625,7 @@ export namespace NetworkCommissioning {
          * Re-ordering to the same NetworkIndex as the current location shall be considered as a success and yield no
          * visible changes of the Networks attribute.
          *
-         * Examples of re-ordering
+         * ### Examples of re-ordering
          *
          * To better illustrate the re-ordering operation, consider this initial state, exemplary of a Wi-Fi device:
          *
@@ -680,7 +680,7 @@ export namespace NetworkCommissioning {
         /**
          * Credentials is the passphrase or PSK for the network (if any is needed).
          *
-         * Security type, cipher and credential format (passphrase or PSK) shall be contextually auto- selected during
+         * Security type, cipher and credential format (passphrase or PSK) shall be contextually auto-selected during
          * execution of the ConnectNetwork Command and during subsequent operational state network connections, based on
          * the most secure Wi-Fi security type available within beacons and probe responses for the set of all
          * discovered BSSIDs for the configured SSID. The type of PSK or passphrase used shall be inferred based on the
@@ -700,10 +700,8 @@ export namespace NetworkCommissioning {
          *
          *   • 8..63 bytes: WPA/WPA2/WPA3 passphrase
          *
-         *   • 64 bytes: WPA/WPA2/WPA3 raw hex PSK
-         *
-         * These lengths shall be contextually interpreted based on the security type of the BSSID where connection will
-         * occur.
+         *   • 64 bytes: WPA/WPA2/WPA3 raw hex PSK These lengths shall be contextually interpreted based on the security
+         *     type of the BSSID where connection will occur.
          *
          * When the length of Credentials and available set of BSSID admits more than one option, such as the presence
          * of both WPA2 and WPA security type within the result set, WPA2 shall be considered more secure.
@@ -732,12 +730,12 @@ export namespace NetworkCommissioning {
     export interface AddOrUpdateWiFiNetworkRequest extends TypeFromSchema<typeof TlvAddOrUpdateWiFiNetworkRequest> {}
 
     /**
-     * The ThreadCapabilitiesBitmap encodes the supported Thread features and capabilities of a Thread- enabled network
+     * The ThreadCapabilitiesBitmap encodes the supported Thread features and capabilities of a Thread-enabled network
      * interface.
      *
-     * NOTE
+     * > [!NOTE]
      *
-     * The valid combinations of capabilities are restricted and dependent on Thread version.
+     * > The valid combinations of capabilities are restricted and dependent on Thread version.
      *
      * @see {@link MatterSpecification.v14.Core} § 11.9.5.2
      */
@@ -819,14 +817,14 @@ export namespace NetworkCommissioning {
          * The semantics of the NetworkID field therefore varies between network types accordingly. It contains SSID for
          * Wi-Fi networks, Extended PAN ID (XPAN ID) for Thread networks and netif name for Ethernet networks.
          *
-         * NOTE
+         * > [!NOTE]
          *
-         * SSID in Wi-Fi is a collection of 1-32 bytes, the text encoding of which is not specified. Implementations
-         * must be careful to support reporting byte strings without requiring a particular encoding for transfer. Only
-         * the commissioner should try to potentially decode the bytes. The most common encoding is UTF-8, however this
-         * is just a convention. Some configurations may use Latin-1 or other character sets. A commissioner may decode
-         * using UTF-8, replacing encoding errors with "?" at the application level while retaining the underlying
-         * representation.
+         * > SSID in Wi-Fi is a collection of 1-32 bytes, the text encoding of which is not specified. Implementations
+         *   must be careful to support reporting byte strings without requiring a particular encoding for transfer.
+         *   Only the commissioner should try to potentially decode the bytes. The most common encoding is UTF-8,
+         *   however this is just a convention. Some configurations may use Latin-1 or other character sets. A
+         *   commissioner may decode using UTF-8, replacing encoding errors with "?" at the application level while
+         *   retaining the underlying representation.
          *
          * XPAN ID is a big-endian 64-bit unsigned number, represented on the first 8 octets of the octet string.
          *
@@ -870,10 +868,8 @@ export namespace NetworkCommissioning {
             /**
              * Indicates the maximum duration taken, in seconds, by the network interface on this cluster server
              * instance to report a successful or failed network connection indication. This maximum time shall account
-             * for all operations needed until a successful network connection is
-             *
-             * deemed to have occurred, including, for example, obtaining IP addresses, or the execution of necessary
-             * internal retries.
+             * for all operations needed until a successful network connection is deemed to have occurred, including,
+             * for example, obtaining IP addresses, or the execution of necessary internal retries.
              *
              * @see {@link MatterSpecification.v14.Core} § 11.9.6.4
              */
@@ -933,9 +929,8 @@ export namespace NetworkCommissioning {
 
             /**
              * This command shall remove the network configuration from the Cluster if there was already a network
-             * configuration with the same NetworkID. The relative order of the entries in the Networks
-             *
-             * attribute shall remain unchanged, except for the removal of the requested network configuration.
+             * configuration with the same NetworkID. The relative order of the entries in the Networks attribute shall
+             * remain unchanged, except for the removal of the requested network configuration.
              *
              * If this command is received without an armed fail-safe context (see ArmFailSafe), then this command shall
              * fail with a FAILSAFE_REQUIRED status code sent back to the initiator.
@@ -1002,9 +997,8 @@ export namespace NetworkCommissioning {
              * configuration if the CommissioningComplete command (see CommissioningComplete) is not successfully
              * invoked before expiry of the Fail-Safe timer.
              *
-             * When non-concurrent commissioning is being used by a Commissioner or Administrator, the Con
-             *
-             * nectNetworkResponse shall be sent with the NetworkingStatus field set to Success prior to closing the
+             * When non-concurrent commissioning is being used by a Commissioner or Administrator, the
+             * ConnectNetworkResponse shall be sent with the NetworkingStatus field set to Success prior to closing the
              * commissioning channel, even if not yet connected to the operational network, unless the device would be
              * incapable of joining that network, in which case the usual failure path described in the prior paragraphs
              * shall be followed. Once the commissioning channel is closed, the operational channel will be started. It

package/src/clusters/occupancy-sensing.ts

@@ -61,7 +61,7 @@ export namespace OccupancySensing {
         /**
          * ActiveInfrared (AIR)
          *
-         * Supports sensing using Active InfraRed measurement (e.g. time-of- flight or transflective/reflective IR
+         * Supports sensing using Active InfraRed measurement (e.g. time-of-flight or transflective/reflec tive IR
          * sensing)
          */
         ActiveInfrared = "ActiveInfrared",
@@ -104,12 +104,10 @@ export namespace OccupancySensing {
     };
 
     /**
-     * NOTE
+     * > [!NOTE]
      *
-     * This enum is as defined in ClusterRevision 4 and its definition shall NOT be
-     *
-     * extended; the feature flags provide the sensor modality (or modalities) for later cluster revisions. See Backward
-     * Compatibility section.
+     * > This enum is as defined in ClusterRevision 4 and its definition shall NOT be extended; the feature flags
+     *   provide the sensor modality (or modalities) for later cluster revisions. See Backward Compatibility section.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 2.7.5.3
      */
@@ -136,10 +134,10 @@ export namespace OccupancySensing {
     }
 
     /**
-     * NOTE
+     * > [!NOTE]
      *
-     * This enum is as defined in ClusterRevision 4 and its definition shall NOT be extended; the feature flags provide
-     * the sensor modality (or modalities) for later cluster revisions. See Backward Compatibility section.
+     * > This enum is as defined in ClusterRevision 4 and its definition shall NOT be extended; the feature flags
+     *   provide the sensor modality (or modalities) for later cluster revisions. See Backward Compatibility section.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 2.7.5.2
      */
@@ -389,7 +387,7 @@ export namespace OccupancySensing {
             /**
              * ActiveInfrared
              *
-             * Supports sensing using Active InfraRed measurement (e.g. time-of- flight or transflective/reflective IR
+             * Supports sensing using Active InfraRed measurement (e.g. time-of-flight or transflective/reflec tive IR
              * sensing)
              */
             activeInfrared: BitFlag(4),
@@ -439,13 +437,12 @@ export namespace OccupancySensing {
             /**
              * This attribute shall specify the time delay, in seconds, before the sensor changes to its unoccupied
              * state after the last detection of occupancy in the sensed area. This is equivalent to the legacy
+             *
              * *OccupiedToUnoccupiedDelay attributes.
              *
              * The value of HoldTime shall be within the limits provided in the HoldTimeLimits attribute, i.e.
-             * HoldTimeMin <= HoldTime <= HoldTimeMax
-             *
-             * Low values of HoldTime SHOULD be avoided since they could lead to many reporting messages. A value 0 for
-             * HoldTime shall NOT be used.
+             * HoldTimeMin <= HoldTime <= HoldTimeMax Low values of HoldTime SHOULD be avoided since they could lead to
+             * many reporting messages. A value 0 for HoldTime shall NOT be used.
              *
              * The figure below illustrates this with an example of how this attribute is used for a PIR sensor. It uses
              * threshold detection to generate an "internal detection" signal, which needs post-processing to become
@@ -460,8 +457,6 @@ export namespace OccupancySensing {
              * the Occupancy attribute will be set to 1 from the start of the first period where the PIR signal exceeds
              * the threshold until HoldTime after the last moment where the PIR exceeded the threshold.
              *
-             * Figure 13. Processing of PIR signal towards Occupancy attribute using HoldTime
-             *
              * @see {@link MatterSpecification.v14.Cluster} § 2.7.6.3
              */
             holdTime: OptionalWritableAttribute(0x3, TlvUInt16, { persistent: true, writeAcl: AccessLevel.Manage }),

package/src/clusters/operational-credentials.ts

@@ -324,16 +324,16 @@ export namespace OperationalCredentials {
          *
          * The format of the new Access Control Entry, created from this, shall be:
          *
-         * NOTE
+         * > [!NOTE]
          *
-         * Unless such an Access Control Entry is added atomically as described here, there would be no way for the
-         * caller on its given Fabric to eventually add another Access Control Entry for CASE authentication mode, to
-         * enable the new Administrator to administer the device, since the Fabric Scoping of the Access Control List
-         * prevents the current Node from being able to write new entries scoped to that Fabric, if the session is
-         * established from CASE. While a session established from PASE does gain Fabric Scope of a newly-joined Fabric,
-         * this argument is made mandatory to provide symmetry between both types of session establishment, both of
-         * which need to eventually add an "Administer Node over CASE" Access Control Entry to finalize new Fabric
-         * configuration and subsequently be able to call the CommissioningComplete command.
+         * > Unless such an Access Control Entry is added atomically as described here, there would be no way for the
+         *   caller on its given Fabric to eventually add another Access Control Entry for CASE authentication mode, to
+         *   enable the new Administrator to administer the device, since the Fabric Scoping of the Access Control List
+         *   prevents the current Node from being able to write new entries scoped to that Fabric, if the session is
+         *   established from CASE. While a session established from PASE does gain Fabric Scope of a newly-joined
+         *   Fabric, this argument is made mandatory to provide symmetry between both types of session establishment,
+         *   both of which need to eventually add an "Administer Node over CASE" Access Control Entry to finalize new
+         *   Fabric configuration and subsequently be able to call the CommissioningComplete command.
          *
          * @see {@link MatterSpecification.v14.Core} § 11.18.6.8.2
          */
@@ -376,45 +376,45 @@ export namespace OperationalCredentials {
          * following shall apply:
          *
          *   1. A new FabricIndex shall be allocated, taking the next valid fabric-index value in monotonically
-         *       incrementing order, wrapping around from 254 (0xFE) to 1, since value 0 is reserved and using 255
-         *       (0xFF) would prevent cluster specifications from using nullable fabric-idx fields.
+         *      incrementing order, wrapping around from 254 (0xFE) to 1, since value 0 is reserved and using 255 (0xFF)
+         *      would prevent cluster specifications from using nullable fabric-idx fields.
          *
          *   2. An entry within the Fabrics attribute table shall be added, reflecting the matter-fabric-id RDN within
-         *       the NOC’s subject, along with the public key of the trusted root of the chain and the AdminVendorID
-         *       field.
+         *      the NOC’s subject, along with the public key of the trusted root of the chain and the AdminVendorID
+         *      field.
          *
          *   3. The operational key pair associated with the incoming NOC from the NOCValue, and generated by the prior
-         *       CSRRequest command, shall be recorded for subsequent use during CASE within the fail-safe timer period
-         *       (see Section 5.5, “Commissioning Flows”).
+         *      CSRRequest command, shall be recorded for subsequent use during CASE within the fail-safe timer period
+         *      (see Section 5.5, “Commissioning Flows”).
          *
          *   4. The incoming NOCValue and ICACValue (if present) shall be stored under the FabricIndex associated with
-         *       the new Fabric Scope, along with the RootCACertificate provided with the prior successful
-         *       AddTrustedRootCertificate command invoked in the same fail-safe period.
+         *      the new Fabric Scope, along with the RootCACertificate provided with the prior successful
+         *      AddTrustedRootCertificate command invoked in the same fail-safe period.
          *
          *     a. Implementation of certificate chain storage may separate or otherwise encode the components of the
          *        array in implementation-specific ways, as long as they follow the correct format when being read from
          *        the NOCs list or used within other protocols such as CASE.
          *
          *   5. The NOCs list shall reflect the incoming NOC from the NOCValue field and ICAC from the ICACValue field
-         *       (if present).
+         *      (if present).
          *
          *   6. The operational discovery service record shall immediately reflect the new Operational Identifier, such
-         *       that the Node immediately begins to exist within the Fabric and becomes reachable over CASE under the
-         *       new operational identity.
+         *      that the Node immediately begins to exist within the Fabric and becomes reachable over CASE under the
+         *      new operational identity.
          *
          *   7. The receiver shall create and add a new Access Control Entry using the CaseAdminSubject field to grant
-         *       subsequent Administer access to an Administrator member of the new Fabric. It is recommended that the
-         *       Administrator presented in CaseAdminSubject exist within the same entity that is currently invoking the
-         *       AddNOC command, within another of the Fabrics of which it is a member.
+         *      subsequent Administer access to an Administrator member of the new Fabric. It is recommended that the
+         *      Administrator presented in CaseAdminSubject exist within the same entity that is currently invoking the
+         *      AddNOC command, within another of the Fabrics of which it is a member.
          *
          *     a. If the Managed Device Feature is implemented by the ACL cluster, then one or more ARL entries with the
          *        new FabricIndex may be added to the ARL attribute.
          *
          *   8. The incoming IPKValue shall be stored in the Fabric-scoped slot within the Group Key Management cluster
-         *       (see KeySetWrite), for subsequent use during CASE.
+         *      (see KeySetWrite), for subsequent use during CASE.
          *
          *   9. The Fabric Index associated with the armed fail-safe context (see ArmFailSafe) shall be updated to match
-         *       the Fabric Index just allocated.
+         *      the Fabric Index just allocated.
          *
          *   10. If the current secure session was established with PASE, the receiver shall:
          *
@@ -583,7 +583,7 @@ export namespace OperationalCredentials {
         /**
          * This field shall contain the label to set for the fabric associated with the current secure session.
          *
-         * Effect on Receipt
+         * ### Effect on Receipt
          *
          * If the Label field is identical to a Label already in use by a Fabric within the Fabrics list that is not the
          * accessing fabric, then an NOCResponse with a StatusCode of LabelConflict shall be returned for the command
@@ -621,13 +621,13 @@ export namespace OperationalCredentials {
          * This field shall contain the Fabric Index reference (see fabric-index) associated with the Fabric which is to
          * be removed from the device.
          *
-         * Effect on Receipt
+         * ### Effect on Receipt
          *
          * If the FabricIndex field does not match the FabricIndex of any entry within the Fabrics list, then an
-         * NOCResponse with a StatusCode of InvalidFabricIndex shall be returned for the command and
+         * NOCResponse with a StatusCode of InvalidFabricIndex shall be returned for the command and there shall NOT be
+         * any permanent changes to any device data.
          *
-         * there shall NOT be any permanent changes to any device data. Otherwise, one of the following outcomes shall
-         * occur:
+         * Otherwise, one of the following outcomes shall occur:
          *
          *   1. If the FabricIndex matches the last remaining entry in the Fabrics list, then the device shall delete
          *      all Matter related data on the node which was created since it was commissioned. This includes all
@@ -875,7 +875,7 @@ export namespace OperationalCredentials {
              *
              * A Commissioner or Administrator SHOULD issue this command after performing the Attestation Procedure.
              *
-             * Effect When Received
+             * ### Effect When Received
              *
              * If this command is received without an armed fail-safe context (see ArmFailSafe), then this command shall
              * fail with a FAILSAFE_REQUIRED status code sent back to the initiator.
@@ -955,8 +955,6 @@ export namespace OperationalCredentials {
              * If the given Fabric being removed is the last one to reference a given Trusted Root CA Certificate stored
              * in the Trusted Root Certificates list, then that Trusted Root Certificate shall be removed.
              *
-             * WARNING
-             *
              * This command, if referring to an already existing Fabric not under the control of the invoking
              * Administrator, shall ONLY be invoked after obtaining some form of explicit user consent through some
              * method executed by the Administrator or Commissioner. This method of obtaining consent SHOULD employ as
@@ -989,10 +987,8 @@ export namespace OperationalCredentials {
              * fail with a FAILSAFE_REQUIRED status code sent back to the initiator.
              *
              * If a prior AddTrustedRootCertificate command was successfully invoked within the fail-safe timer period,
-             * which would cause the new invocation to add a second root certificate within a given fail-
-             *
-             * safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the
-             * initiator.
+             * which would cause the new invocation to add a second root certificate within a given fail-safe timer
+             * period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.
              *
              * If a prior UpdateNOC or AddNOC command was successfully executed within the fail-safe timer period, then
              * this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.

package/src/clusters/operational-state.ts

@@ -104,10 +104,9 @@ export namespace OperationalState {
      * be treated as reserved. As shown by the table, errors that may be specific to a certain Device Type or other
      * modality shall be defined in a derived cluster of this cluster.
      *
-     * The derived cluster-specific error definitions shall NOT duplicate the general error definitions.
-     *
-     * That is, a derived cluster specification of this cluster cannot define errors with the same semantics as the
-     * general errors defined below.
+     * The derived cluster-specific error definitions shall NOT duplicate the general error definitions. That is, a
+     * derived cluster specification of this cluster cannot define errors with the same semantics as the general errors
+     * defined below.
      *
      * The manufacturer-specific error definitions shall NOT duplicate the general error definitions or derived
      * cluster-specific error definitions. That is, a manufacturer-defined error defined for this cluster or a derived
@@ -239,10 +238,9 @@ export namespace OperationalState {
 
         /**
          * The total operational time, in seconds, from when the operation was started via an initial Start command or
-         * autonomous/manual starting action, until the operation completed. This includes any time
-         *
-         * spent while paused. There may be cases whereby the total operational time exceeds the maximum value that can
-         * be conveyed by this attribute, in such instances, this attribute shall be populated with null.
+         * autonomous/manual starting action, until the operation completed. This includes any time spent while paused.
+         * There may be cases whereby the total operational time exceeds the maximum value that can be conveyed by this
+         * attribute, in such instances, this attribute shall be populated with null.
          *
          * @see {@link MatterSpecification.v14.Cluster} § 1.14.7.2.2
          */
@@ -289,10 +287,9 @@ export namespace OperationalState {
 
             /**
              * This attribute represents the current phase of operation being performed by the server. This shall be the
-             * positional index representing the value from the set provided in the PhaseList Attribute,
-             *
-             * where the first item in that list is an index of 0. Thus, this attribute shall have a maximum value that
-             * is "length(PhaseList) - 1".
+             * positional index representing the value from the set provided in the PhaseList Attribute, where the first
+             * item in that list is an index of 0. Thus, this attribute shall have a maximum value that is
+             * "length(PhaseList) - 1".
              *
              * Null if the PhaseList attribute is null or if the PhaseList attribute is an empty list.
              *
@@ -379,10 +376,9 @@ export namespace OperationalState {
              * If this command is received when already in the Paused state the device shall respond with an
              * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.
              *
-             * A device that receives this command in any state which is not Pause-compatible shall respond
-             *
-             * with an OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState and shall take
-             * no further action.
+             * A device that receives this command in any state which is not Pause-compatible shall respond with an
+             * OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState and shall take no
+             * further action.
              *
              * States are defined as Pause-compatible as follows:
              *
@@ -443,7 +439,7 @@ export namespace OperationalState {
              * in an operational state from which it can be started. There may be either regulatory or
              * manufacturer-imposed safety and security requirements that first necessitate some specific action at the
              * device before a Start command can be honored. In such instances, a device shall respond with a status
-             * code of CommandInvalidInState if a Start command is received prior to the required on- device action.
+             * code of CommandInvalidInState if a Start command is received prior to the required on-device action.
              *
              * If this command is received when already in the Running state the device shall respond with an
              * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.