is-spacelisted

# Working in an Ideaspace Canonical protocols: read `${CLAUDE_PLUGIN_ROOT}/reference/guide.md`, `${CLAUDE_PLUGIN_ROOT}/reference/capture.md`, `${CLAUDE_PLUGIN_ROOT}/reference/writing.md`, or `${CLAUDE_PLUGIN_ROOT}/reference/awareness.md` when the task needs the full shared standard. This entrypoint adds Claude-specific navigation and tool guidance. An ideaspace is inhabited through a simple loop: ```text arrive → orient → inspect → act → capture → push/pull → reflect ``` The plugin handles **arrive** automatically with SessionStart awareness. For active work, pick the intent skill by tier: - **Daily loop** — `is-orient`, `is-capture`, `is-push` / `is-pull`, `is-reflect`. - **Access** — `is-share` for people, teams, and public/private visibility. - **Space lifecycle** — `is-setup`, `is-publish`, `is-shape`. - **Reference** — `is-space`, `is-writing`. You have two working surfaces: - **Skills** — agent procedures for user intent. Use these first. - **Tools** — low-level primitives (`is_navigate`, `is_status`, `is_write`, `is_commit`, `is_push`, `is_pull`, `is_auth`). Skills choose the mechanism; don't make backend choice the user's problem. Native `Read`, `Glob`, `Grep`, `Edit`, `Write`, and `Bash` remain the default for navigation, search, source-code work, and ordinary doc edits. ## Start here **No `_agent/` yet?** Suggest `/is-setup` — it walks the user through the contract scaffold and conversational seeding. **Returning?** The SessionStart hook surfaces what's p