Clarify assertion flow: remove references to non-live on-chain validator checks

[soniasingla]

Pick one:

• Bug Report
• Feature Request

Description

Some documentation currently implies that validator status is checked on-chain by the assertion contract.

This is not part of the live testnet implementation today and is creating confusion for developers trying to understand the current assertion flow.

The current testnet flow uses the auto-admin mechanism, with assertion claims approved via the master key. The contract-based assertion flow, including the on-chain validator-status check, is still being built.

Expected Behaviour

Docs should clearly distinguish between:

• Current/live testnet flow: assertions are handled through the auto-admin/master-key approval flow.
• Planned/under-development flow: contract-based assertions and any on-chain validator-status checks.

Any wording that currently presents the on-chain validator-status check as live should be commented out or updated until the contract is deployed.

Related links

• https://docs.shinzo.network/reference/components/outpost/#evm-implementation

Context

The requirement to participate with an active Ethereum Mainnet validator remains unchanged. The issue is specifically that the mechanism used to enforce/verify this requirement is currently being described as on-chain when that functionality is not live yet.