FIX [SCMS] un-haunt test suite + stabilize API app initialization 🧪 #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR stabilizes the API’s core wiring and restores trust in the test suite by eliminating divergent app initialization paths and enforcing a single, canonical test app factory.
What began as intermittent 404s and “missing initializer” errors was ultimately a systems-boundary issue: tests, runtime, and environment configuration had quietly drifted out of alignment. This PR realigns them.
Key Changes
🧪 Test Infrastructure
createTestApphelper used by all test suitesapi()helper🧬 Application Wiring
⚙️ Environment Configuration
Why This Matters
The issue was not failing logic, but incoherent system boundaries.
Multiple app instantiation paths, inconsistent route registration, and implicit test data assumptions produced failures that looked chaotic but were actually structural.
This PR does not merely “fix tests” — it:
Status