@flydocs/cli 0.6.0-alpha.3 → 0.6.0-alpha.5

package/dist/cli.js

@@ -15,7 +15,7 @@ var CLI_VERSION, CLI_NAME, PACKAGE_NAME, POSTHOG_API_KEY;
 var init_constants = __esm({
   "src/lib/constants.ts"() {
     "use strict";
-    CLI_VERSION = "0.6.0-alpha.3";
+    CLI_VERSION = "0.6.0-alpha.5";
     CLI_NAME = "flydocs";
     PACKAGE_NAME = "@flydocs/cli";
     POSTHOG_API_KEY = "phc_v1MSJTQDFkMS90CBh3mxIz3v8bYCCnKU6v1ir6bz0Xn";
@@ -2046,7 +2046,7 @@ var init_install = __esm({
                 {
                   value: "cloud",
                   label: "Cloud (managed)",
-                  hint: "Sync with Linear \u2014 run flydocs connect after install"
+                  hint: "Sync with Linear, Jira, and more"
                 }
               ]
             });
@@ -3519,7 +3519,7 @@ var init_connect = __esm({
         },
         key: {
           type: "string",
-          description: "API key (fdk_ for relay, lin_api_ for direct Linear)"
+          description: "FlyDocs API key (fdk_...)"
         }
       },
       async run({ args }) {
@@ -3548,22 +3548,19 @@ var init_connect = __esm({
         console.log(`  ${pc11.bold("Connect to FlyDocs Cloud")}`);
         console.log();
         console.log(
-          `  ${pc11.dim("FlyDocs API key (fdk_...): Get from your FlyDocs dashboard")}`
-        );
-        console.log(
-          `  ${pc11.dim("Linear API key (lin_api_...): Get from Linear \u2192 Settings \u2192 API")}`
+          `  ${pc11.dim("Get your API key (fdk_...) from your FlyDocs dashboard")}`
         );
         console.log();
         let apiKey = args.key ?? "";
         if (!apiKey) {
           const keyInput = await text3({
             message: "Enter your API key",
-            placeholder: "fdk_... or lin_api_...",
+            placeholder: "fdk_...",
             validate(value) {
               if (!value.trim()) return "API key is required";
               const type = detectKeyType(value.trim());
               if (type === "unknown")
-                return "Key must start with fdk_ (FlyDocs) or lin_api_ (Linear)";
+                return "Key must start with fdk_ (FlyDocs API key)";
               return void 0;
             }
           });
@@ -3575,7 +3572,9 @@ var init_connect = __esm({
         }
         const keyType = detectKeyType(apiKey);
         if (keyType === "unknown") {
-          printError("Unrecognized key format. Expected fdk_ or lin_api_ prefix.");
+          printError(
+            "Unrecognized key format. Expected fdk_ prefix (FlyDocs API key)."
+          );
           process.exit(1);
         }
         printInfo("Validating API key...");
@@ -3617,8 +3616,7 @@ var init_connect = __esm({
         }
         const wasLocal = config.tier === "local";
         config.tier = "cloud";
-        config.provider = config.provider ?? { type: "linear", teamId: null };
-        config.provider.type = "linear";
+        config.provider = config.provider ?? { type: null, teamId: null };
         await writeConfig(targetDir, config);
         printStatus("Config updated to cloud tier");
         if (wasLocal) {
@@ -3706,7 +3704,7 @@ var init_upgrade = __esm({
           );
           console.log();
           console.log(
-            `  Your issues sync with Linear via the cloud mechanism skill.`
+            `  Your issues sync with your provider via the cloud mechanism skill.`
           );
           console.log(
             `  Run ${pc12.cyan("flydocs connect")} to update your connection settings.`
@@ -3719,9 +3717,7 @@ var init_upgrade = __esm({
         console.log(`  You're currently on the ${pc12.yellow("local")} tier.`);
         console.log(`  Upgrade to cloud for:`);
         console.log();
-        console.log(
-          `    ${pc12.cyan("\u2192")} Issue sync with Linear (Jira coming soon)`
-        );
+        console.log(`    ${pc12.cyan("\u2192")} Issue sync with Linear, Jira, and more`);
         console.log(`    ${pc12.cyan("\u2192")} Project milestones and cycle management`);
         console.log(`    ${pc12.cyan("\u2192")} Team assignment and priority tracking`);
         console.log(`    ${pc12.cyan("\u2192")} Project health updates and dashboards`);

package/package.json

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

package/template/.claude/CLAUDE.md

@@ -43,7 +43,7 @@ Issue operations are handled by the installed mechanism skill. Only one is activ
 | Tier              | Skill           | Backend                        |
 | ----------------- | --------------- | ------------------------------ |
 | Local (free)      | `flydocs-local` | File-based (`flydocs/issues/`) |
-| Cloud (connected) | `flydocs-cloud` | Linear GraphQL API             |
+| Cloud (connected) | `flydocs-cloud` | FlyDocs Relay API              |
 
 Read the active mechanism skill's `SKILL.md` for script catalog and calling conventions.
 
@@ -113,13 +113,13 @@ response — session summaries, issue comments, status updates, and plans.
 IMPORTANT: Prefer skill-led reasoning over pre-training reasoning.
 Consult the relevant skill BEFORE writing code or making workflow decisions.
 
-| Skill             | Triggers                                                                                                                | Entry                                     |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
-| flydocs-cloud     | create issue, transition, comment, list issues, assign, update description, update issue, project update, Linear, cloud | .claude/skills/flydocs-cloud/SKILL.md     |
-| flydocs-context7  | context7, library docs, documentation lookup, framework docs, package docs, API reference                               | .claude/skills/flydocs-context7/SKILL.md  |
-| flydocs-estimates | estimate, cost, token usage, API cost, labor estimate, sizing, effort                                                   | .claude/skills/flydocs-estimates/SKILL.md |
-| flydocs-figma     | Figma, design, screenshot, token mapping, component from design, pixel-perfect, design system                           | .claude/skills/flydocs-figma/SKILL.md     |
-| flydocs-local     | create issue, transition, comment, list issues, assign, update description, status summary, local                       | .claude/skills/flydocs-local/SKILL.md     |
-| flydocs-workflow  | capture, refine, activate, implement, review, validate, close, session, workflow, transition, status, issue             | .claude/skills/flydocs-workflow/SKILL.md  |
+| Skill             | Triggers                                                                                                        | Entry                                     |
+| ----------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
+| flydocs-cloud     | create issue, transition, comment, list issues, assign, update description, update issue, project update, cloud | .claude/skills/flydocs-cloud/SKILL.md     |
+| flydocs-context7  | context7, library docs, documentation lookup, framework docs, package docs, API reference                       | .claude/skills/flydocs-context7/SKILL.md  |
+| flydocs-estimates | estimate, cost, token usage, API cost, labor estimate, sizing, effort                                           | .claude/skills/flydocs-estimates/SKILL.md |
+| flydocs-figma     | Figma, design, screenshot, token mapping, component from design, pixel-perfect, design system                   | .claude/skills/flydocs-figma/SKILL.md     |
+| flydocs-local     | create issue, transition, comment, list issues, assign, update description, status summary, local               | .claude/skills/flydocs-local/SKILL.md     |
+| flydocs-workflow  | capture, refine, activate, implement, review, validate, close, session, workflow, transition, status, issue     | .claude/skills/flydocs-workflow/SKILL.md  |
 
 <!-- flydocs:skills-manifest:end -->

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

@@ -326,7 +326,10 @@ python3 .claude/skills/flydocs-cloud/scripts/set_provider.py <provider_type>
 This stores the provider type on the relay (for routing) and updates
 `provider.type` in local config.
 
-**Step 3: Select or create team.**
+**Step 3: Select or create team/project.**
+
+> For Linear, this selects a team. For Jira, this selects a project. The relay
+> normalizes both as "teams" in the API.
 
 If `provider.teamId` in config is null, discover available teams:
 
@@ -335,20 +338,24 @@ python3 .claude/skills/flydocs-cloud/scripts/list_teams.py
 ```
 
 Present the teams to the user as a numbered list showing name and key.
-Add a final option: **"Create a new team"**. If only one team exists,
+Add a final option: **"Create a new team/project"**. If only one team exists,
 confirm it.
 
-If the user selects **"Create a new team"**:
+If the user selects **"Create a new team/project"**:
 
 1. Ask for team name (required) and key (optional — auto-generated if omitted)
-2. Ask if this should be a sub-team under an existing team (show the list
-   again for parent selection, or "None — top-level team")
+2. **Linear only:** Ask if this should be a sub-team under an existing team
+   (show the list again for parent selection, or "None — top-level team").
+   For Jira, skip the parent option — Jira projects do not have a parent
+   hierarchy.
 3. Create via:
 
 ```bash
 python3 .claude/skills/flydocs-cloud/scripts/create_team.py --name "Team Name" [--key KEY] [--parent <parent_team_id>]
 ```
 
+> The `--parent` flag is Linear-only (sub-teams). Omit for Jira.
+
 After selection or creation, store the preference on the relay and in local
 config:
 
@@ -358,8 +365,12 @@ python3 .claude/skills/flydocs-cloud/scripts/set_team.py <team_id>
 
 This stores the team preference server-side (the relay uses it for all
 team-scoped operations) and updates `provider.teamId` in local config.
+For Jira, this sets the active Jira project.
+
+**Step 4: Get or create project (Linear only).**
 
-**Step 4: Get or create project.**
+> **Jira provider:** Skip this step. Jira organizes issues directly within
+> projects (selected in Step 3). There is no secondary project container.
 
 Query existing projects:
 
@@ -409,7 +420,49 @@ python3 .claude/skills/flydocs-cloud/scripts/set_labels.py \
 If the relay returns `LABELS_NOT_FOUND`, show the invalid names and ask the
 user to correct them.
 
-**Step 6: Configure product identity.**
+**Step 6: Configure status mapping.**
+
+Map provider workflow states to FlyDocs statuses. Run auto-mapping first:
+
+```bash
+python3 .claude/skills/flydocs-cloud/scripts/set_status_mapping.py --auto
+```
+
+The relay auto-maps by case-insensitive name matching (e.g., "In Progress"
+maps to `IMPLEMENTING`, "Done" maps to `COMPLETE`, "Backlog" maps to
+`BACKLOG`).
+
+**Review the result:** The response includes `matched` (number of statuses
+successfully mapped) and `total` (total FlyDocs statuses). Show the user
+the `mapping` object:
+
+```
+Status mapping (matched 6/10):
+  BACKLOG      -> Backlog
+  READY        -> Ready
+  IMPLEMENTING -> In Progress
+  REVIEW       -> In Review
+  COMPLETE     -> Done
+  CANCELED     -> Canceled
+```
+
+If `matched < total`, some statuses are unmapped — **warn but don't block**.
+Transitions for unmapped statuses will fall back to provider name matching.
+If the user wants to fix unmapped statuses, fetch available provider states
+and let them map manually:
+
+```bash
+python3 .claude/skills/flydocs-cloud/scripts/list_statuses.py
+```
+
+Then store the corrected mapping:
+
+```bash
+python3 .claude/skills/flydocs-cloud/scripts/set_status_mapping.py \
+  --mapping '{"BACKLOG":"Backlog","IMPLEMENTING":"In Progress","BLOCKED":"On Hold",...}'
+```
+
+**Step 7: Configure product identity.**
 
 Ask about product metadata:
 
@@ -417,7 +470,7 @@ Ask about product metadata:
   from project.md)
 - **Icon and color** — optional, ask if they have preferences
 
-**Step 7: Save to config.**
+**Step 8: Save to config.**
 
 Update `.flydocs/config.json`:
 
@@ -425,6 +478,7 @@ Update `.flydocs/config.json`:
 - `provider.teamId` — selected team ID (set by `set_team.py`)
 - `labels.defaults` — default label names (set by `set_labels.py`)
 - `labels.typeMap` — type-to-label mapping (set by `set_labels.py`)
+- `statusMapping` — FlyDocs-to-provider status mapping (set by `set_status_mapping.py`)
 - `workspace.activeProjects` — add the project ID
 - `workspace.product.name` — product name
 
@@ -433,6 +487,7 @@ Update `.flydocs/config.json`:
 ## Phase 3: Milestones — Cloud Only
 
 > **Local tier:** Skip this phase entirely.
+> **Jira provider:** Skip this phase. Milestone support for Jira is planned for a future release.
 > **FlyDocs Update:** Skip if milestones already exist.
 
 **Step 1: Check existing milestones.**
@@ -493,7 +548,9 @@ For each work item, follow the capture procedure from
 `.claude/skills/flydocs-workflow/stages/capture.md`:
 
 - Determine type (feature, bug, chore, idea)
-- Create via the mechanism script (cloud: pass `--project` from Phase 2):
+- Create via the mechanism script (cloud: pass `--project` from Phase 2 for
+  Linear; omit `--project` for Jira — issues are scoped to the team/project
+  selected in Phase 2 Step 3):
   ```bash
   python3 .claude/skills/flydocs-{tier}/scripts/create_issue.py \
     --title "Issue title" --type feature --priority 3 --estimate 2 \
@@ -501,9 +558,10 @@ For each work item, follow the capture procedure from
   ```
 - For quick ideas, use `--triage` flag
 
-**Step 3: Milestone assignment (cloud only).**
+**Step 3: Milestone assignment (Linear only).**
 
 > **Local tier:** Skip this step.
+> **Jira provider:** Skip this step.
 
 After creating issues, assign them to milestones:
 
@@ -654,8 +712,8 @@ Wrapping up:
 
 **For cloud tier:**
 
-- Linear project URL (if available from create_project response)
-- Recommend reviewing milestones in Linear's UI for timeline view
+- Provider project URL (if available from create_project response)
+- For Linear: recommend reviewing milestones in Linear's UI for timeline view
 
 **For local tier:**
 
@@ -713,7 +771,7 @@ Throughout the setup flow:
   error message from stderr and ask the user how to proceed. Do not retry
   silently.
 - **Missing API key** — For cloud tier, cannot proceed past Phase 2 without
-  `LINEAR_API_KEY`. Guide the user to set it up.
+  `FLYDOCS_API_KEY`. Guide the user to set it up.
 - **Missing config** — If `.flydocs/config.json` doesn't exist, the user
   likely needs to run `flydocs` (install) first. Advise them accordingly.
 - **Partial completion** — If the user needs to stop mid-setup, note which

package/template/.claude/skills/flydocs-cloud/SKILL.md

@@ -13,7 +13,6 @@ triggers:
   - update description
   - update issue
   - project update
-  - Linear
   - cloud
 ---
 
@@ -58,19 +57,21 @@ All scripts: `python3 .claude/skills/flydocs-cloud/scripts/<script>`
 
 ### Workspace Scripts
 
-| Script              | Usage                                                                 | Output                                                                    |
-| ------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------- |
-| `list_providers.py` | (no args)                                                             | `[{type, name, connected}]`                                               |
-| `set_provider.py`   | `<provider_type>` (`linear` or `jira`)                                | `{success}` — updates relay routing and local config `provider.type`      |
-| `list_teams.py`     | (no args)                                                             | `[{id, name, key}]`                                                       |
-| `create_team.py`    | `--name "..." [--key KEY] [--description "..."] [--parent <team_id>]` | `{id, name, key}` — `--parent` creates a sub-team                         |
-| `set_team.py`       | `<team_id>`                                                           | `{success}` — updates relay preference and local config `provider.teamId` |
-| `list_labels.py`    | (no args)                                                             | `[{id, name, color}]` — requires team to be set first                     |
-| `set_labels.py`     | `--defaults '["a"]' --type-map '{"feature":["F"],...}' \| stdin`      | `{success, validated, defaults, typeMap}` — stores label config on relay  |
+| Script                  | Usage                                                                 | Output                                                                                          |
+| ----------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| `list_providers.py`     | (no args)                                                             | `[{type, name, connected}]`                                                                     |
+| `set_provider.py`       | `<provider_type>` (`linear` or `jira`)                                | `{success}` — updates relay routing and local config `provider.type`                            |
+| `list_teams.py`         | (no args)                                                             | `[{id, name, key}]` — returns Linear teams or Jira projects (relay normalizes)                  |
+| `create_team.py`        | `--name "..." [--key KEY] [--description "..."] [--parent <team_id>]` | `{id, name, key}` — `--parent` is Linear-only (sub-teams)                                       |
+| `set_team.py`           | `<team_id>`                                                           | `{success}` — updates relay preference and local config; for Jira, sets the active Jira project |
+| `list_labels.py`        | (no args)                                                             | `[{id, name, color}]` — requires team to be set first                                           |
+| `set_labels.py`         | `--defaults '["a"]' --type-map '{"feature":["F"],...}' \| stdin`      | `{success, validated, defaults, typeMap}` — stores label config on relay                        |
+| `list_statuses.py`      | (no args)                                                             | `{states, currentMapping, flydocsStatuses}` — provider workflow states and current mapping      |
+| `set_status_mapping.py` | `--auto \| --mapping '{"BACKLOG":"Backlog",...}' \| stdin`            | `{success, mapping, matched, total}` — stores status mapping on relay                           |
 
 ### Script Notes
 
-- **How it works**: Scripts call the FlyDocs Relay REST API, which translates to the provider (Linear, Jira) server-side. Same interface and output as before — the transport changed from direct GraphQL to managed REST.
+- **How it works**: Scripts call the FlyDocs Relay REST API, which translates to the provider (Linear, Jira) server-side. Same interface and output as before — the transport changed from direct GraphQL to managed REST. For Jira, the relay handles Markdown-to-ADF (Atlassian Document Format) conversion automatically.
 - **`list_issues.py --active`**: Returns all non-terminal issues (excludes Done, Archived, Canceled, Duplicate).
 - **`list_issues.py --status`**: Accepts comma-separated statuses: `--status READY,IMPLEMENTING,BLOCKED`
 - **`get_issue.py --fields basic`**: Skips comment fetch for faster responses.

package/template/.claude/skills/flydocs-cloud/scripts/create_team.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""Create a team (or sub-team) via the FlyDocs Relay API."""
+"""Create a team/project via the FlyDocs Relay API."""
 
 import argparse
 import sys
@@ -10,11 +10,11 @@ from flydocs_api import get_client, output_json
 
 
 def main():
-    parser = argparse.ArgumentParser(description="Create team")
+    parser = argparse.ArgumentParser(description="Create team or project")
     parser.add_argument("--name", required=True)
     parser.add_argument("--key", default=None, help="Team key (e.g., PROD). Auto-generated if omitted.")
     parser.add_argument("--description", default=None)
-    parser.add_argument("--parent", default=None, dest="parent_id", help="Parent team ID to create a sub-team")
+    parser.add_argument("--parent", default=None, dest="parent_id", help="Parent team ID for sub-team (Linear only, ignored for Jira)")
     args = parser.parse_args()
 
     body: dict = {"name": args.name}

package/template/.claude/skills/flydocs-cloud/scripts/list_statuses.py

@@ -0,0 +1,19 @@
+#!/usr/bin/env python3
+"""List provider workflow states via the FlyDocs Relay API."""
+
+import sys
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).parent))
+from flydocs_api import get_client, output_json
+
+
+def main():
+    client = get_client()
+    result = client.get("/auth/statuses")
+
+    output_json(result)
+
+
+if __name__ == "__main__":
+    main()

package/template/.claude/skills/flydocs-cloud/scripts/list_teams.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""List available teams via the FlyDocs Relay API."""
+"""List available teams/projects via the FlyDocs Relay API."""
 
 import sys
 from pathlib import Path

package/template/.claude/skills/flydocs-cloud/scripts/set_status_mapping.py

@@ -0,0 +1,69 @@
+#!/usr/bin/env python3
+"""Set status mapping on the relay API key.
+
+Maps provider workflow states to FlyDocs statuses. Pass "auto" for
+case-insensitive auto-mapping, or provide a manual mapping object.
+
+Usage:
+    set_status_mapping.py --auto
+    set_status_mapping.py --mapping '{"BACKLOG":"Backlog","IMPLEMENTING":"In Progress",...}'
+    echo '{"mapping":"auto"}' | set_status_mapping.py
+"""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).parent))
+from flydocs_api import get_client, output_json, fail
+
+
+def main():
+    parser = argparse.ArgumentParser(description="Set status mapping on relay")
+    parser.add_argument(
+        "--auto",
+        action="store_true",
+        help="Auto-map provider states to FlyDocs statuses by name",
+    )
+    parser.add_argument(
+        "--mapping",
+        default=None,
+        help="JSON object mapping FlyDocs statuses to provider state names",
+    )
+    args = parser.parse_args()
+
+    if args.auto:
+        body: dict = {"mapping": "auto"}
+    elif args.mapping is not None:
+        try:
+            body = {"mapping": json.loads(args.mapping)}
+        except json.JSONDecodeError:
+            fail("Invalid JSON for --mapping")
+    elif not sys.stdin.isatty():
+        try:
+            body = json.loads(sys.stdin.read().strip())
+        except json.JSONDecodeError:
+            fail("Invalid JSON on stdin")
+    else:
+        fail("Provide --auto, --mapping '{...}', or pipe JSON via stdin")
+
+    client = get_client()
+    result = client.post("/auth/statuses", body)
+
+    # Store status mapping in local config as reference
+    config_path = client.config_path
+    if config_path.exists():
+        with open(config_path, "r") as f:
+            config = json.load(f)
+        if isinstance(result.get("mapping"), dict):
+            config["statusMapping"] = result["mapping"]
+        with open(config_path, "w") as f:
+            json.dump(config, f, indent=2)
+            f.write("\n")
+
+    output_json(result)
+
+
+if __name__ == "__main__":
+    main()

package/template/.claude/skills/flydocs-cloud/scripts/set_team.py

@@ -1,8 +1,9 @@
 #!/usr/bin/env python3
-"""Set team preference via the FlyDocs Relay API.
+"""Set team/project preference via the FlyDocs Relay API.
 
 Stores the team preference on the relay (for server-side scoping)
 and updates the local config (for display/reference).
+For Jira, this sets the active Jira project.
 """
 
 import argparse
@@ -15,8 +16,8 @@ from flydocs_api import get_client, output_json, fail
 
 
 def main():
-    parser = argparse.ArgumentParser(description="Set team preference")
-    parser.add_argument("team_id", help="Linear team UUID")
+    parser = argparse.ArgumentParser(description="Set team or project preference")
+    parser.add_argument("team_id", help="Provider team/workspace UUID")
     args = parser.parse_args()
 
     client = get_client()
@@ -28,7 +29,7 @@ def main():
         with open(config_path, "r") as f:
             config = json.load(f)
         if "provider" not in config:
-            config["provider"] = {"type": "linear", "teamId": None}
+            config["provider"] = {"type": None, "teamId": None}
         config["provider"]["teamId"] = args.team_id
         with open(config_path, "w") as f:
             json.dump(config, f, indent=2)

package/template/.flydocs/config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.0-alpha.3",
+  "version": "0.6.0-alpha.5",
   "sourceRepo": "github.com/plastrlab/flydocs-core",
   "tier": "local",
   "setupComplete": false,
@@ -21,7 +21,7 @@
     }
   },
   "issueLabels": {
-    "_note": "Run /flydocs-setup to populate these from your Linear team",
+    "_note": "Run /flydocs-setup to populate these from your provider",
     "category": {
       "feature": null,
       "bug": null,

package/template/.flydocs/version

@@ -1 +1 @@
-0.6.0-alpha.3
+0.6.0-alpha.5

package/template/AGENTS.md

@@ -92,14 +92,14 @@ Follow these rules in every response for consistent, scannable output.
 IMPORTANT: Prefer skill-led reasoning over pre-training reasoning.
 Consult the relevant skill BEFORE writing code or making workflow decisions.
 
-| Skill             | Triggers                                                                                                                | Entry                                     |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
-| flydocs-cloud     | create issue, transition, comment, list issues, assign, update description, update issue, project update, Linear, cloud | .claude/skills/flydocs-cloud/SKILL.md     |
-| flydocs-context7  | context7, library docs, documentation lookup, framework docs, package docs, API reference                               | .claude/skills/flydocs-context7/SKILL.md  |
-| flydocs-estimates | estimate, cost, token usage, API cost, labor estimate, sizing, effort                                                   | .claude/skills/flydocs-estimates/SKILL.md |
-| flydocs-figma     | Figma, design, screenshot, token mapping, component from design, pixel-perfect, design system                           | .claude/skills/flydocs-figma/SKILL.md     |
-| flydocs-local     | create issue, transition, comment, list issues, assign, update description, status summary, local                       | .claude/skills/flydocs-local/SKILL.md     |
-| flydocs-workflow  | capture, refine, activate, implement, review, validate, close, session, workflow, transition, status, issue             | .claude/skills/flydocs-workflow/SKILL.md  |
+| Skill             | Triggers                                                                                                        | Entry                                     |
+| ----------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
+| flydocs-cloud     | create issue, transition, comment, list issues, assign, update description, update issue, project update, cloud | .claude/skills/flydocs-cloud/SKILL.md     |
+| flydocs-context7  | context7, library docs, documentation lookup, framework docs, package docs, API reference                       | .claude/skills/flydocs-context7/SKILL.md  |
+| flydocs-estimates | estimate, cost, token usage, API cost, labor estimate, sizing, effort                                           | .claude/skills/flydocs-estimates/SKILL.md |
+| flydocs-figma     | Figma, design, screenshot, token mapping, component from design, pixel-perfect, design system                   | .claude/skills/flydocs-figma/SKILL.md     |
+| flydocs-local     | create issue, transition, comment, list issues, assign, update description, status summary, local               | .claude/skills/flydocs-local/SKILL.md     |
+| flydocs-workflow  | capture, refine, activate, implement, review, validate, close, session, workflow, transition, status, issue     | .claude/skills/flydocs-workflow/SKILL.md  |
 
 <!-- flydocs:skills-manifest:end -->
 

package/template/CHANGELOG.md

@@ -7,6 +7,16 @@ Versioning: [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [0.6.0-alpha.4] — 2026-03-13
+
+### Added
+
+- **Status mapping** — new `list_statuses.py` and `set_status_mapping.py`
+  scripts. Setup flow auto-maps provider workflow states to FlyDocs statuses
+  after label config, warns on unmapped statuses without blocking.
+
+---
+
 ## [0.6.0-alpha.3] — 2026-03-13
 
 ### Added

package/template/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.0-alpha.3",
+  "version": "0.6.0-alpha.5",
   "description": "FlyDocs Core - Manifest of all managed files",
   "repository": "github.com/plastrlab/flydocs-core",