docs: publish Azure C3 cost-guard acceptance evidence

[ruby-dlee]

Intent

Reconcile the retained Azure-related Firstmate work occupying local capacity against current public main and the Downloads grievance definition of done. Preserve unlanded work and worker-authored reports, carry only still-required changes, and record exact evidence for work already landed or superseded. The required current-main change is the smallest coherent one: publish the already-completed C3 live cost-guard evidence without changing C1 or C2, while preserving verified result return, truthful terminalization, ordinary release, atomic staging, six-profile reuse, no-mistakes/Crosscheck isolation, the USD 100 default daily bound, credential custody, and zero-resource protections. Use focused local checks and required CI shards rather than a monolithic local suite; do not execute a fresh Azure acceptance campaign from this PR. After this lands, the next work is one real released-generation six-profile run-first loop and one clean repeat that return every result, release every resource, and complete no-mistakes and Crosscheck.

What Changed

• Publish a compact, secret-free evidence record for the completed Azure C3 live cost-guard acceptance.
• Document verification commands, source-artifact hashes, and the Cost Management telemetry limitation.
• Mark C3 as done while explicitly leaving C1 and C2 unchanged.

Risk Assessment

✅ Low: The change is a narrowly scoped publication of previously completed C3 evidence, preserves the existing C1 and C2 statuses, explicitly limits its claims, and introduces no source-verifiable behavior or intent contradiction.

Testing

The configured baseline had already passed; focused semantic checks then validated the published C3 contract and documentation links and produced a reviewer-visible transcript. No new Azure campaign was run, and no screenshot was appropriate because this is a documentation/JSON evidence-only change with no rendered UI.

Evidence: Published C3 evidence transcript

C3 acceptance: 2026-08-24 idle: threshold=600s power=deallocated queue=assigned early_release_proof=false ordinary_cleanup=true bound refusal: spend_usd=2.983466 controlled_bound_usd=1 override=none refused=true wind_down=true default reproof: bound_usd=100 tripped=false queue=0 desired=0 active=0 assignments=0 used_vcpus=0 committed_vcpus=0 scope exclusions: C1, C2 telemetry caveat: Azure Cost Management actuals lag by hours; this is a backstop on recorded spend, not a real-time meter.

C3 acceptance: 2026-08-24
idle: threshold=600s power=deallocated queue=assigned early_release_proof=false ordinary_cleanup=true
bound refusal: spend_usd=2.983466 controlled_bound_usd=1 override=none refused=true wind_down=true
default reproof: bound_usd=100 tripped=false queue=0 desired=0 active=0 assignments=0 used_vcpus=0 committed_vcpus=0
scope exclusions: C1, C2
telemetry caveat: Azure Cost Management actuals lag by hours; this is a backstop on recorded spend, not a real-time meter.

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• if [ "${FM_AZURE_VALIDATION_CELL:-0}" = 1 ]; then exec "$FM_AZURE_VALIDATION_SHARD_BRIDGE" behavior --count "${FM_AZURE_VALIDATION_SHARD_COUNT:-8}"; else exec bin/fm-no-mistakes-test-command.sh; fi
• Baseline previously passed: if [ "${FM_AZURE_VALIDATION_CELL:-0}" = 1 ]; then exec "$FM_AZURE_VALIDATION_SHARD_BRIDGE" behavior --count "${FM_AZURE_VALIDATION_SHARD_COUNT:-8}"; else exec bin/fm-no-mistakes-test-command.sh; fi
• Inspected git diff 64c77dc051b358679b26adb877e37873cc5093a9..2fed01585a75af1f16f16fa6ec6f38c049172cda to confirm the committed scope is limited to C3 documentation and its evidence record
• Executed the README’s focused jq -e evidence-contract verification, including 600-second idle deallocation, ordinary cleanup, controlled bound refusal, $100 default reproof, zero fleet state, C1/C2 exclusions, and SHA-256 field validation
• Rendered the public evidence contract with jq -r into c3-published-evidence-transcript.txt
• Resolved every relative Markdown link in docs/azure-requirements.md and the C3 evidence README and confirmed each target exists

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.