Find the gaps in your ServiceNow CMDB that break routing

**Objective:** Audit the CMDB, optionally for class `{class}` and environment `{environment}`, and list configuration items that break basic data quality rules.

**Step 1: Pull the CIs**

Call `servicenow-get-configuration-item` with class `{class}` and environment `{environment}` if given, install-status Installed, and max-records 500.

**Step 2: Apply the rules**

Flag a CI when:

* support-group is empty (nobody to route incidents to)
* assigned-to is empty
* location is empty
* the class is a server or network device and ip-address is empty
* environment is empty
* operational-status is Non-Operational while install-status is Installed (contradiction)
* two or more CIs share the same name, or the same serial-number
* serial-number is empty on a hardware class

For each duplicate serial-number, call `servicenow-get-base-configuration-item` with serial-number set to it to show every record holding it.

**Step 3: Report**

* A summary table: rule, number of CIs failing, percentage of those audited.
* A detail table, worst CIs first (most flags): name, class, environment, support-group, assigned-to, location, ip-address, flags.
* The three fixes that would clear the most flags.

**Rules & Guidelines:**

* Read-only. Do not call `servicenow-update-configuration-item`, `servicenow-update-base-configuration-item`, `servicenow-add-configuration-item` or any other add- or update- tool.

**Validation:**

* If nothing matches the filters, say so. If the pull hit 500, say the audit was capped and suggest filtering by class.