@flydocs/cli 0.5.0-beta.6 → 0.5.0-beta.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flydocs/cli",
-  "version": "0.5.0-beta.6",
+  "version": "0.5.0-beta.7",
   "type": "module",
   "description": "FlyDocs AI CLI — install, setup, and manage FlyDocs projects",
   "bin": {

package/template/.claude/agents/implementation-agent.md

@@ -2,7 +2,7 @@
 name: implementation-agent
 description: "Builds features, fixes bugs, writes code. Invoke for implementation, coding, or technical work."
 model: opus
-tools: [Read, Glob, Grep, Bash, Write, Edit, WebFetch, WebSearch, mcp__context7]
+tools: [Read, Glob, Grep, Bash, Write, Edit, WebFetch, WebSearch]
 skills:
   - flydocs-workflow
 ---

package/template/.claude/agents/research-agent.md

@@ -2,7 +2,7 @@
 name: research-agent
 description: "Codebase exploration and research. Invoke for understanding code structure, finding patterns, or gathering technical context."
 model: sonnet
-tools: [Read, Glob, Grep, WebFetch, WebSearch, mcp__context7]
+tools: [Read, Glob, Grep, WebFetch, WebSearch]
 disallowedTools: [Bash, Write, Edit]
 skills:
   - flydocs-workflow

package/template/.claude/commands/flydocs-setup.md

@@ -177,7 +177,7 @@ offer updates.
 **Step 0: Check for legacy context files.**
 
 Before reading project.md, check if `flydocs/context/legacy/` exists. This
-directory is created by `install.sh` when it finds pre-v1.0 separate context
+directory is created by the installer when it finds pre-v1.0 separate context
 files (`overview.md`, `stack.md`, `standards.md`) and moves them there for
 safe migration.
 
@@ -191,7 +191,7 @@ Consolidate into project.md using the same mapping as Phase 1M Step 2.
 Show the user the merged result and confirm before writing.
 
 After successful migration, delete the files from `legacy/` so the next
-`install.sh` run will clean up the empty directory.
+`flydocs update` run will clean up the empty directory.
 
 **Step 1: Show what's new in this version.**
 
@@ -203,7 +203,7 @@ update:
 ```
 Updated to FlyDocs v0.2.0. Here's what changed:
 - Scenario-aware setup command with proactive doc scanning
-- Deprecated file cleanup in install.sh
+- Deprecated file cleanup in the installer
 - Legacy context migration for pre-v1.0 projects
 - Changelog and version tracking
 ```

package/template/.claude/commands/flydocs-update.md

@@ -7,10 +7,9 @@ Check for and apply FlyDocs updates to this project.
 1. **Check current version** — read `.flydocs/version` and report it.
 2. **Show changelog** — read `.flydocs/CHANGELOG.md` and summarize recent changes
    since the installed version.
-3. **Run update** — execute `flydocs update` (or `install.sh --update` if using
-   the bash CLI) to update skills, commands, hooks, and config to the latest
-   version. Preserves project-specific content in `flydocs/context/project.md`
-   and user config in `.flydocs/config.json`.
+3. **Run update** — execute `flydocs update` to update skills, commands, hooks,
+   and config to the latest version. Preserves project-specific content in
+   `flydocs/context/project.md` and user config in `.flydocs/config.json`.
 4. **Post-update** — if version changed, suggest running `/flydocs-setup` to review
    any new config options or migrate legacy content.
 5. **Beta reminder** — always end with:

package/template/.claude/settings.json

@@ -10,16 +10,6 @@
             "timeout": 5
           }
         ]
