Find the clutter in your Ghost Inspector account

**Objective:** Audit how the Ghost Inspector organization named `{organization-name}` has its tests, suites, folders and data sources arranged, and list what breaks the conventions.

**Step 1: Identify the organization**

Call `ghost-inspector-get-organization` with `name.contains` set to `{organization-name}`. If more than one matches, list them with their plan and test count and stop. Keep the `id`, `test-count`, `suite-count` and `plan-name`.

**Step 2: Read the structure**

Call `ghost-inspector-get-folder`, `ghost-inspector-get-suite` and `ghost-inspector-get-data-source`, each with `organization-id` from step 1. Then call `ghost-inspector-get-test` once per suite, filtered by that suite's `id`, so you know what each suite holds.

**Step 3: Check each rule**

* suites with no `folder-id`, which sit loose at the top level
* suites whose `test-count` is zero, which never do anything
* folders that no suite references, which are empty
* tests with no `test-frequency`, which only ever run when somebody presses the button
* suites whose tests do not all share the suite's `browser` and `region`, since a per test override is usually accidental
* suites with `screenshot-compare-enabled` where the tests have it off, and the reverse
* data sources no test appears to draw on, checked by calling `ghost-inspector-get-data-source-row` with each `data-source-id` and the `organization-id` to see whether it holds any rows at all

**Step 4: Report**

One section per rule, each listing the offenders by name and id, with a count. Lead with a two line summary: how many suites, tests, folders and data sources exist, and how many findings there are. Close with the three findings worth fixing first and why.

**Rules and guidelines:**

* Read only. Do NOT call `ghost-inspector-create-suite`, `ghost-inspector-create-folder`, `ghost-inspector-create-data-source`, `ghost-inspector-update-suite`, `ghost-inspector-update-folder`, `ghost-inspector-update-test`, `ghost-inspector-update-data-source`, or any execute or duplicate tool. Report the problems, let a person fix them.
* A rule with no offenders still gets a line saying it is clean. An absent section reads as an oversight.
* An unscheduled test is not automatically wrong. Flag it, note that it may be run on demand deliberately, and do not call it a defect.

**Validation:**

* If `{organization-name}` matches nothing, list the organizations from `ghost-inspector-get-organization` and stop.
* If the suite or test lists come back at `max-records`, say the audit is partial and which sections are affected.