docs: update test counts and upstream differences after PR #119, #121

Test infrastructure grew from 47→50 suites and 1,046→1,096 tests after
merging multi-node solar fix (PR #119, +24 tests) and mode sync fix
(PR #121, +8 tests). Updated all documentation references:

- CLAUDE.md, README.md, CONTRIBUTING.md: test count references
- docs/quality.md: 4 occurrences of test metrics
- docs/upstream-differences.md: added both fixes as upstream divergences
- docs/manual-test-plan.md: test count reference
- test-specification.md: regenerated (70 features, 1,082 scenarios)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: basmeerman

CLAUDE.md

@@ -605,7 +605,7 @@ All 15 plans are complete.
   logic correctness, Plan 11 tests protocol compliance
 - Plan 12 (Modbus Compat) complements Plan 05 (Meter Compatibility): Plan 05
   extracts code, Plan 12 tests it against real meter register layouts
-- All plans depend on the test infrastructure being stable (currently: 47 suites, 1,046 tests)
+- All plans depend on the test infrastructure being stable (currently: 50 suites, 1,096 tests)
 
 ## Files You Should Know
 

CONTRIBUTING.md

@@ -134,7 +134,7 @@ void test_normal_charge_cycle(void) { ... }
 The CI traceability job validates that all annotated tests have requirement IDs and
 uploads the reports as build artifacts. See the
 [test specification](SmartEVSE-3/test/native/test-specification.md) for the full
-list of 410 scenarios across 31 features.
+list of 1,082 scenarios across 70 features.
 
 ## Reporting Findings & Proposing Improvements
 

README.md

@@ -17,7 +17,7 @@ The upstream SmartEVSE firmware is a monolithic embedded C++/Arduino codebase wh
 state machine, load balancing, MQTT, HTTP, and hardware control all live in a single
 ~3,000-line `main.cpp`. This fork restructures the architecture to enable **native host
 testing** of the core logic — pure C modules, context structs, a bridge layer, and HAL
-callbacks — resulting in 1,200+ automated tests (1,046 native C tests across 47 suites,
+callbacks — resulting in 1,200+ automated tests (1,096 native C tests across 50 suites,
 50 OCPP protocol tests, and 146 Modbus compatibility tests).
 
 See [Quality Engineering](docs/quality.md) for the full architecture, testing