Skip to content

Rust-hybrid pre-release: TS/JS and Go Agent Sufficiency refresh #279

Description

@jununfly

This was generated by AI during triage.

Parent

What to build

Refresh README-backed Agent Sufficiency claims with current rust-hybrid evidence for one TS/JS representative and one Go representative. This is release-claim hygiene, not #165 performance optimization. Do not use deterministic smoke as a substitute for agent A/B metrics.

Default representatives are Excalidraw for TS/JS and Gin for Go unless current corpus availability requires an explicit documented substitution.

Acceptance criteria

  • TS/JS representative repo is selected and recorded, defaulting to Excalidraw.
  • Go representative repo is selected and recorded, defaulting to Gin.
  • Each repo runs 2 flow prompts.
  • Each prompt runs 2 runs per arm, WITH ZCodeGraph vs WITHOUT ZCodeGraph.
  • Read/Grep fallback, tool calls, wall time, and cost/tokens when available are recorded.
  • Corpus commits, corpus paths, ZCodeGraph commit, runner version/context, and unavailable reasons are recorded.
  • README metrics are replaced only for claims covered by this evidence.
  • If agent A/B cannot run, evidence records the unavailable reason and README metric replacement is blocked rather than invented.
  • Full 7-repo scoreboard is not run.
  • Evidence is written under docs/benchmarks/.

Blocked by

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