Repository navigation
Retire embedded filesystem METHOD tooling after GitHub Issues migration #528
Copy link
Copy link
Open
Labels
lane:bad-codeMethod lane bad-code.Method lane bad-code.lane:up-nextMethod lane up-next.Method lane up-next.legend:methodMethod legend method.Method legend method.legend:processMethod legend process.Method legend process.priority:mediumMethod priority medium.Method priority medium.release:echo-1.0Echo 1.0 release convergence scopeEcho 1.0 release convergence scopetype:maintenanceMethod work type maintenance.Method work type maintenance.
Milestone
Description
Activity
- addedlane:bad-codeMethod lane bad-code.Method lane bad-code.legend:methodMethod legend method.Method legend method.priority:mediumMethod priority medium.Method priority medium.type:maintenanceMethod work type maintenance.Method work type maintenance.
on Jun 1, 2026 coderabbitai commented
on Jun 1, 2026 coderabbitaiboton Jun 1, 2026 – with coderabbitaiContributorMore actions🔗 Related PRs
#184 - Docs: align roadmap with milestone tracks (closes
#183) [merged]
#309 - feat: add Doghouse PR flight recorder [merged]
#373 - chore: remove legacy ttd-browser surface [merged]
#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]
#388 - docs(method): add backlog cards and hook failure note [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand 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!
- addedlane:up-nextMethod lane up-next.Method lane up-next.legend:processMethod legend process.Method legend process.
on Jun 1, 2026 - added a parent issue
on Jun 20, 2026 - addedrelease:echo-1.0Echo 1.0 release convergence scopeEcho 1.0 release convergence scope
on Jun 20, 2026
Metadata
Metadata
Assignees
Labels
lane:bad-codeMethod lane bad-code.Method lane bad-code.lane:up-nextMethod lane up-next.Method lane up-next.legend:methodMethod legend method.Method legend method.legend:processMethod legend process.Method legend process.priority:mediumMethod priority medium.Method priority medium.release:echo-1.0Echo 1.0 release convergence scopeEcho 1.0 release convergence scopetype:maintenanceMethod work type maintenance.Method work type maintenance.
Projects
- StatusShow more project fieldsTodo
Problem
Echo has migrated live Method backlog tracking to GitHub Issues, but the embedded METHOD tooling still assumes the old filesystem backlog exists.
Concrete evidence from the migration:
crates/method/src/workspace.rsstill discovers a workspace by requiringdocs/method/backlog.docs/method/backlog/.gitkeeppurely as a compatibility marker so fresh clones can still run legacycargo xtask method ...commands.cargo xtask method inbox,matrix,dag,frontier,critical-path, andcheck-dagstill describe or operate on the old filesystem backlog model.cargo xtask method statusnow reports zero legacy backlog files after migration, which is expected but misleading if treated as the live tracker.This is bad code because the implementation encodes a retired workflow as a structural workspace invariant. The marker file is acceptable as a short-term bridge, not as architecture.
Desired outcome
Echo either removes the embedded filesystem-backlog METHOD command surface or replaces it with GitHub-Issues-aware behavior.
Acceptance criteria
cargo xtask method statusdoes not present the empty legacy filesystem backlog as the live tracker.docs/method/backlog/**cards.References
c26e3ed505db0b8de4057dc53be2d94426486cf7docs/method/backlog/.gitkeep