Back to corpus
technical noteexperiment writeup candidatescore 36
DEP Audit V2 — Trajectory Search
**Date**: 2025-07-14 **Version**: 0.2.0 (changelog says 0.3.0 unreleased) **Stack**: Tauri v2 + React 19 + TypeScript 5.9 + Vite 7 **Scale**: 293 source files, ~42,253 lines TypeScript frontend, ~6,839 lines Rust backend
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Date**: 2025-07-14 **Version**: 0.2.0 (changelog says 0.3.0 unreleased) **Stack**: Tauri v2 + React 19 + TypeScript 5.9 + Vite 7 **Scale**: 293 source files, ~42,253 lines TypeScript frontend, ~6,839 lines Rust backend
Trajectory Search is an extraordinarily ambitious application that attempts to be a universal desktop UI for the entire CompCore/OpenClaw ecosystem. The breadth of features is impressive — 20+ views, motion choreography, 3D visualization, AI agent orchestration, calendar, notes, dream generation, research browser, terminal emulation, and more. But the codebase has outpaced its ability to compile, test, or ship. It's a prototype masquerading as a product.
### TypeScript Strictness - `strict: true` ✅ — good - `noUnusedLocals: true` ✅ — enforced but violated 70+ times - `noUnusedParameters: true` ✅ — enforced but violated - `erasableSyntaxOnly: true` ✅ — blocks enum syntax in 2 files - `verbatimModuleSyntax: true` ✅
The tsconfig is strict, which is the right call. But the codebase doesn't comply with its own config. **156 TypeScript errors** currently (up from 127 in the handoff doc — regression).
### Error Breakdown | Category | Count | Severity | |----------|-------|----------| | Missing type properties (TS2739) | ~30 | Medium — test fixtures & conflict detector | | Property doesn't exist (TS2339) | ~15 | Medium — type drift | | Unused variables (TS6133) | ~25 | Low — cleanup | | Type assignment mismatch (TS2322) | ~12 | Medium — string/number confusion | | Unused type declarations (TS6196) | ~8 | Low | | Argument type mismatch (TS2345) | ~15 | Medium — ConflictResolutionSuggestion | | Missing exports (TS2305) | ~3 | Medium — LatentState/MotionDescriptor | | erasableSyntaxOnly (TS1294) | 2 | Low — pulse enum syntax | | Implicit any (TS7053) | ~3 | Medium | | Other | ~43 | Mixed |
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.