Extract method crate to its own repo

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/cool-ideas/PLATFORM_method-crate-extract.md
Original lane: cool-ideas
Original legend: PLATFORM

Original backlog card

Extract method crate to its own repo

Status: active cool idea. Echo has a Rust crates/method library with no Echo
dependencies and a working cargo xtask method status --json command. The
external /Users/james/git/method repo already contains the TypeScript METHOD
CLI/library, drift detector, MCP server, and tests. What remains is deciding
whether the Rust crate should be extracted into that repo, published separately,
or kept as Echo-local compatibility glue.

The crates/method/ library has zero Echo dependencies. It could
live in ~/git/method/ alongside the existing TS CLI and serve
both Rust and JS projects. The TS CLI and Rust crate would share
the same METHOD doctrine but implement it in their native ecosystems.

[coderabbitai]

🔗 Related PRs

flyingrobots/echo#373 - chore: remove legacy ttd-browser surface [merged]
flyingrobots/echo#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]
flyingrobots/echo#388 - docs(method): add backlog cards and hook failure note [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!