Add SVS verified action example

[CryptoZaddy-dev]

Summary

Adds a small example under examples/misc/svs-verified-action/ showing how a Solana Agent Kit agent can route sensitive actions through SVS before execution.

The example covers:

• installing @svsprotocol/solana
• creating one Solana Agent Kit compatible SVS verification/submission tool
• checking SVS production readiness before submitting an action
• requiring a hosted SVS registry gate so protocols/wallets can reject unverified automation
• linking public SVS docs, registry, verifier, and Verified Agent Standard

Why

Agents that can prepare Solana actions still need an application-level trust path before execution. This example shows a minimal pattern for signed bot identity, human approval, registry proof, and portable verification without changing Solana Agent Kit core.

Scope

This is an isolated example/docs package only. It does not change core framework behavior.

Public References

• Docs: https://svsprotocol.com/docs
• Registry: https://registry.svsprotocol.com/registry.json
• Verified Agent Standard: https://svsprotocol.com/docs#verified-agent-standard
• Verifier: https://svsprotocol.com/verify

Validation

From examples/misc/svs-verified-action/:

• npm run validate
• node ./svs-verified-action.mjs

Note: installing the isolated example currently reports transitive npm audit warnings from the example dependency tree; this PR does not claim audit-clean dependency status.

[CryptoZaddy-dev]

Hi maintainers, quick follow-up on this example. The public package referenced here is now published as @svsprotocol/solana@0.2.0, and this PR is intentionally scoped as an example/docs addition so it should not affect core Solana Agent Kit runtime behavior.

Happy to adjust the location, naming, or shape of the example if there is a preferred pattern for agent verification examples in this repo.

[CryptoZaddy-dev]

Quick follow-up: if this example is useful, is there a preferred location or format for maintainer-friendly verified-action examples in this repo? Happy to adjust placement, trim the scope, or keep it as a docs-only example if that fits better.