You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Legacy commands such as cargo xtask method inbox, matrix, dag, frontier, critical-path, and check-dag still describe or operate on the old filesystem backlog model.
cargo xtask method status now 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
Fresh clones do not require a fake/empty backlog directory solely to satisfy Method workspace discovery.
cargo xtask method status does not present the empty legacy filesystem backlog as the live tracker.
Legacy filesystem commands are removed, explicitly deprecated, or redirected to GitHub Issues guidance.
Docs and command help agree that GitHub Issues are the live tracker.
Existing design/retro/legend docs remain discoverable without resurrecting live docs/method/backlog/** cards.
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