is-pulllisted

# Pull Pull brings remote changes into the local ideaspace (fetch → rebase/merge). It is one direction across the agreement boundary — it never pushes your work out. ## Rule - **Integrating rewrites the tree** — it needs a committed, clean tree. Uncaptured or uncommitted changes? Capture first, or ask whether to leave them local. - **Missing auth?** Use `is_auth` only when pull reports credentials are needed. ## How 1. Inspect state with `is_status`. 2. Preview when useful: `is_pull({ dry_run: true })`. 3. If staged captures are uncommitted or the tree is dirty, do not pull yet — commit first (`is_commit`). 4. If the plan is safe, run `is_pull`. 5. Report what integrated, or why nothing changed. ## Watch for - No upstream/remote: suggest **is-publish** if the user wants to host this space remotely. - Conflicts during integrate: pull surfaces how to back out (abort, resolve, retry). - Auth failure: offer `is_auth action="login"`, then retry pull. ## After pull If new remote understanding landed, consider **is-reflect**: does Now, Purpose, or the local agreement still match reality?