@elevasis/sdk 1.36.2 → 1.36.3
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.
package/dist/cli.cjs
CHANGED
|
@@ -45808,7 +45808,7 @@ function wrapAction(commandName, fn) {
|
|
|
45808
45808
|
// package.json
|
|
45809
45809
|
var package_default = {
|
|
45810
45810
|
name: "@elevasis/sdk",
|
|
45811
|
-
version: "1.36.
|
|
45811
|
+
version: "1.36.3",
|
|
45812
45812
|
description: "SDK for building Elevasis organization resources",
|
|
45813
45813
|
type: "module",
|
|
45814
45814
|
bin: {
|
|
@@ -48296,6 +48296,13 @@ function registerTaskCreate(program3) {
|
|
|
48296
48296
|
if (checklist !== void 0) body.checklist = checklist;
|
|
48297
48297
|
const apiUrl = resolveApiUrl(options.apiUrl);
|
|
48298
48298
|
const result = await apiPost("/api/external/project-tasks", body, apiUrl);
|
|
48299
|
+
if (!options.milestone) {
|
|
48300
|
+
process.stderr.write(
|
|
48301
|
+
source_default.yellow(
|
|
48302
|
+
"Warning: Task created without a milestone \u2014 it will appear under the 'Unassigned' group, not under a phase. Pass --milestone to link it.\n"
|
|
48303
|
+
)
|
|
48304
|
+
);
|
|
48305
|
+
}
|
|
48299
48306
|
if (options.pretty) {
|
|
48300
48307
|
const t = result.task;
|
|
48301
48308
|
console.log(source_default.green(`
|
package/package.json
CHANGED
|
@@ -718,6 +718,8 @@ Onboarding & Scope — Checklist (2/3 complete)
|
|
|
718
718
|
|
|
719
719
|
### `task add <client> "<name>" [options]` — Add Task
|
|
720
720
|
|
|
721
|
+
> **Milestone linking guidance:** Task creation SHOULD resolve a milestone and pass `--milestone <milestone-id>`. An unmilestoned task is allowed (the CLI warns when `--milestone` is omitted, and the task saves with `milestone_id = null`), but it will appear under an "Unassigned / No milestone" group in the Project view rather than under its phase — so phase-grouped progress views will not reflect it until it is linked. Resolve the milestone first and link on creation whenever possible.
|
|
722
|
+
|
|
721
723
|
**Options:**
|
|
722
724
|
|
|
723
725
|
- `--milestone "<name>"` — link to a milestone (resolve by name first)
|
|
@@ -966,10 +968,10 @@ When args don't match any command pattern, infer intent from natural language:
|
|
|
966
968
|
| "what's overdue?" | List milestones where `due_date < now() AND status != 'completed'` |
|
|
967
969
|
| "block acme, waiting on client credentials" | `update acme --status blocked` |
|
|
968
970
|
| "show checklist for phase 2" | Read and display checklist for milestone "phase 2" via psql or `project:milestone:list` |
|
|
969
|
-
| "add 'deploy staging' to task X's checklist" | Read task X's checklist → append `{id: uuid, label: "deploy staging", completed: false}` → `project:task:update <id> --checklist '<json-array>'`
|
|
970
|
-
| "mark 'deploy staging' done on task X" | Read task X's checklist → flip `completed` on matching item → `project:task:update <id> --checklist '<json-array>'`
|
|
971
|
+
| "add 'deploy staging' to task X's checklist" | Read task X's checklist → append `{id: uuid, label: "deploy staging", completed: false}` → `project:task:update <id> --checklist '<json-array>'` |
|
|
972
|
+
| "mark 'deploy staging' done on task X" | Read task X's checklist → flip `completed` on matching item → `project:task:update <id> --checklist '<json-array>'` |
|
|
971
973
|
| "clear the checklist on task X" | `project:task:update <task-id> --checklist '[]'` |
|
|
972
|
-
| "add checklist item to onboarding milestone: review scope doc" | Read milestone checklist → append item → `project:milestone:update <id> --checklist '<json-array>'`
|
|
974
|
+
| "add checklist item to onboarding milestone: review scope doc" | Read milestone checklist → append item → `project:milestone:update <id> --checklist '<json-array>'` |
|
|
973
975
|
| "I'm done" / "task complete" / "done with this" | Resolve active task → confirm → `project:task:update <task-id> --status completed` |
|
|
974
976
|
| "save: Apify actor X rate-limits at 20rps" | Resolve active project/task → `project:note:create --project <id> --type agent_learning --task <task-id> "Apify actor X rate-limits at 20rps"` |
|
|
975
977
|
| "remember: client requires ISO dates, not timestamps" | Resolve active project/task → `project:note:create --project <id> --type agent_learning --task <task-id> "client requires ISO dates, not timestamps"` |
|