Say what the emulated apply settles, and what it still does not

[sethbergman]

The emulated AWS apply landed with a paragraph in the README and nothing
else. Every other place that describes this repository still said the
AWS profile had never been applied, full stop -- which was the precise
claim that had just stopped being true, in one specific and limited way.

Left alone, that decays in the direction this repository cares least to
decay in. A reader who found the CI job before the prose would conclude
the docs undersell what is proven, and start trusting them less on the
claims that are still exactly right. A reader who found the prose first
would not know an apply runs on every PR at all.

So the claim is now qualified everywhere rather than deleted anywhere:
neither profile has been applied to a real account. The AWS profile
applies and destroys against an implementation of the AWS API, which
settles that it applies in one pass with every reference resolved and no
value refused -- and settles nothing about behaviour, because an
emulator answers requests without booting anything. Azure has no
equivalent run, so its wording is unchanged.

Both v1.0 blockers stay blockers. What changed is that the AWS one is
now a shorter list of questions, and the cheap failures are off it.

Also syncs the counts CLAUDE.md carries, stale since the two suites that
preflight-static and cloud-apply-emulated added: 17 suites not 15, 27 CI
jobs not 25, eight static jobs not seven, and a requirements row for each
of the two.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01BBXQMdYVC346ac3fBXnCLr