@pulsarinteractive/geniustasker 0.1.0-beta.13 → 0.1.0-beta.15
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/CHANGELOG.md +21 -0
- package/README.md +5 -1
- package/docs/CHATGPT.md +17 -0
- package/docs/CLI.md +46 -1
- package/docs/FEEDBACK.md +96 -0
- package/docs/INTEGRATIONS.md +4 -4
- package/docs/PLANNING.md +149 -10
- package/docs/TASK_CHECKLISTS.md +85 -0
- package/docs/TASK_LOCKS.md +99 -0
- package/docs/TASK_PAUSES.md +91 -0
- package/examples/codex.toml +1 -1
- package/examples/mcp.json +1 -1
- package/mcp.json +1 -1
- package/package.json +1 -1
- package/plugin.json +1 -1
- package/remote/tool-catalog.json +735 -2
- package/remote/workflows.json +62 -6
- package/skills/geniustasker/SKILL.md +37 -0
- package/skills/geniustasker/references/agent-runs.md +33 -2
- package/skills/geniustasker/references/collaboration.md +15 -2
- package/skills/geniustasker/references/host-events.md +9 -0
- package/skills/geniustasker/references/incremental-reads.md +11 -0
- package/skills/geniustasker/references/protocols.md +29 -3
- package/skills/geniustasker-feedback/SKILL.md +44 -0
- package/skills/geniustasker-feedback/agents/openai.yaml +4 -0
- package/skills/geniustasker-planning/SKILL.md +48 -0
- package/src/changes.mjs +5 -1
- package/src/cli.mjs +134 -7
- package/src/client.mjs +16 -0
- package/src/command-catalog.mjs +156 -1
- package/src/command-input-schemas.mjs +924 -0
- package/src/commands.mjs +250 -20
- package/src/feedback-contract.mjs +629 -0
- package/src/feedback-image.mjs +123 -0
- package/src/feedback-media-transfer.mjs +61 -0
- package/src/feedback.mjs +152 -0
- package/src/intents.mjs +111 -0
- package/src/mcp.mjs +126 -3
- package/src/protocols.mjs +1 -0
- package/src/resources.mjs +26 -3
- package/src/task-availability-contract.mjs +166 -0
- package/src/task-availability.mjs +35 -0
- package/src/task-state-legacy-contract.mjs +121 -0
- package/src/transport.mjs +10 -3
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
# Pause and resume known work
|
|
2
|
+
|
|
3
|
+
Client beta.15 supports explicit pause commands and task-state v2. Installed
|
|
4
|
+
beta.14 does not expose these additions. Client support does not establish
|
|
5
|
+
server rollout: discover the connected service's commands and collection
|
|
6
|
+
versions before use. An unavailable transition is a limitation to
|
|
7
|
+
report, not permission to guess a command or reset started work to New.
|
|
8
|
+
|
|
9
|
+
## Record the actual work state
|
|
10
|
+
|
|
11
|
+
New means work has not started. InProgress requires current identifiable
|
|
12
|
+
execution, not partial implementation or an undelivered lot. Paused records a
|
|
13
|
+
known interruption of started work, with its reason and concrete resumption
|
|
14
|
+
point. Done requires verified intended completion. Multiple InProgress tasks
|
|
15
|
+
require actual parallel activity with attributable workers.
|
|
16
|
+
|
|
17
|
+
When work you control is knowingly interrupted or you switch away from it,
|
|
18
|
+
preserve its description, comments and verified results and use the discovered
|
|
19
|
+
pause operation. Never infer a pause from silence, an absent heartbeat or an
|
|
20
|
+
expired lease. Do not pause somebody else's task merely because its reports
|
|
21
|
+
are old. Until the transition is available, retain a factual authorized note
|
|
22
|
+
and explain the missing capability.
|
|
23
|
+
|
|
24
|
+
Paused is progress; Locked is a separate obstacle. A paused task can also be
|
|
25
|
+
Locked by a manual reason or unfinished prerequisites. Removing a lock does
|
|
26
|
+
not resume it, and pausing/resuming does not remove dependencies or manual
|
|
27
|
+
reasons. Read both `progress` and effective `status`, not one badge alone.
|
|
28
|
+
Unknown/incomplete availability never proves that resuming is allowed.
|
|
29
|
+
|
|
30
|
+
## Use the explicit command
|
|
31
|
+
|
|
32
|
+
Inspect `commands describe --kind KIND --json` or `tasker_command_help` and use
|
|
33
|
+
the ordinary immutable prepare/execute workflow:
|
|
34
|
+
|
|
35
|
+
| Command | Envelope target and revision | Data |
|
|
36
|
+
| ------------- | ------------------------------------ | --------------------------------- |
|
|
37
|
+
| `task.pause` | Task ID and current task revision | `{reason,nextSteps}` |
|
|
38
|
+
| `task.resume` | Task ID and current task revision | `{}` |
|
|
39
|
+
| `run.pause` | Live run ID and current run revision | `{taskRevision,reason,nextSteps}` |
|
|
40
|
+
| `run.resume` | Live run ID and current run revision | `{taskRevision}` |
|
|
41
|
+
|
|
42
|
+
`reason` is required text of 1–500 characters; `nextSteps` is required text of
|
|
43
|
+
1–2000 characters. Both must be nonempty after trimming. Give an observed reason
|
|
44
|
+
and the next concrete action needed to resume, without replacing the task's
|
|
45
|
+
existing description or past comments. For example: reason "Switching to the
|
|
46
|
+
requested incident investigation" and nextSteps "Resume the pending migration
|
|
47
|
+
verification from the saved test results" only when those facts are true.
|
|
48
|
+
|
|
49
|
+
Pause applies to InProgress or an already Paused task; repeating it can update
|
|
50
|
+
the reason and next steps while retaining the original pause time. It is not
|
|
51
|
+
a way to label never-started, Done or archived work. Resume applies to Paused
|
|
52
|
+
and requests InProgress: use it only when actual execution is resuming. Current
|
|
53
|
+
locks, dependencies, revisions and permissions can refuse that request. Reread
|
|
54
|
+
the current task and availability before resuming; a receipt is not an automatic
|
|
55
|
+
start signal or proof that an external worker is running.
|
|
56
|
+
|
|
57
|
+
Never enter or leave Paused through `task.update`, `run.patch`, a workflow move
|
|
58
|
+
or a fabricated status. `pauseReason`, `pauseNextSteps` and `pausedAt` are
|
|
59
|
+
server-owned read fields. A Working report is not a substitute for resumption.
|
|
60
|
+
|
|
61
|
+
Under an active agent claim, its owner must use **run.pause/run.resume**, with
|
|
62
|
+
both current run and task revisions. The pause records the run as Waiting and
|
|
63
|
+
the resume records Working; these commands retain the claim and do not extend
|
|
64
|
+
its lease. Read both records after success. A standalone Waiting checkpoint
|
|
65
|
+
does not itself pause the task. Expiry, cancellation or takeover cannot be
|
|
66
|
+
bypassed with direct task commands, profile switching or a guessed fresh lease.
|
|
67
|
+
|
|
68
|
+
Preserve the operation ID, issuedAt, target, revisions, reason, next steps and
|
|
69
|
+
full body after an uncertain reply. Retry that same operation. A definitive
|
|
70
|
+
conflict needs fresh reads and a newly prepared reconciled intent. Do not
|
|
71
|
+
convert a known refusal into automatic retries or claim XP/push delivery.
|
|
72
|
+
|
|
73
|
+
## Discover and read v2 explicitly
|
|
74
|
+
|
|
75
|
+
Read capabilities. In the `collections` entry with `id: "tasks"`, choose
|
|
76
|
+
`taskState: "v2"` only when `taskStateVersions` includes `"v2"`. For CLI use
|
|
77
|
+
`--task-state v2` on `resources list`, `changes list` or `changes watch`; for MCP
|
|
78
|
+
pass `taskState: "v2"`. Keep the version unchanged across continuations and
|
|
79
|
+
bounded watches. No hidden discovery or automatic opt-in occurs.
|
|
80
|
+
|
|
81
|
+
V2 snapshots retain the existing source and dependency fields and require
|
|
82
|
+
`pauseReason`, `pauseNextSteps` and `pausedAt`, each nullable. `progress` can be
|
|
83
|
+
Paused while effective `status` is Paused, Locked or Unknown. A null pause field
|
|
84
|
+
does not make an incomplete source complete or authorize resumption.
|
|
85
|
+
|
|
86
|
+
Older support is advertised by `taskState: "v1"`; choose v1 only when that
|
|
87
|
+
signal is present. V1 deliberately omits the entire availability snapshot for
|
|
88
|
+
Paused tasks, and it never contains the three new fields. Without either
|
|
89
|
+
advertisement omit the option. Missing snapshots remain unknown, never New or
|
|
90
|
+
available. Follow [source freshness and bounded reads](TASK_LOCKS.md#read-the-current-source)
|
|
91
|
+
before any start, resumption or completion, including after a remove-only delta.
|
package/examples/codex.toml
CHANGED
package/examples/mcp.json
CHANGED
package/mcp.json
CHANGED
package/package.json
CHANGED
package/plugin.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
|
|
3
3
|
"name": "geniustasker",
|
|
4
|
-
"version": "0.1.0-beta.
|
|
4
|
+
"version": "0.1.0-beta.15",
|
|
5
5
|
"description": "Track project work and independent product memories with your own agents.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Pulsar Interactive"
|