v0.21.2.0 fix(remote): self-heal unregistered remote projects after Add Project

[avinashjoshi]

Summary

Closes the trap where adding a remote project from the TUI looked successful but attaching to its (main) row errored with project not registered for that host — and the suggested recovery command used a flag the CLI doesn't accept.

Wire protocol

• canopy ls --json emits a new per-row project_root field (absolute path on the host). Additive; pre-v0.21.2 laptops parse and ignore.

Self-heal

• refreshRemoteCmd now calls autoRegisterRemoteOrphans on every tick. For each (host, project) pair the remote sent a project_root for and the laptop's hosts.json doesn't have, validate the path against the same safety contract as the v0.20 result-file channel and reg.AddProject it. Idempotent. No-op when the remote is too old to send the field.

Surface failures, don't swallow them

• registerRemoteAddProject returns the reason it couldn't auto-register instead of dropping it into ~/.canopy/log/canopy.log. The success toast renders ⚠ <reason> with the literal manual-recovery command and stretches from 3 s to 8 s so the user can copy it.

Correct the broken hint

• update_attach.go:211 was suggesting canopy project add --host tower <path>, but canopy project add accepts --on, not --host. Fixed flag and arg order.

Test Coverage

Six regression tests in internal/ui/remote_project_recovery_test.go:

• TestAttachRemoteRow_NotRegisteredErrorWording — asserts --on and correct arg order
• TestShowAddProjectToast_WarningRendersInToast — toast carries warning + extended expiry
• TestAutoRegisterRemoteOrphans_RegistersUnknownProject — happy path + dedup + on-disk persistence
• TestAutoRegisterRemoteOrphans_SkipsEmptyProjectRoot — older-remote graceful degradation
• TestAutoRegisterRemoteOrphans_RejectsInvalidPath — relative paths and control chars rejected
• TestAutoRegisterRemoteOrphans_SkipsFailedHost — errored hosts don't poison the registry

All paths in the diff have direct test coverage. go test ./... and go test -tags=e2e ./... both pass.

Caveat

The self-heal needs the remote canopy to also be on v0.21.2+ (so it emits project_root). For users whose remote is still pre-v0.21.2, the corrected attach error message gives them a copy-pasteable manual recovery command.

Test plan

• go test ./... passes
• go test -tags=e2e ./... passes
• go build ./... clean
• Manual: add a project on a v0.21.2 tower → row attaches without manual register
• Manual: add a project on a pre-v0.21.2 remote → toast shows the warning + manual command

🤖 Generated with Claude Code