Release: prepare CaeReflex 2.0.0b6

[khalid-saqr]

Release

Prepare CaeReflex 2.0.0b6 as a consolidation release after the Gate 5–8 platform build and the merged strategic README/GitHub Pages positioning work.

What changed

• Bumped package metadata and caereflex.version to 2.0.0b6.
• Updated package description and keywords to the current Physics-AI engineering-evidence category.
• Synchronized the README release badge and protocol table.
• Synchronized the GitHub Pages release metric and structured-data version.
• Synchronized the checked-in OpenAPI JSON and YAML contract metadata.
• Added the frozen 2.0.0b6 release summary and changelog entry.
• Updated citation metadata.
• Updated active and superseded security-support versions.
• Corrected the wiki home, release index and release navigation, which still exposed stale 1.0.0 and pre–Gate 8 facts.
• Preserved ReflexCase schema 1.0, inspection contract 2.0-alpha.3, and every independently versioned Gate 5–8 protocol.

Release character

This is a release-coherence and platform-consolidation increment. It does not change runtime, CLI, REST/OpenAPI routes or protocol behaviour from 2.0.0b5.

The release captures the current integrated platform identity—native inspection, evidence contracts, spatial evidence, deterministic physics rules and governed lifecycle—without unsupported customer, adoption, performance, valuation or acquisition claims.

Safety boundary

CaeReflex remains an evidence and workflow-control system. It does not validate simulations, prove convergence, establish mesh adequacy, certify engineering results, establish regulatory compliance or determine design safety.

Validation expected

• Package, module, citation, README, Pages and OpenAPI versions match.
• Matching release page exists and declares ReflexCase schema 1.0.
• Changelog and MkDocs navigation contain 2.0.0b6.
• Wiki strict-build and release-control tests pass.
• Core, Gate 5, Gate 6, Gate 7, Gate 8 and optional backend workflows remain green.

Scope

• 13 release, contract-metadata and public-surface files
• No runtime implementation, protocol schema, CLI route or REST/OpenAPI route change
• Both one-time synchronization workflows were removed after applying the required version replacements