Ansible/scripts/addons/webgui/docs/CORE-3.2.1RC1-REVIEW.md

Historical reference retained from the preceding release. Current deployment/contracts and evidence are in DEPLOYMENT.md, REPORTS.md, JOURNAL.md and VERIFICATION.md. Do not treat old limitations or tests as current qualification.

Historical core review. Current2.1 behavior is documented in README, API and READ-ONLY-EXPERIENCE; older capability limits below are not current release claims.

Review of supplied AIM 3.2.1rc1

Reviewed archive checksum: AIM-Ansible-3.2.1rc1.zip.sha256 matched the uploaded ZIP. Core is separately managed and was not modified.

Contract adopted

• Product: AIM 3.2.1rc1; service/wire/event API remains 1.0 / stable_1.x.
• Canonical Ansible Core remains 2.19.11.
• capabilities.execution_progress advertises summary and detail; WebGUI opts reviewed runs into progress_mode: detail.
• Detail schema play_task_host_v1 exposes safety-filtered static play/task labels, host outcomes, fixed failure hints, retries/async polls and per-host recap. Raw stdout/stderr, module arguments/results, rendered labels, paths and variables remain unavailable.
• staging_check is now a public operation and staging preflight runs before credentials and again before launch. WebGUI treats staging errors as executor deployment/access failures rather than credential failures.
• Core 3.2.1rc1 requires a private writable controller staging directory in the executor sandbox. The release-managed executor profile provisions /var/lib/aim-web-executor/.ansible/tmp, adds only that path to the writable sandbox set, sets the matching executor HOME, and runs core-staging-check as ExecStartPre.

UI mapping

WebGUI renders the detail stream into an Ansible-like live view (PLAY, TASK, host status, fixed hints, recap) but does not claim it is raw Ansible output. The stream remains memory-only and disappears after completion/navigation. Authoritative job outcome remains the Core final result/counters.