Review who has access to your Bugsnag projects

**Objective:** Audit who has access to the Bugsnag project `{project-name}`, and flag anyone whose access looks stale or unfinished. Report only.

**Step 1: List the project's collaborators**

Call `bugsnag-get-project-collaborator` with `project-name` set to `{project-name}` and `max-records` set to 200. If `{project-name}` is empty, audit every project by omitting the filter, and group the report by project.

**Step 2: Fill in the organization detail**

Call `bugsnag-get-collaborator` with `max-records` set to 200 and match on `collaborator-id`. From it read `last-request-at-date`, `pending-invitation`, `two-factor-enabled`, `administrator` and `paid-for`.

**Step 3: Flag what matters**

Flag a collaborator when any of these holds:

* `pending-invitation` is true, meaning they were invited and never joined
* `last-request-at-date` is more than `{stale-days}` days ago (default 90), or is empty
* `two-factor-enabled` is false
* `administrator` is true, since an admin has access whether or not they are on the project

**Step 4: Report**

Give a table of collaborators with name, email, role on the project, last request, and the flags raised. Follow it with a short list of the access worth reviewing and why. Do not make the removal decision.

**Rules & Guidelines:**

* Read-only. Do not call `bugsnag-add-project-collaborator` or `bugsnag-update-project`.
* Do not recommend removing anyone. Report the evidence and let the user decide.
* Say which checks you could not make when a field came back empty.

**Validation:**

* If the project has no collaborators, say so; it usually means the project name did not resolve rather than that nobody has access.
* If `{stale-days}` is not supplied, use 90 and say which threshold you applied.