* add warning for enabled provisional clusters
* set warnings and print to console on file import
* add unit tests and .zap file for testing on provisional cluster warnings

* add element conform warning on file opening
* fix expression parsing
* print warnings to console

fix fetching baseType for commands derived from custom xml in zcl_commands_with_arguments() helper (#1509)

- hide warning icon for disabled required clusters only when ZAP is not in standalone mode
- clean up unused code
- correct documentation changes in `docs/api.md`

* Take into consideration transitive dependencies, not just root struct

* Apply changes addressing comments in PR

* Added 2 new args in previous commit:

      <arg name="arg7" type="DoubleNestedStructList" />
      <arg name="arg8" type="DeepNestedStructList" />

* Calculate struct_has_fabric_sensitive_fields only at the top level, not transitively

* Add test for struct_contains_array

* Apply suggestions from code review

Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>

* Fixup references after applying suggestions from code review

---------

Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>

0. Remove the whole process of registering a second socket listener to the same event.
1. Retain only one dirtyFlag notifier.
2. Add the transformation from the default ZAP data format, towards the IDE data format.
3. Remove state transitions in VueX store. These are not needed at all.

* set session_uuid in one place

* Revert "retrieve dirty status and send it via postMessage (#1495)"

This reverts commit 5d60f451.

JIRA: ZAPP-1185

* updating to macos-14

* only installing macos packages if missing

- Enable users to toggle device type features.
- When toggling a feature, automatically update the associated elements (attributes, commands, events) to correct conformance, and update the feature map attribute.
- Show warnings and disable feature toggle if relevant elements have conformance that is unknown or too complex to handle.
- Show detailed conformance warnings for elements if they're enabled state conflicts with conformance value.

* enabling ZAP to load multiple devices for an endpoint composition

* fixing code so there can be multiple endpoints with different consraints and conformance if necessary

* remove debug test

* PR review cleanup

- call API directly without action
- check if $serverGet defined before calling it

Attribute validation defaults to minimum and maximum defined by type if not defined by attribute. (#1481)

* Attribute validation defaults to minimum and maximum defined by type if not defined by attribute.

* Added tests

* add doc for external helpers

- Added support to process domain data parsed from XML in both formats:
<domain>General</domain> and <domain name="General"/>
- The plan to update ZAP XMLs using Alchemy will require this change, as domain definitions will be updated to the format <domain name="General">

- as_underlying_atomic_identifier_for_attributeId checks for the attribute type and returns the atomic identifier associated with it.
- JIRA: ZAPP-1385

- Add additional is_power_of_two helper for matter use case to determine odd sized data types (#1472)

- update the atomic table schema, retrieval and mapping
- Add unit tests with the example needed for Matter code
- update feature level pointer
- Updating the zap schema
- Adding support to determine if a data type is baseline type or not from the xml itself
- This is done by adding BASE_TYPE column to the atomic table and then mapping it appropriately to baseType for the zcl_atomics helper
- Adding base types for derived types in the atomic xml file
- This is done by adding baseType column to the atomic table and then mapping it appropriately to baseType for the zcl_atomics helper such that derived types can refer to base types
Cleanup
- Github: ZAP#1438

- Add the zcl extension files to part of its crc check.
- If the crc changes based on the inclusion of extensions then reload the top level template json file and turn its IN_SYNC to true and turn the old on to false
- These changes make sure that when a zcl extension file (eg json files in zcl section such as cluster-to-component.json) is updated then everything from the top level json files are loaded again
- Add tests to make sure top level template json file is reloaded when the zcl extension file is modified

- JIRA: ZAPP-1092

* Handling Cluster Extension loading when custom XML is reloaded:
* Making sure cluster extension is not duplicated when custom XML is reloaded
* Added a MANUFACTURER_CODE_DERIVED column since NULL!=NULL in SQL
* Added SIDE to the UNIQUE constraint in attributes
* Added logic to catch duplicates during loading before insertion
* Added relevant tests

JIRA ZAPP-1486

* handling enums and bitmaps declared as unsigned integers in Unify XML 
* logging warnings for each inconsistency 

* Added support for qualities in commands
* Added isLargeMessage quality
* Modified relevant queries and template helpers
* Also fixed issues with loading of attribute qualities
* Added tests for both command and attribute qualities
* updated schema diagram

- Create a flag called --upgradeZapFile which can be passed during generation to update the package paths during generation. add this to apack.json
- During generation use the flag to determine if packages should be updated in the .zap file. If the .zap file does not already have the packages mentioned in generation(uc_generate) then the .zap file is updated with those packages and saved.
- Normalize the paths in the options.zcl/template such that they can be searched accurately in the database
- Adding unit tests for checking the path upgrades to packages in the .zap file before and after generation is complete.
- JIRA: ZAPP-1456

* Copy commands and events when duplicating endpoint

- When duplicating an endpoint, only attribute states are copied. This PR extends to copy command and event states.

- fix issue #1441

- Jira: GHM_ZAP-457

Added SQL Triggers that check for undefined types in attributes,command arguments and event fields for a custom XML when inserted into a session. Add session notice as required (#1453)

Added SQL Triggers that check for undefined types in attributes ,command arguments and event fields for a custom XML when inserted into a session. Add session notice as required

Added relevant tests

Corrected typo in package.json

* creating new package id when crc mismatch instead of updating crc for existing package

* added relevant tests

* added some comments

These were just added, but it turns out they are not actually needed.

1) Add device types to availability macro generation.
2) Add some helpers that allow properly generating device type metadata.

* added clean script to build release packages

* script can be used in CI and locally

* modified instructions to build binaries locally

* modified release workflow to use build-release-package.js script