[33imattei33]

Closes the WP3 concept gap from PLAN-docs-expansion.md (Jira: ECO-19).

What's new

Five original pages in docs/04_building-apps/. They are numbered 07–11 because 05_node-grpc.md and 06_data-service-api.md already hold the plan's 05_/06_ prefixes.

Page	Covers
07_smart-contracts-overview.md	The three script types, compile and deploy flow, limits, fees, Testnet vs Mainnet differences, common mistakes
08_creating-and-launching-a-dapp.md	Walkthrough: a pledge-drive dApp (write, check complexity, configure, deploy, call, read state)
09_smart-accounts.md	How verification works; 2-of-3 multisig and escrow walkthroughs
10_smart-assets.md	Asset script rules, what the script sees, allowlist-token walkthrough
11_blockchain-updates.md	Enabling the extension, the API, the event model, rules for a reliable consumer

Samples:

• Four Ride scripts in docs/_samples/ride/ and seven TypeScript files in docs/_samples/.
• The pages show them with {literalinclude}, so the published code is exactly the code CI typechecks. No pasted copies can drift.
• The existing samples_typecheck job checks the TypeScript. I added @types/node to the samples' dev dependencies for readFile.
• A new docs/scripts/check_ride_samples.py compiles the Ride scripts with a node's /utils/script/compileCode. It needs network access, so it isn't wired into CI; that belongs to the follow-up ticket "Run docs samples against testnet in CI".

Small corrections to existing pages:

• 05_node-grpc.md said enabling the gRPC server also enables BlockchainUpdates. They are separate extension classes.
• 02_node-extensions.md described min-keep-alive as a subscription lifetime; it is the minimum client keep-alive ping interval. It also named only one of the module's two extension classes.
• Glossary entries now link to the new pages.
• PLAN-docs-expansion.md records the final numbering.

Acceptance criteria

• The 5 pages exist and are linked from 04_building-apps/index.md; the -W build passes on this PR
• The independence check and Vale pass on this PR
• Every page has a "Verified against node-scala v1.8.0" stamp with its date
• Reviewer: spot-check 3 paragraphs per page against docs.waves.tech with a search to confirm no copied prose

How it was verified

• Facts (fees, size and complexity limits, rules on asset scripts and proofs, Blockchain Updates behaviour) were traced to node-scala v1.8.0 source and to io.decentralchain:protobuf-schemas 1.6.6.
• Fees were confirmed with POST /transactions/calculateFee on both public nodes.
• All four Ride scripts compile on the Testnet node (v1.8.0-dev-e6248f2408) and the Mainnet node (DCC v1.3.5).
• The second commit applies the findings of a code review of this PR:
  • The escrow script now reads its timeout and amount from data written before locking, instead of a fixed height that Mainnet has already passed.
  • The escrow script only accepts one payout of exactly the escrowed amount with the standard fee, so funds cannot leak out through fees.
  • refund() now decrements total.
  • The compile helper and the checker script handle non-JSON and network errors.
  • check_install_snippets.py now parses directive fences that carry an argument ({literalinclude} path). Before, it silently skipped any npm install line that came after an include.
  • The limits table reconciles the per-callable and per-invocation complexity caps.
  • The Testnet's highest active feature is corrected to 26.

Not verified:

• Nothing was broadcast to the Testnet (no funded accounts).
• The Blockchain Updates grpcurl commands were not run against a live node. That page's stamp says so.

Worth knowing for review

• Mainnet is behind Testnet. It runs node v1.3.5 with features up to 16 active, so Ride V5 is its highest version. The samples use STDLIB_VERSION 5 so they deploy on both networks.
• Mainnet Set Script fee. Mainnet charges a flat 0.01 DCC, but setScript() defaults to the Testnet's per-kilobyte fee. The pages tell Mainnet users to pass fee: 1_000_000.
• SDK chain ID default. @decentralchain/transactions builders other than transfer()/massTransfer() default to chain ID 76 ('L'), which no DecentralChain network uses. The pages warn about it; the SDK itself needs a separate issue.
• Stale protobuf package. The published @decentralchain/protobuf-serialization 3.0.0 still uses the previous protobuf package names, so a generated client cannot reach a v1.8.0 node's BlockchainUpdates service. The Blockchain Updates page warns against generating from it.
• Wrong function name in the Ride reference (outside this PR). 03_functions.rst documents the native-coin balance function as decentralchainBalance, but the Testnet node only compiles dccBalance, and the Mainnet node only accepts the upstream name.
• PR size. This is about 1,200 changed lines in one PR, above the plan's ~600-line guideline. Happy to split it if that helps review.

🤖 Generated with Claude Code

[33imattei33]

Reviewed the five new pages in docs/04_building-apps/ (07–11) and the samples in docs/_samples/.

Acceptance criterion 4 (no copied prose): I spot-checked 3 paragraphs per page against docs.waves.tech with a search. No matches.

Page	Result
07 Smart Contracts Overview	✅ original
08 Creating and Launching a dApp	✅ original
09 Smart Accounts	✅ original
10 Smart Assets	✅ original
11 Blockchain Updates	✅ original

CI is green on de11f3b: strict build, independence check, samples typecheck, Vale and link check.

All four acceptance criteria for ECO-19 are met. Ready to merge into dev.