docs: spec-review wrap-up routing — inbox-route supersedes direct-move

Reviewed the approved wrap-up routing spec; rubric Not ready, two blocking findings. The central one: route keepers via the existing inbox-send path to the destination's inbox and let its own process-inbox file them, rather than the spec's new atomic cross-repo todo.org move. inbox-send already provides the provenance the direct-move design reinvents, the destination files through its own value gate, and a verified precondition (chime and yt-sync have inbox/ but no todo.org) reverses the spec's assumption. Second finding pins the candidate-set marking to a tag stamped at process-inbox file time. Review file carries the analysis and drop-in implementation tasks.

0 files changed, 0 insertions, 0 deletions