Skip to content

Phase 4: make Rust indexing RSS and profile evidence repeatable #78

Description

@jununfly

This was generated by AI during triage.

What to build

Make Phase 4 Rust indexing profile evidence repeatable enough to support rollout-readiness decisions. The profiler or validation harness should compare TypeScript and Rust indexing on the hard-gate repositories and report wall-clock, peak RSS, finalization subphases, toolchain metadata, and explicit RSS unavailable reasons.

Acceptance criteria

  • TypeScript and Rust profile output includes wall-clock time, peak RSS, source scanning, parsing/extraction, SQLite writing, subprocess handoff, and TypeScript finalization subphases.
  • RSS output is valid on at least one supported platform, and unavailable RSS includes a machine-readable reason rather than an unexplained null.
  • Profile artifacts include repository commit, indexed file count, CLI version, Rust core version, Node version, OS, and architecture.
  • Baseline profiles are recorded for ZCodeGraph, Excalidraw, and Zustand.
  • Automated tests cover profile JSON shape, RSS unavailable reasons, and artifact/summary layout.
  • Benchmark/profile evidence is recorded in Phase 4 results artifacts or a document that points to the raw artifacts.

Blocked by

None - can start immediately

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions