flightdesk 0.6.0 → 0.6.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +7 -4
  2. package/main.js +287 -183
  3. package/main.js.map +4 -4
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -27,7 +27,7 @@ npm install -g flightdesk
27
27
  flightdesk init
28
28
 
29
29
  # Register a Claude Code session with a task
30
- claude --remote "Fix the auth bug" | flightdesk register <project-id>
30
+ flightdesk register <task-id> --prompt "Fix the auth bug"
31
31
 
32
32
  # Check task status
33
33
  flightdesk status
@@ -105,6 +105,9 @@ MCP equivalents are `bind_agent`, `list_dispatch_requests`, `update_dispatch_req
105
105
  `list_tasks` also accepts `assigneeId` and `openDispatch`. A normal comment, including an `@agent`
106
106
  mention, is stored as data and does not request execution.
107
107
 
108
- Tasks now expose nullable `runStatus` and an independent `workStatusId`. GraphQL `status` remains
109
- a deprecated alias for existing clients; MCP task detail responses also retain the alias. General
110
- tasks have no run status and cannot enter GitHub or preview operations.
108
+ Tasks expose a nullable `runStatus` (the coding run, written by GitHub webhooks and QA) and a
109
+ `phase` — where the work is in the FlightDesk pipeline: `BACKLOG`, `READY`, `PLAN`, `PLAN_REVIEW`,
110
+ `BUILD`, `WAITING`, `CODE_REVIEW`, `MERGE`, `RELEASE` or `DONE`. The phases are the same on every
111
+ project; a project's settings decide only whether each gate needs a human. `transition_work_status`
112
+ takes `phase`. GraphQL `status` remains a deprecated alias for `runStatus`. General tasks have no
113
+ run status and cannot enter GitHub or preview operations.