[Feature]: Restore PulseStack Monorepo Integrity and Runtime Stability for Production-Safe AI Observability

[vraj826]

Problem Statement

PulseStack currently contains multiple advanced-critical issues including broken pnpm/Turbo workspace behavior, merge-corrupted runtime files, duplicated execution logic, invalid shared contracts, failing CI pipelines, and conflicting frontend implementations.

Core runtime and observability components are unstable, preventing deterministic workflow execution, reliable replay behavior, typed API enforcement, and contributor-safe development workflows.

These issues collectively make the platform non-buildable, difficult to maintain, and unsafe for production-scale distributed AI observability.

---

Proposed Solution

Implement a staged monorepo recovery and runtime hardening initiative that:

• restores pnpm/Turbo workspace integrity
• removes merge-corrupted runtime/frontend code
• fixes TypeScript and ESLint pipeline failures
• enforces typed API/runtime contracts
• restores deterministic workflow execution
• introduces safe plugin dispatch isolation
• improves replay/dashboard loading and accessibility states
• hardens observability and distributed runtime behavior

Likely affected areas:

• packages/core
• packages/contracts
• apps/pulse-web
• apps/pulse-runtime
• apps/pulse-gateway
• plugins/*

---

Impact on Observability and Runtime

This enhancement restores PulseStack’s ability to operate as a stable AI-native observability platform by improving:

• distributed trace reliability
• deterministic workflow replay
• runtime telemetry consistency
• event-driven execution safety
• plugin observability isolation
• CI/CD reproducibility
• contributor onboarding experience

---

Alternatives Evaluated

Minimal syntax cleanup

Rejected because it would not address unsafe runtime boundaries, duplicated execution paths, or broken observability contracts.

Full runtime rewrite

Rejected due to excessive migration risk and potential loss of recent retry/tracing improvements.

Removing plugin architecture

Rejected because PulseStack’s extensibility depends on runtime plugins and observability integrations.

---

Technical Requirements & Dependencies

• pnpm + Turbo workspace restoration
• ESLint v9 compatibility migration
• stricter TypeScript validation
• OpenTelemetry compatibility
• Fastify contract validation
• React Query/WebSocket state recovery
• Docker + Helm deployment verification

---

Acceptance Criteria

• pnpm install, pnpm lint, pnpm typecheck, and pnpm test execute successfully
• Merge-corrupted runtime/frontend files are fully resolved
• Runtime execution paths are deterministic and type-safe
• Shared contracts enforce typed API boundaries
• Replay/dashboard UI includes loading, reconnect, and accessibility states
• Plugin dispatch operates in isolated failure-safe boundaries
• Docker Compose and Helm deployments validate successfully

---

Additional Context & Diagrams

Agents / Workflows
        ↓
 Pulse Gateway API
        ↓
 Distributed Event Bus
        ↓
 Runtime Engine + DAG Executor
        ↓
 Observability Pipeline
        ↓
 Replay Engine + UI Console

[vraj826]

Hello Maintainers @NEXARA-oss , I'll like to work on this issue under GSSoC'26, kindly assign this to me!