Fail smoke tests when any reflected invocation fails

[krotname]

Motivation

• The smoke harness previously counted reflective invocation failures but only asserted that at least one invocation was attempted, allowing crashes to be masked by a single successful invocation.
• The change aims to strengthen the smoke-test signal so that any crashing executable path causes the harness to fail, preserving the original intention of exposing regressions.

Description

• Change the final check in quality.SmokeMethodTestHarness.verify(...) to Assertions.assertEquals(0, failed, ...) so the harness fails when any reflected invocation throws.
• Update quality.SmokeMethodTestHarnessTest to assert that a class with any failing executable path triggers an AssertionError, renaming the test to reflect the stricter behaviour.
• Remove the now-unused assertDoesNotThrow import and keep the existing summary diagnostics in the failure message.

Testing

• Ran mvn -Dtest=quality.SmokeMethodTestHarnessTest test and the harness regression tests passed (2 tests, 0 failures).
• Ran mvn test and the full test suite completed successfully (Tests run: 597, Failures: 0, Errors: 0).
• Ran mvn -DskipTests checkstyle:check and there were no Checkstyle violations (build success).

---

Codex Task

[krotname]

Superseded by the validated combined merge in #115: #115