docs: document enterprise testing coverage gates

[OgeonX-Ai]

Summary

• document the current verified release baseline and 100% coverage policy
• add the release gate matrix that maps local commands to CI jobs
• link operator testing and enterprise gates from README surfaces

Verification

• git diff --check
• npm.cmd run release:verify

Notes

• The documentation explicitly avoids claiming unknown failures are impossible; new defects must become regression tests.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a0352d9d16

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add clean install to the local release gate path

When an operator follows this matrix locally, release:verify is described as the aggregate of the gates above, but universal-refiner/package.json shows it starts at npm run build and never runs npm ci. That lets a release be certified against stale or locally patched node_modules, missing the clean-install gate that CI enforces; either add npm ci as an explicit local step before this row or stop calling release:verify the aggregate of the listed gates.

Useful? React with 👍 / 👎.