Put the explanation on a failed Ghost Inspector suite run

**Objective:** Attach the explanation `{message}` to the most recent failed run of the Ghost Inspector suite named `{suite-name}`, within the last `{lookback-days}` days (default 7), so the failure is on the record.

**Step 1: Identify the suite**

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

**Step 2: Find the run to annotate**

Call `ghost-inspector-get-suite-result` with `suite-id` from step 1, `passing` false and `date-created.from` at the start of the window. Take the most recent. Keep its `id`, that is the suite result id the comment attaches to. If there are no failed runs in the window, say so and stop; do not comment on a passing run.

**Step 3: Check nobody has already explained it**

Call `ghost-inspector-get-suite-result-comment` with `suite-result-id` from step 2. If a comment already says substantially the same thing as `{message}`, quote it, say the run is already annotated and stop without writing. If there are comments but they say something different, quote them and carry on.

**Step 4: Summarise what actually failed**

Call `ghost-inspector-get-test-result` with the `suite-id` from step 1, `passing` false and a `date-created.from` at the start of that suite run, so you can name the tests that failed within it.

**Step 5: Confirm, then write once**

Show the user the suite, the run date, its pass and fail counts, the tests that failed, and the exact comment text you will post. Ask for confirmation. On an explicit yes, call `ghost-inspector-add-suite-result-comment` with `suite-result-id` from step 2 and `message` set to `{message}`. Call it exactly once.

**Step 6: Report**

Confirm the comment was added, and restate which run it landed on with its date and fail count.

**Rules and guidelines:**

* `ghost-inspector-add-suite-result-comment` is the ONLY tool here that may write, once, after the confirmation in step 5.
* Do NOT call `ghost-inspector-cancel-suite-run`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-test`, `ghost-inspector-update-suite` or any create or duplicate tool.
* Post `{message}` as the user wrote it. Do not rewrite or embellish it; put your own findings in the report to the user instead.

**Validation:**

* If `{suite-name}` matches nothing, list some suite names and stop.
* If `{message}` is empty, ask for the explanation text and stop.
* If the user declines the confirmation, stop without writing.