@jive-ai/cli 0.0.26 → 0.0.31

package/docs/team.md

@@ -1,514 +0,0 @@
-# Team Management Commands
-
-Teams are the organizational unit in Jive. All subagents and MCP servers belong to a team, and team members can collaborate on shared AI resources.
-
-## Overview
-
-Team management in Jive allows you to:
-- Create and manage teams
-- Invite team members
-- Switch between teams in a project
-- View team membership
-
-Each user can be a member of multiple teams, and each project can be associated with one active team at a time.
-
-## Commands
-
-### `jive team create`
-
-Create a new team.
-
-**Usage:**
-```bash
-jive team create
-```
-
-**Requirements:**
-- Must be authenticated (run `jive login` first)
-
-**Interactive Prompts:**
-- **Team name:** Name for the team (minimum 3 characters)
-- **Description:** Optional description of the team's purpose
-
-**Process:**
-1. Prompts for team name and description
-2. Validates team name (minimum 3 characters)
-3. Calls the Jive API to create team (`POST /api/teams`)
-4. Updates credentials if a new API token is issued
-5. Displays success message with team ID
-
-**Output:**
-```
-Team created successfully!
-Team ID: team-abc123
-
-Next step: Initialize Jive in your project
-Run: jive init
-```
-
-**Team Structure:**
-```json
-{
-  "id": "team-abc123",
-  "name": "My Team",
-  "description": "Team for AI development",
-  "createdAt": "2025-01-15T10:30:00.000Z",
-  "members": [
-    {
-      "id": "user-123",
-      "email": "user@example.com",
-      "role": "owner"
-    }
-  ]
-}
-```
-
-**Notes:**
-- You are automatically added as the team owner
-- The team creator has full permissions
-- You can create multiple teams
-
-**Error Conditions:**
-- Not authenticated
-- Team name too short (< 3 characters)
-- Network connectivity issues
-
-**Implementation:** `src/commands/team.ts` (teamCommands.create)
-
----
-
-### `jive team list`
-
-List all teams you're a member of.
-
-**Usage:**
-```bash
-jive team list
-```
-
-**Requirements:**
-- Must be authenticated
-
-**Process:**
-1. Fetches teams from Jive API (`GET /api/teams`)
-2. Displays team information in a formatted list
-3. Highlights the active team (if in a Jive-initialized project)
-
-**Output:**
-```
-Your teams:
-* My Team (team-abc123) [Active]
-  Engineering Team (team-xyz789)
-  Design Team (team-def456)
-```
-
-**Notes:**
-- Green asterisk (*) indicates the active team in the current project
-- "Active" label shows which team is selected for the current project
-- If not in a Jive project, no team is marked as active
-
-**Related Commands:**
-- `jive team switch` - Change the active team
-- `jive init` - Set the active team during project initialization
-
-**Error Conditions:**
-- Not authenticated
-- Network connectivity issues
-- No teams found (displays "You are not a member of any teams")
-
-**Implementation:** `src/commands/team.ts` (teamCommands.list)
-
----
-
-### `jive team switch`
-
-Switch the active team for the current project.
-
-**Usage:**
-```bash
-jive team switch
-```
-
-**Requirements:**
-- Must be authenticated
-- Must be in a Jive-initialized project (`.jive/config.json` exists)
-
-**Interactive Prompts:**
-- **Select a team:** Interactive menu of available teams
-
-**Process:**
-1. Fetches all teams you're a member of
-2. Displays interactive selection menu
-3. Updates `activeTeamId` in `.jive/config.json`
-4. Displays success message
-
-**Output:**
-```
-? Select a team: (Use arrow keys)
-❯ My Team (team-abc123)
-  Engineering Team (team-xyz789)
-  Design Team (team-def456)
-
-Switched to team: My Team
-```
-
-**Configuration Update:**
-
-Before:
-```json
-{
-  "activeTeamId": "team-xyz789",
-  "apiUrl": "https://next.getjive.app"
-}
-```
-
-After:
-```json
-{
-  "activeTeamId": "team-abc123",
-  "apiUrl": "https://next.getjive.app"
-}
-```
-
-**Notes:**
-- Switching teams changes which subagents and MCP servers you're working with
-- The same API authentication token works for all teams
-- You may want to run `jive sync` after switching to pull the new team's resources
-
-**Workflow:**
-```bash
-# Switch to a different team
-jive team switch
-
-# Pull the new team's resources
-jive sync
-
-# Restart Claude Code to apply changes
-```
-
-**Error Conditions:**
-- Not authenticated
-- Project not initialized (no `.jive/config.json`)
-- No teams available
-- User cancels selection
-
-**Implementation:** `src/commands/team.ts` (teamCommands.switch)
-
----
-
-### `jive team invite <email>`
-
-Invite a user to join your team.
-
-**Usage:**
-```bash
-jive team invite <email>
-```
-
-**Arguments:**
-- `<email>` (required) - Email address of the user to invite
-
-**Requirements:**
-- Must be authenticated
-- Must be in a Jive-initialized project
-- Must have permission to invite users (typically team owner/admin)
-
-**Process:**
-1. Gets the active team ID from `.jive/config.json`
-2. Validates email format
-3. Calls the Jive API to send invitation (`POST /api/teams/{teamId}/invite`)
-4. Server sends invitation email to the user
-
-**Output:**
-```
-Invitation sent to user@example.com
-```
-
-**Examples:**
-```bash
-# Invite a user by email
-jive team invite colleague@example.com
-
-# Invite multiple users (run command multiple times)
-jive team invite user1@example.com
-jive team invite user2@example.com
-```
-
-**Invitation Email:**
-
-The invited user receives an email with:
-- Team name and description
-- Invitation link to accept
-- Instructions for joining
-
-**Accepting Invitations:**
-
-Users can accept invitations by:
-1. Clicking the link in the invitation email
-2. Logging in or signing up for Jive
-3. Accepting the team invitation
-
-After accepting:
-- User appears in `jive team list`
-- User can access team resources
-- User can run `jive init` to connect projects to the team
-
-**Notes:**
-- Invitations are sent via email
-- Users must have a Jive account (or create one) to accept
-- There's no limit to the number of team members
-
-**Error Conditions:**
-- Not authenticated
-- Project not initialized
-- Invalid email format
-- User already on the team
-- Network connectivity issues
-- Insufficient permissions
-
-**Implementation:** `src/commands/team.ts` (teamCommands.invite)
-
----
-
-## Team Workflows
-
-### Creating a Team and Onboarding Members
-
-1. **Create the team:**
-   ```bash
-   jive team create
-   ```
-
-2. **Initialize in your project:**
-   ```bash
-   cd my-project
-   jive init
-   ```
-   Select the newly created team when prompted.
-
-3. **Add team resources:**
-   ```bash
-   # Create subagents
-   jive subagents create
-
-   # Add MCP servers
-   jive mcp add my-server
-   ```
-
-4. **Invite team members:**
-   ```bash
-   jive team invite teammate1@example.com
-   jive team invite teammate2@example.com
-   ```
-
-5. **Team members join:**
-   - Accept email invitation
-   - Run `jive login` (or `jive signup` if new)
-   - Run `jive init` in their local project
-   - Select the team
-   - Run `jive sync` to pull resources
-
-### Working Across Multiple Teams
-
-1. **List your teams:**
-   ```bash
-   jive team list
-   ```
-
-2. **Switch teams in a project:**
-   ```bash
-   jive team switch
-   ```
-
-3. **Sync resources:**
-   ```bash
-   jive sync
-   ```
-
-4. **Verify the active team:**
-   ```bash
-   jive status
-   ```
-
-### Managing Team Resources
-
-**View team resources:**
-```bash
-# List team subagents
-jive subagents list
-
-# List team MCP servers
-jive mcp list
-```
-
-**Share resources with the team:**
-```bash
-# Push local subagents
-jive subagents push
-
-# Push local MCP servers
-jive mcp push
-```
-
-**Get resources from the team:**
-```bash
-# Pull team subagents
-jive subagents pull
-
-# Pull team MCP servers
-jive mcp pull
-```
-
-## Team Configuration
-
-### Project-Level Configuration
-
-Each project stores its active team in `.jive/config.json`:
-
-```json
-{
-  "activeTeamId": "team-abc123",
-  "apiUrl": "https://next.getjive.app",
-  "telemetry": {
-    "enabled": true
-  },
-  "lastSync": "2025-01-15T10:30:00.000Z"
-}
-```
-
-**Important:** This file should be in `.gitignore` to prevent committing team IDs to version control.
-
-### User-Level Authentication
-
-Team access is controlled by authentication credentials in `~/.jive/credentials.json`:
-
-```json
-{
-  "token": "auth-token-here",
-  "userId": "user-123",
-  "email": "user@example.com"
-}
-```
-
-The same token provides access to all teams you're a member of.
-
-## Team Permissions
-
-### Roles (Conceptual)
-
-While not fully implemented in the current version, teams typically have:
-
-- **Owner:** Full control, can manage members and settings
-- **Admin:** Can invite members and manage resources
-- **Member:** Can access and contribute to team resources
-
-### Current Behavior
-
-In the current implementation:
-- Team creators have full permissions
-- All team members can access team resources
-- All members can push/pull subagents and MCP servers
-
-## Troubleshooting
-
-### "Project not initialized" Error
-
-**Symptom:** Team commands fail with "Project not initialized in this directory"
-
-**Solution:**
-```bash
-jive init
-```
-
-This creates `.jive/config.json` with the active team ID.
-
-### "Not a member of any teams" Error
-
-**Symptom:** `jive team list` shows no teams
-
-**Solutions:**
-1. Create a team:
-   ```bash
-   jive team create
-   ```
-
-2. Accept an invitation (check email)
-
-3. Verify authentication:
-   ```bash
-   jive login
-   ```
-
-### Wrong Team Selected
-
-**Symptom:** Wrong team's resources are being pulled
-
-**Solutions:**
-1. Check active team:
-   ```bash
-   jive team list
-   ```
-
-2. Switch teams:
-   ```bash
-   jive team switch
-   ```
-
-3. Verify change:
-   ```bash
-   jive status
-   ```
-
-### Cannot Invite Users
-
-**Symptom:** Invitation fails or email not sent
-
-**Solutions:**
-1. Verify you're in a Jive project:
-   ```bash
-   ls .jive/config.json
-   ```
-
-2. Check authentication:
-   ```bash
-   jive doctor
-   ```
-
-3. Verify email format is correct
-
-4. Check network connectivity
-
-## Related Commands
-
-- [`jive init`](./init.md#jive-init) - Initialize project and select team
-- [`jive sync`](./sync.md#jive-sync) - Sync team resources
-- [`jive status`](./sync.md#jive-status) - View active team
-- [`jive doctor`](./init.md#jive-doctor) - Verify team configuration
-
-## API Endpoints
-
-**Team Management:**
-- `POST /api/teams` - Create team
-- `GET /api/teams` - List user's teams
-- `POST /api/teams/{teamId}/invite` - Invite user
-
-**Team Resources:**
-- `GET /api/teams/{teamId}/subagents` - List team subagents
-- `GET /api/teams/{teamId}/mcp-servers` - List team MCP servers
-- `POST /api/teams/{teamId}/subagents` - Create subagent for team
-- `POST /api/teams/{teamId}/mcp-servers` - Create MCP server for team
-
-## Implementation Details
-
-**Source Files:**
-- Main implementation: `src/commands/team.ts`
-- Configuration helpers: `src/lib/config.ts`
-- API client: `src/lib/api-client.ts`
-
-**Key Functions:**
-- `teamCommands.create()` - Creates new team
-- `teamCommands.list()` - Lists user's teams
-- `teamCommands.switch()` - Changes active team
-- `teamCommands.invite()` - Invites user to team
-- `getActiveTeamId()` - Gets team ID from project config
-- `requireProjectConfig()` - Ensures project is initialized