Restore PulseStack Monorepo Integrity and Runtime Stability#54
Open
vraj826 wants to merge 1 commit into
Open
Conversation
Author
|
Maintainers @NEXARA-oss , can you please review this! |
Owner
|
hey @vraj826 could u please fix the conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Overview
This Pull Request restores monorepo stability and resolves critical merge-corruption issues affecting PulseStack’s runtime, contracts, frontend, and workspace tooling.
The implementation focuses on restoring deterministic runtime behavior, repairing broken pnpm/Turbo workflows, consolidating conflicting frontend implementations, and re-enabling reproducible lint/typecheck/test execution without introducing architectural redesigns or unnecessary abstractions.
Key goals achieved:
The implementation intentionally remains surgical and PR-scoped to avoid broad system rewrites while preserving existing retry/tracing behavior.
Related Issues
Architecture and Implementation Details
kindschema definitions inpackages/contracts/src/index.tspackages/core/src/lib/runtime.tspackages/core/src/lib/runtime.test.tsApp.tsximplementations into a single stable runtime console UIpackage-lock.jsonto preserve pnpm workspace consistencyBreaking Changes
This PR does not intentionally introduce API, telemetry, or configuration breaking changes.
Testing Methodology
Executed:
pnpm installpnpm typecheckpnpm lintpnpm testManually validated:
Verified:
Performance & Observability Impact
This PR primarily improves runtime stability and observability reliability rather than introducing new telemetry features.
Impact includes:
No significant memory overhead or telemetry schema changes were introduced.
Contributor Checklist