June 25 product hardening notes

This note summarizes a June 25 Veripsa Core hardening batch. It is deliberately short: the public site should explain what changed for users without turning engine behavior into public implementation material.

What changed

• Clearer advisory wording. PR checks now use narrower language around

overlap risk and make the advisory posture explicit.

• Draft PR visibility. Draft pull requests can receive Veripsa checks, with

copy that makes the draft context visible.

• Broader file coverage. More common application and project files can

receive useful advisories, while unsupported areas still return Unknown rather than a false sense of safety.

• A clearer Unknown state. Unknown is separated from Clear so teams can tell

the difference between "no concern found" and "not enough signal to judge."

• Content-free reliability work. Release and processing-health safeguards

were tightened. Public status pages can describe service state without exposing customer code or Core internals.

• Japanese site coverage. Core marketing, docs, pricing, support, and status

surfaces now have Japanese-language routes.

What did not change

• Veripsa Core is still advisory by default.
• Veripsa Core is not a merge queue, not an AI reviewer, and not CI.
• Source file bodies are not stored or displayed on customer surfaces.
• The public docs still describe the product at the user-contract level, not

private engine implementation.

For the rolling list of product changes, see /whats-new. For the current product contract, see /docs, /privacy, and /pricing.