v7.0.0-next.1

• remove deprecated row-by-row native QA matrix tooling from the active release process
• add a concise H6 RC readiness packet that keeps stable-release approval separate from Developer Preview
• keep Developer Preview verification focused on smoke-test notes and release-gate output
• document that the current source is prepared for 7.0.0-next.1 while the latest published Developer Preview is still 7.0.0-next.0
• require the full H6 owner decision set for release-candidate approval
• guard the required CKV2 command surface and Developer Preview publish manifest in tests
• guard the release-gate-required package scripts and GitHub issue-template
  fields in tests
• verify the main CI workflow in the release gate so required lint, security,
  typecheck, test, e2e, surface, docs, RN CLI, benchmark, and build checks do
  not drift
• add a local Developer Preview publish preflight that runs the preview gate,
  rebuilds packages, pack-checks all release packages, and verifies the expected
  pre-publish npm registry state
• harden npm publish checks so registry/network errors fail instead of being
  treated as unpublished packages
• verify the selected npm dist-tag after publish and require current-version
  changelog notes before creating GitHub release notes
• run the selected release gate inside the publish workflow before package-state
  checks or npm writes
• block next publishes unless H5 owner approval has been recorded and block
  latest publishes unless H6 owner approval has been recorded
• record post-publish npm evidence through npm run release:publish:evidence
  and upload the generated evidence JSON from the next publish workflow
• guard package manifest entries, package order, package versions, and the
  Pro/Skia unpublished boundary in tests
• use lockfile-based npm ci --ignore-scripts installs with npm caching in CI,
  native-release, and publish workflows
• record the latest high/critical npm security audit result while keeping the
  known moderate Expo/PostCSS advisory documented
• rename release docs and publish-manifest fields from beta wording to Developer Preview wording
• keep Pro and Skia unpublished while preserving pack checks and preview evidence