Clarify and validate developer entry paths

[HDauven]

Summary

• add a concise interface map for DuskEVM, Dusk Connect, W3sper, and raw Rusk integrations
• surface the DuskVM standards library and its token, access, security, governance, and reference-contract coverage
• move W3sper to Network Integration and replace the invalid unsynchronized transfer example with tested query and contract examples
• clarify the DuskVM deployment output and make the Hardhat 3 initialization path reproducible

Why

The Build section did not make ownership boundaries clear. In particular, the W3sper page implied that a newly generated profile could immediately sign a transfer even though direct signing requires synchronized nonce, balance, and treasury state behind a Bookkeeper.

It also failed to direct DuskVM developers to the reusable Dusk-native standards already available in contracts/standards, increasing the chance that common token, authorization, governance, and security patterns would be rebuilt unnecessarily.

This pass also checks that the quickstarts describe commands users can actually run, including the distinction between a DuskVM contract ID and its deployment transaction hash.

Validation

• npm run build (59 pages, all internal links valid)
• checked the documented standards inventory against the current contracts/main tree and source exports
• installed Forge v0.3.0 with the documented command; ran new, check, test, build, schema, verify, and call
• deployed the generated DuskVM counter to a clean two-node local Rusk 1.7.1 network with Rusk Wallet 0.3.0, then exercised increment, set_count(42), and a W3sper readback
• ran the revised W3sper examples against the live testnet node and a local data-driver contract
• deployed the generated Foundry 1.7.1 and Hardhat 3.9.1 counters to a disposable EVM chain configured with chain ID 745
• checked DuskEVM network metadata against the SDK, genesis, and deployment configuration
• reviewed all affected routes in Chromium at 1440x1000 and 390x844

Validation boundary

The public DuskEVM testnet RPC returned HTTP 503 during this pass, so a public testnet broadcast was not possible. The quickstart now explicitly tells readers to stop if the RPC is unavailable or returns a different chain ID.