Document dispositions, replies and group report remediation

[maximelb]

Document independent analyst dispositions, release_message, neutral report receipts and disposition-specific resolution replies. Report resolution uses the shared disposition vocabulary and optional message, campaign or group remediation. Group previews freeze recipients; repeated requests use one UUID attempt and confirmation, and incomplete execution leaves the report open.

Add bounded CLI waiting and resume examples, permission requirements, event group IDs and the distinction between provider placement and the reported original's disposition.

Risk: publish only after the matching SDK/CLI is released. Examples were checked against the corresponding public SDK change; they are not yet in the stable CLI release.

Validation: strict documentation build passed, command flags and SDK signatures checked. After the service and CLI releases, run the synthetic preview/confirm flow and verify the documented pending, timeout/resume and original-only results.

🤖 Generated with Claude Code

[maximelb]

/lc-review

[limacharlie-refractionpoint]

LimaCharlie Cloud Security — code scan

No new code findings were introduced by this pull request.

This check reports and never fails: no gating.fail_on is set on the code_scanning policy.

Scanned refractionPOINT/documentation 49b3513…8a37d2a — only findings new in the head commit are listed; anything already on the base branch is the repository's own finding set, on the Cloud Security Code page.

This comment is updated in place on every push to this pull request.

[maximelb]

/lc-review

[maximelb]

/lc-review

[maximelb]

/lc-review

The merge-base changed after approval.

[maximelb]

Adversarial follow-up review completed: required UUID group attempts, frozen request preservation across preview/confirm/polling, bounded waiting and timeout results, unknown/partial outcome refusal, permissions and original-only classification are covered by the corresponding unit tests and documented workflow. Command flags/signatures and public links were checked. Exact current-head CI passes.

A fresh /lc-review was requested, but no substantive new AI review has arrived after more than 40 minutes. Empty approval bodies are not content reviews. This public PR remains open for Maxime; documentation publication must follow the corresponding stable SDK/CLI release.

[maximelb]

/lc-review

The merge-base changed after approval.

The merge-base changed after approval.