chore: prepare rc.8 with the corrected verification command

[exploitintel]

Release vehicle for PR 15 (the module verification quoting fix). Supersedes v0.1.0-rc.7, whose update path would fail closed at the verification step; rc.8 carries the parseable command and the parse-guarded tests. Forge pin unchanged. Module version 0.1.0-rc.8, versionCode 10 per policy.

[claude]

Reviewed against akita build CP2A.260805.005 / DEVICE.json. This PR's entire diff is:

module/module.prop
-version=0.1.0-rc.7      -versionCode=9
+version=0.1.0-rc.8      +versionCode=10

No kernel config, KernelSU module lifecycle, ext4 loop mounting, Docker startup, Wi-Fi routing, or packaging code is touched, and no firmware/credential/generated artifact is introduced.

Checks performed on the change itself:

• version (0.1.0-rc.8) and versionCode (10) satisfy tools/assemble-module.py's module.prop validator: matches SAFE_NAME_PATTERN, doesn't end in -dev, versionCode matches [1-9][0-9]*, and no updateJson key was added.
• versionCode increments monotonically from the prior release (9 → 10), consistent with the file's own comment ("versionCode 10 per policy" per the PR description) and module/uninstall.sh's parser (NR==4 line requires exactly this key value shape).
• No other file references the old rc.7/9 version — repo-wide grep found only an unrelated fixture string (0.1.0-rc.5) in tests/simple-installer.test.mjs, which predates this PR and isn't tied to the real release version.
• DEVICE.json / kernel/builds.json (device, kernel, KernelSU-Next, Docker identities) are unaffected and remain internally consistent with CP2A.260805.005.

No correctness or regression issues found in this diff. Nothing to change.