Завершить разделение SDK и внешних проектов

release_docs/en/getting_started.md

@@ -10,14 +10,15 @@ After extracting `sprinter-c-v1.0-<host>.tar.gz` you've got:
 * **`lib/sprinter.lib`** — the Sprinter target libc (prebuilt; rebuilt by `make` if you modify libc sources).
 * **`runtime/`** — crt0 variants and runtime helpers (assembled per-build).
 * **`toolchain/mkexe/`** — host utility that packs SDCC's `.ihx` into a SprintEXE.
-* **`examples/`** — 27 ready-to-build programs.
+* **`tests/` + `testkit/`** — SDK regression programs and host tests.
+* **`app.mk`** — standalone application build/run rules.
 * **`docs/{en,ru}/`** — this documentation.
 
 ## First build
 
 ```sh
 cd sprinter-c-v1.0-<host>
-make all                    # rebuild lib + every example (~30 s)
+make all                    # rebuild tools, libraries and SDK tests
 ```
 
 If `make` complains about a missing SDCC binary, fetch it once:
@@ -48,8 +49,9 @@ ESTEX DSS shell.
 The release does **not** include the MAME emulator or the Sprinter ROM /
 DSS / HDD images — those are large and have their own licensing.  To test:
 
-* **MAME:** install MAME 0.283+ separately, obtain Sprinter Sp2000 images from
-  Peters Plus, mount a FAT12 floppy with your `.exe` files as `-flop1`.
+* **MAME:** install a build with the Sprinter driver and prepare `MAME_HOME`
+  containing `mame.arm`, `roms/`, DSS floppy and system CHD. `make floppy`
+  creates a local SDK test disk; `make run MAME_HOME=/path/to/runtime` mounts it.
 * **Real Sprinter:** copy `.exe` to a floppy or HDD partition that DSS can
   see, then `RUN HELLO` from the shell.
 
@@ -57,5 +59,5 @@ DSS / HDD images — those are large and have their own licensing.  To test:
 
 * Read `sprinter_cc.md` for compiler flags.
 * Read `memory_modes.md` when you start needing more than 14 KB of code.
-* Browse `examples/` — every file is a working program with comments.
+* See `examples.md` for SDK tests and the separate Examples project.
 * See `headers.md` for the public API surface.