Rebuild the README as an adoption surface and stop pinning claim text to it

[0j0bit]

The README is the adoption and indexing surface for MCL, and it is now written as one.

README

• Leads with a searchable definition: machine-to-machine protocol, device discovery, transport negotiation, BLE/IP/acoustic, C99.
• New sections: what MCL solves, where it fits beside MQTT/ROS 2/DDS/HTTP/CAN, use cases (robotics, embedded/IoT, provisioned fleets, offline networking, cross-transport), how it works, supported transports, get started, compiling mcl/machine.h example, architecture, repository map, compatibility and maturity, security model, specifications and conformance, contributing.
• Removed: the "What this release claims, and what it does not" section, the What is claimed navigation link, the scientist/researcher section, review-status prose, and "not adopted, not standardized, not stable".
• The code example was compiled against the release developer SDK with gcc and clang (-Wall -Wextra -Werror -pedantic) through find_package(mcl_sdk).

Publication gate

• check-publication-readiness.sh section 6 now requires the claim boundary only in conformance/ICS.md, governance/V1_SCOPE.md and releases/v1.0.0/manifest.txt. It passes with no NOT claim in the README.

Cross-references

• V1_SCOPE.md §5.9, RELEASE_GATE_V1.md and the manifest (and its generator) said the four lines also appear in README.md. They now name only the three authorities.
• The two edited governance documents are bundle artifacts, so their digests in releases/v1.0.0/SHA256SUMS.txt are refreshed from the committed bytes. All bundle checksums verify.

No protocol or specification semantics change.

🤖 Generated with Claude Code