@sinoia/hubdoc-tools 1.9.0 → 1.10.0
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/cli.js +883 -814
- package/docs/llm-usage.md +15 -7
- package/package.json +1 -1
package/docs/llm-usage.md
CHANGED
|
@@ -377,12 +377,16 @@ themselves. All commands support `--json` for machine parsing.
|
|
|
377
377
|
| start | complete`.
|
|
378
378
|
|
|
379
379
|
`hubdoc tickets --project=<pid>` — `ls | show | create | update | delete
|
|
380
|
-
| assign | status | move | activities | deliverable | dispatch
|
|
381
|
-
verb requires `--project=<pid>`. `ls
|
|
382
|
-
|
|
383
|
-
[--column <col>]` uses the canonical
|
|
384
|
-
|
|
385
|
-
kanban column at the same
|
|
380
|
+
| assign | status | move | activities | deliverable | dispatch |
|
|
381
|
+
comment | comments`. Every verb requires `--project=<pid>`. `ls
|
|
382
|
+
--backlog` (or `ls --sprint null`) lists the backlog. `assign --to null`
|
|
383
|
+
unassigns. `status --to <state> [--column <col>]` uses the canonical
|
|
384
|
+
statuses: `open | in_progress | done | blocked | awaiting_human |
|
|
385
|
+
cancelled | failed` and optionally pins the kanban column at the same
|
|
386
|
+
time. `comment <id> --body <text>` (or `--body-file <path>`) posts a
|
|
387
|
+
message on the ticket's discussion thread (visible in Corex / Agoria,
|
|
388
|
+
attributed to the token holder); `comments <id>` reads the thread
|
|
389
|
+
oldest-first (paginated like `activities`).
|
|
386
390
|
|
|
387
391
|
`hubdoc tasks --project=<pid> --ticket=<tid>` — `ls | show | create |
|
|
388
392
|
update | delete | complete | reorder`. Sub-tasks live under a ticket;
|
|
@@ -443,7 +447,11 @@ hubdoc tasks create --project "$PID" --ticket "$TID" \
|
|
|
443
447
|
# 5. Dispatch the agent already configured on the ticket.
|
|
444
448
|
hubdoc tickets dispatch "$TID" --project "$PID" --json
|
|
445
449
|
|
|
446
|
-
# 6. Later —
|
|
450
|
+
# 6. Later — post a follow-up on the ticket thread (visible to the human):
|
|
451
|
+
hubdoc tickets comment "$TID" --project "$PID" \
|
|
452
|
+
--body "Point d’avancement : devis en cours de rédaction, ETA demain 10h." --json
|
|
453
|
+
|
|
454
|
+
# 7. Publish an already-attached deliverable and close the ticket.
|
|
447
455
|
hubdoc tickets deliverable "$TID" --project "$PID" \
|
|
448
456
|
--deliverable "$DELIVERABLE_ID" --json
|
|
449
457
|
hubdoc tickets status "$TID" --project "$PID" \
|