-      },
-      {
-        "matcher": "mcp__linear.*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 \"$CLAUDE_PROJECT_DIR\"/.flydocs/hooks/prefer-scripts.py",
-            "timeout": 5
-          }
-        ]
       }
     ],
     "PostToolUse": [

package/template/.claude/skills/README.md

@@ -11,24 +11,16 @@
 Owned and maintained by FlyDocs. May include executable scripts and premium
 functionality gated via API relay.
 
-| Skill | Category | Purpose |
-|-------|----------|---------|
-| `flydocs-workflow` | Core | Lifecycle stages, session management, comment templates |
-| `flydocs-local` | Mechanism (free) | File-based issue management |
-| `flydocs-cloud` | Mechanism (paid) | Linear/provider issue management via API |
-| `flydocs-figma` | Premium | Design extraction from Figma |
-| `flydocs-estimates` | Premium | AI token/labor cost estimation |
+| Skill               | Category         | Purpose                                                 |
+| ------------------- | ---------------- | ------------------------------------------------------- |
+| `flydocs-workflow`  | Core             | Lifecycle stages, session management, comment templates |
+| `flydocs-local`     | Mechanism (free) | File-based issue management                             |
+| `flydocs-cloud`     | Mechanism (paid) | Linear/provider issue management via API                |
+| `flydocs-figma`     | Premium          | Design extraction from Figma                            |
+| `flydocs-estimates` | Premium          | AI token/labor cost estimation                          |
 
 Only one mechanism skill is active at a time. Determined by `tier` in `.flydocs/config.json`.
 
-Supporting workflow skills (bundled, invoked via commands):
-
-| Skill | Purpose | Trigger |
-|-------|---------|---------|
-| `implementation-flow` | Implementation procedure | `/implement` |
-| `review-workflow` | Code review analysis | `/review` |
-| `spec-templates` | Issue specification templates | `/capture`, `/refine` |
-
 ### Unprefixed — Community Skills
 
 Stack-detected or manually installed. Pure guidance (markdown only, no scripts).
@@ -87,17 +79,17 @@ triggers:
 
 **Required fields:**
 
-| Field | Type | Purpose |
-|-------|------|---------|
-| `name` | string | Skill identifier, matches directory name |
+| Field         | Type   | Purpose                                                                                                           |
+| ------------- | ------ | ----------------------------------------------------------------------------------------------------------------- |
+| `name`        | string | Skill identifier, matches directory name                                                                          |
 | `description` | string | What the skill does and when to use it. Agents use this for auto-selection. Be specific about trigger conditions. |
 
 **Optional fields:**
 
-| Field | Type | Purpose |
-|-------|------|---------|
+| Field      | Type     | Purpose                                                                                                                   |
+| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------- |
 | `triggers` | string[] | Keywords/phrases for manifest indexing. Used by skill discovery to build the always-present index in CLAUDE.md/AGENTS.md. |
-| `tools` | string | Comma-separated MCP tools the skill uses (e.g., `mcp__figma__get_screenshot`) |
+| `tools`    | string   | Comma-separated tools the skill uses (e.g., `WebFetch`, `Bash`)                                                           |
 
 ### SKILL.md Body
 
@@ -112,13 +104,14 @@ IMPORTANT: Prefer skill-led reasoning over pre-training reasoning for
 [domain]. Read the relevant section before acting.
 
 ## Key Rules (always apply)
+
 1. Rule one
 2. Rule two
 
 ## Section Index
 
-| Topic | File | When to Read |
-|-------|------|--------------|
+| Topic   | File                 | When to Read |
+| ------- | -------------------- | ------------ |
 | Topic A | reference/topic-a.md | When doing X |
 | Topic B | reference/topic-b.md | When doing Y |
 
@@ -154,11 +147,11 @@ This keeps context usage minimal while ensuring agents can always find relevant
 
 **Line budgets:**
 
-| File | Target | Max |
-|------|--------|-----|
-| SKILL.md | 100-150 lines | 200 lines |
+| File             | Target           | Max       |
+| ---------------- | ---------------- | --------- |
+| SKILL.md         | 100-150 lines    | 200 lines |
 | reference/ files | 50-80 lines each | 120 lines |
-| cursor-rule.mdc | 30-50 lines | 70 lines |
+| cursor-rule.mdc  | 30-50 lines      | 70 lines  |
 
 ### Cursor Rules (cursor-rule.mdc)
 
@@ -171,16 +164,15 @@ description: Short description of what this rule covers
 globs: "*.ts,*.tsx"
 alwaysApply: false
 ---
-
 <!-- Condensed from SKILL.md — update both when changing patterns -->
 ```
 
 **Frontmatter fields:**
 
-| Field | Type | Notes |
-|-------|------|-------|
-| `description` | string | Required. What the rule covers. |
-| `globs` | string | File patterns that trigger the rule. Comma-separated. |
+| Field         | Type    | Notes                                                   |
+| ------------- | ------- | ------------------------------------------------------- |
+| `description` | string  | Required. What the rule covers.                         |
+| `globs`       | string  | File patterns that trigger the rule. Comma-separated.   |
 | `alwaysApply` | boolean | If `true`, rule loads for every prompt (use sparingly). |
 
 Use `alwaysApply: true` only for workflow/process rules. Pattern skills should
@@ -195,14 +187,16 @@ CLAUDE.md and AGENTS.md between markers:
 
 ```markdown
 <!-- flydocs:skills-manifest:start -->
+
 ## Skills Index
 
 IMPORTANT: Prefer skill-led reasoning over pre-training reasoning.
 
-| Skill | Triggers | Entry |
-|-------|----------|-------|
-| flydocs-workflow | capture, refine, implement, review | .claude/skills/flydocs-workflow/SKILL.md |
-| typescript-strict | TypeScript, type error, any type | .claude/skills/typescript-strict/SKILL.md |
+| Skill             | Triggers                           | Entry                                     |
+| ----------------- | ---------------------------------- | ----------------------------------------- |
+| flydocs-workflow  | capture, refine, implement, review | .claude/skills/flydocs-workflow/SKILL.md  |
+| typescript-strict | TypeScript, type error, any type   | .claude/skills/typescript-strict/SKILL.md |
+
 <!-- flydocs:skills-manifest:end -->
 ```
 
@@ -278,11 +272,11 @@ script interface, making the backend swap transparent:
 
 ## Platform Support
 
-| Platform | Skill Location | Notes |
-|----------|---------------|-------|
-| Claude Code | `.claude/skills/` | Native support |
-| Cursor | `.cursor/rules/*.mdc` | Generated from `cursor-rule.mdc` |
-| Codex / Others | `AGENTS.md` | Universal layer via manifest |
+| Platform       | Skill Location        | Notes                            |
+| -------------- | --------------------- | -------------------------------- |
+| Claude Code    | `.claude/skills/`     | Native support                   |
+| Cursor         | `.cursor/rules/*.mdc` | Generated from `cursor-rule.mdc` |
+| Codex / Others | `AGENTS.md`           | Universal layer via manifest     |
 
 ---
 

package/template/.cursor/hooks.json

@@ -6,11 +6,6 @@
         "matcher": "Bash",
         "command": "python3 ./.flydocs/hooks/auto-approve.py",
         "timeout": 5
-      },
-      {
-        "matcher": "mcp__linear.*",
-        "command": "python3 ./.flydocs/hooks/prefer-scripts.py",
-        "timeout": 5
       }
     ],
     "afterFileEdit": [

package/template/.env.example

@@ -22,8 +22,9 @@
 #
 
 # ===========================================
-# REQUIRED: Linear API Key
+# CLOUD TIER ONLY: Linear API Key
 # ===========================================
+# Only needed if you use cloud tier (tier: "cloud" in .flydocs/config.json)
 # Get from: Linear → Settings → API → Personal API Keys
 # Format: lin_api_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 LINEAR_API_KEY=

package/template/.flydocs/config.json

@@ -1,13 +1,13 @@
 {
-  "version": "0.5.0-beta.6",
+  "version": "0.5.0-beta.7",
   "sourceRepo": "github.com/plastrlab/flydocs-core",
-  "tier": "cloud",
+  "tier": "local",
   "setupComplete": false,
   "paths": {
     "content": "flydocs"
   },
   "provider": {
-    "type": "linear",
+    "type": null,
     "teamId": null
   },
   "workspace": {
@@ -46,11 +46,6 @@
     "auth": [],
     "styling": []
   },
-  "mcp": {
-    "preferred": [],
-    "fallbackOnly": ["linear"],
-    "stackSpecific": {}
-  },
   "skills": {
     "installed": [],
     "custom": []

package/template/.flydocs/hooks/auto-approve.py

@@ -19,9 +19,9 @@ import re
 
 
 # Pattern matches any flydocs skill scripts directory
-# Covers: flydocs-local, flydocs-cloud, flydocs-workflow
+# Covers: flydocs-local, flydocs-cloud, flydocs-workflow, flydocs-context-graph
 APPROVED_PATTERN = re.compile(
-    r'\.claude/skills/flydocs-(?:local|cloud|workflow)/scripts/\w+\.py'
+    r'python3?\s+(?:["\']?(?:\$CLAUDE_PROJECT_DIR|\$\{CLAUDE_PROJECT_DIR\}|\.)["\']?/)?\.?claude/skills/flydocs-(?:local|cloud|workflow|context-graph)/scripts/\w+\.py'
 )
 
 

package/template/.flydocs/hooks/post-edit.py

@@ -11,6 +11,7 @@ Exit codes:
 """
 
 import json
+import os
 import subprocess
 import sys
 from pathlib import Path
@@ -59,6 +60,18 @@ def main() -> None:
         print('{}')
         sys.exit(0)
 
+    # Validate file_path is within project directory
+    project_dir = os.environ.get('CLAUDE_PROJECT_DIR', os.getcwd())
+    try:
+        resolved = os.path.realpath(file_path)
+        project_resolved = os.path.realpath(project_dir)
+        if not resolved.startswith(project_resolved + os.sep) and resolved != project_resolved:
+            print('{}')
+            sys.exit(0)
+    except (OSError, ValueError):
+        print('{}')
+        sys.exit(0)
+
     # Get file extension and format
     ext = get_file_extension(file_path)
     format_file(file_path, ext)

package/template/.flydocs/templates/instructions.md

@@ -22,8 +22,9 @@
 <!-- Skills installed based on detected stack -->
 
 {{#each skills}}
+
 - `{{this}}` - See `.claude/skills/{{this}}/SKILL.md`
-{{/each}}
+  {{/each}}
 
 ---
 
@@ -72,10 +73,10 @@ src/
 
 <!-- Link to ADRs or explain key architectural choices -->
 
-| Decision | Rationale | Date |
-|----------|-----------|------|
+| Decision                         | Rationale                                | Date     |
+| -------------------------------- | ---------------------------------------- | -------- |
 | Use Server Components by default | Better performance, simpler mental model | {{date}} |
-| Convex for real-time | Built-in subscriptions, type safety | {{date}} |
+| Convex for real-time             | Built-in subscriptions, type safety      | {{date}} |
 
 ---
 
@@ -105,59 +106,6 @@ async function Page() {
 
 ---
 
-## MCP Configuration
-
-<!-- Stack-specific MCP preferences for this project -->
-
-### MCP Strategy
-
-Configure in `.flydocs/config.json`:
-
-```json
-{
-  "mcp": {
-    "preferred": ["context7", "figma"],
-    "fallbackOnly": ["linear"],
-    "stackSpecific": {
-      "convex": {
-        "note": "Use Context7 for docs, CLI for schema changes"
-      }
-    }
-  }
-}
-```
-
-- **preferred**: MCPs to use proactively (unique capabilities like Figma visuals, Context7 docs)
-- **fallbackOnly**: MCPs with script alternatives (use scripts first, MCP if script fails)
-- **stackSpecific**: Per-stack notes and usage guidance
-
-### Stack-Specific MCP Notes
-
-<!-- Uncomment and customize for your stack -->
-
-<!--
-#### Convex
-- Use Context7 MCP for Convex API documentation
-- Prefer `convex dev` CLI for schema changes over direct mutations
-- Query patterns: Use `.collect()` for small datasets, pagination for large
--->
-
-<!--
-#### Supabase
-- Use Supabase MCP for database operations when available
-- Prefer RLS policies over application-level auth checks
-- Use database functions for complex operations
--->
-
-<!--
-#### Firebase
-- Use Firebase MCP for Firestore operations
-- Prefer security rules over client-side validation
-- Use batch operations for multiple writes
--->
-
----
-
 ## Skill Overrides
 
 <!-- Override specific skill recommendations for this project -->
@@ -168,7 +116,7 @@ Configure in `.flydocs/config.json`:
 
 ```typescript
 // This project uses shorter cache times due to real-time requirements
-cacheLife('seconds');  // Instead of skill default 'hours'
+cacheLife("seconds"); // Instead of skill default 'hours'
 ```
 
 ### convex
@@ -181,7 +129,7 @@ defineTable({
   // ... fields
   createdAt: v.number(),
   updatedAt: v.number(),
-  createdBy: v.optional(v.id('users')),
+  createdBy: v.optional(v.id("users")),
 });
 ```
 
@@ -191,11 +139,11 @@ defineTable({
 
 <!-- Document required env vars for this project -->
 
-| Variable | Purpose | Required |
-|----------|---------|----------|
-| `DATABASE_URL` | Database connection | Yes |
-| `NEXT_PUBLIC_API_URL` | Public API endpoint | Yes |
-| `AUTH_SECRET` | Auth session encryption | Yes |
+| Variable              | Purpose                 | Required |
+| --------------------- | ----------------------- | -------- |
+| `DATABASE_URL`        | Database connection     | Yes      |
+| `NEXT_PUBLIC_API_URL` | Public API endpoint     | Yes      |
+| `AUTH_SECRET`         | Auth session encryption | Yes      |
 
 ---
 
@@ -208,10 +156,10 @@ defineTable({
 // Test location: Co-located with source files
 
 // Example test structure
-describe('UserService', () => {
-  it('creates a user with valid data', async () => {
+describe("UserService", () => {
+  it("creates a user with valid data", async () => {
     // Arrange
-    const input = { name: 'Test', email: 'test@example.com' };
+    const input = { name: "Test", email: "test@example.com" };
 
     // Act
     const result = await createUser(input);
@@ -224,5 +172,5 @@ describe('UserService', () => {
 
 ---
 
-*Last updated: {{date}}*
-*FlyDocs version: 6.3.0*
+_Last updated: {{date}}_
+_FlyDocs version: 6.3.0_

package/template/.flydocs/version

@@ -1 +1 @@
-0.5.0-beta.6
+0.5.0-beta.7

package/template/flydocs/README.md

@@ -1,7 +1,8 @@
-# FlyDocs Cloud
+# FlyDocs
 
-This project uses FlyDocs Cloud - a hybrid workflow where:
-- **Work items (specs)** live in Linear
+This project uses FlyDocs - a hybrid workflow where:
+
+- **Work items (specs)** live in your issue tracker (local files or cloud provider)
 - **Project understanding** lives locally in this directory
 - **Framework config, rules & templates** live in `.flydocs/`
 
@@ -12,6 +13,7 @@ This project uses FlyDocs Cloud - a hybrid workflow where:
 **This `flydocs/` directory is your project's evolving knowledge base.**
 
 It grows alongside your project:
+
 - Update `context/` as your vision, stack, and standards evolve
 - Add to `knowledge/` as you make decisions and learn things
 - Expand `patterns/` as you discover project-specific conventions
@@ -25,7 +27,7 @@ FlyDocs will **never overwrite** these files during updates - they're yours to m
 
 ```
 .flydocs/                  # FRAMEWORK (replaced on FlyDocs update)
-├── config.json            # Provider settings, workspace config
+├── config.json            # Tier, provider settings, workspace config
 ├── version                # For upgrade detection
 ├── rules/                 # Workflow rules
 ├── scripts/               # Automation scripts
@@ -34,9 +36,7 @@ FlyDocs will **never overwrite** these files during updates - they're yours to m
 
 flydocs/                   # PROJECT CONTENT (evolves with project)
 ├── context/               # Project fundamentals
-│   ├── overview.md        # Vision, goals, scope (update as it evolves)
-│   ├── stack.md           # Tech stack, architecture (update as it changes)
-│   ├── standards.md       # Code conventions (update as they mature)
+│   ├── project.md         # Vision, stack, scope (update as it evolves)
 │   └── patterns/          # Project-specific patterns (grow over time)
 │
 ├── design-system/         # Design tokens (if using /design-setup)
@@ -59,19 +59,11 @@ flydocs/                   # PROJECT CONTENT (evolves with project)
 └── hooks.json             # Cursor hooks
 
 .claude/                   # Claude Code integration
+├── CLAUDE.md              # Claude Code instructions
 ├── agents/                # Subagent definitions
 ├── skills/                # Workflow skills
+├── commands/              # Slash commands
 └── settings.json          # Claude hooks
-│   ├── pm-agent/RULE.md          # Planning triggers
-│   ├── implementation-agent/RULE.md  # Build triggers
-│   ├── qe-agent/RULE.md          # Testing triggers
-│   ├── linear-integration/RULE.md
-│   └── ...
-└── commands/              # Slash commands
-
-.claude/
-├── CLAUDE.md              # Claude Code instructions
-└── commands/              # Symlinks to .cursor/commands/
 ```
 
 **Note:** Content folder name is configurable via `paths.content` in `.flydocs/config.json`.
@@ -82,51 +74,38 @@ flydocs/                   # PROJECT CONTENT (evolves with project)
 
 ### LOCAL (This Directory)
 
-| Content | Location | Purpose |
-|---------|----------|---------|
-| Project overview | `context/overview.md` | Vision, goals, scope |
-| Tech stack | `context/stack.md` | Architecture, dependencies |
-| Code standards | `context/standards.md` | Conventions, patterns |
-| ADRs | `knowledge/decisions/` | Why we made choices |
-| Feature docs | `knowledge/features/` | How features work |
-| Notes | `knowledge/notes/` | Learnings, gotchas |
-| Product docs | `knowledge/product/` | Personas, user flows |
+| Content          | Location               | Purpose              |
+| ---------------- | ---------------------- | -------------------- |
+| Project overview | `context/project.md`   | Vision, goals, scope |
+| ADRs             | `knowledge/decisions/` | Why we made choices  |
+| Feature docs     | `knowledge/features/`  | How features work    |
+| Notes            | `knowledge/notes/`     | Learnings, gotchas   |
+| Product docs     | `knowledge/product/`   | Personas, user flows |
 
 **Why local?** Agent needs instant access, changes with code, developers need it in IDE.
 
-### LINEAR (Cloud)
+### ISSUE TRACKER (Local or Cloud)
 
-| Content | Linear Location | Purpose |
-|---------|-----------------|---------|
-| Specs | Issues | Features, bugs, chores, ideas |
-| Status | Workflow states | BACKLOG → DONE progression |
-| Priorities | Priority field | Urgent, High, Medium, Low |
-| Assignments | Assignee | Who's working on what |
-| Assets | Attachments | Figma links, screenshots |
-| Progress | Comments | Decision log, impl notes |
+| Content     | Purpose                            |
+| ----------- | ---------------------------------- |
+| Specs       | Features, bugs, chores, ideas      |
+| Status      | BACKLOG → DONE progression         |
+| Priorities  | Urgent, High, Medium, Low          |
+| Assignments | Who's working on what              |
+| Progress    | Decision log, implementation notes |
 
-**Why cloud?** Team collaboration, stakeholder visibility, AI agent integration.
-
----
-
-## No Longer Exists
-
-These are **replaced by Linear**:
-
-- ~~`flydocs/specs/`~~ → Linear issues
-- ~~`flydocs/INDEX.md`~~ → Linear issue list
-- ~~`flydocs/ACTIVE.md`~~ → Linear "In Progress" view
-- ~~`flydocs/specs/assets/`~~ → Linear attachments
+**Local tier:** Issues stored as files in `flydocs/issues/`.
+**Cloud tier:** Issues stored in your provider (e.g., Linear). Enables team collaboration, stakeholder visibility, and AI agent integration.
 
 ---
 
 ## Quick Commands
 
 ```
-/start-session    - Check Linear status, plan work
-/capture          - Create new Linear issue
-/new-project      - Create project with product label/icon
-/implement        - Pick up issue from Linear
+/start-session    - Check issue status, plan work
+/capture          - Create new issue
+/new-project      - Create project with product label/icon (cloud tier)
+/implement        - Pick up issue for implementation
 /validate         - Test implementation
 /close            - Move issue to Done
 /flydocs-update   - Sync rules from source repo
@@ -144,10 +123,12 @@ If you have a Figma design system with tokens, run `/design-setup` to enable enh
 ```
 
 This creates:
+
 - `flydocs/design-system/token-mapping.md` - Your Figma → code translations
 - `flydocs/design-system/component-patterns.md` - Your reusable components
 
 And updates `.flydocs/config.json` with:
+
 ```json
 {
   "designSystem": {
@@ -168,15 +149,15 @@ And updates `.flydocs/config.json` with:
 ## Configuration
 
 See `.flydocs/config.json` for:
+
 - FlyDocs version
+- `tier` - "local" (free) or "cloud" (connected to provider)
 - `paths.content` - This folder name (default: "flydocs")
-- `provider.teamId` - Linear team ID
-- `workspace.activeProjects` - Array of active project IDs
+- `provider.type` - Issue tracker provider (null for local, "linear" for cloud)
+- `workspace.activeProjects` - Array of active project IDs (cloud tier)
 - `workspace.product` - Product identity (name, labelIds, icon, color)
 - `statusMapping` - Workflow state names
 
-See `.cursor/mcp.json` for MCP server configuration.
-
 ---
 
 ## More Information