@pulsarinteractive/geniustasker 0.1.0-beta.18 → 0.1.0-beta.19
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 +5 -0
- package/README.md +1 -1
- package/docs/CLI.md +5 -1
- package/docs/INTEGRATIONS.md +8 -4
- package/docs/PLANNING.md +2 -1
- package/docs/STORAGE.md +32 -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 +523 -9
- package/remote/workflows.json +12 -1
- package/skills/geniustasker/SKILL.md +7 -0
- package/skills/geniustasker-media/SKILL.md +10 -1
- package/skills/geniustasker-memory/SKILL.md +7 -0
- package/skills/geniustasker-planning/SKILL.md +7 -0
- package/src/attachment-upload.mjs +203 -0
- package/src/cli.mjs +22 -0
- package/src/command-catalog.mjs +15 -14
- package/src/mcp.mjs +42 -3
- package/src/ticket-storage.mjs +67 -0
- package/src/transport.mjs +21 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,10 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.0-beta.19
|
|
4
|
+
|
|
5
|
+
- Inspect one project’s storage, preview a single attachment change and publish an original with resumable uploads. Addition, replacement and removal have separate grants.
|
|
6
|
+
- Retire individual notes with a recoverable editorial history. Project and Memory deletion are owner actions.
|
|
7
|
+
|
|
3
8
|
## 0.1.0-beta.18 — 2026-11-19
|
|
4
9
|
|
|
5
10
|
- Review verified project changes against the owner's documentation policy and the selected note revision. Offer first notes individually, preserve each section's language and style, and preview optional product, game, music or free-form pages.
|
package/README.md
CHANGED
|
@@ -55,7 +55,7 @@ For a stdio MCP host, use this after signing in:
|
|
|
55
55
|
"mcpServers": {
|
|
56
56
|
"geniustasker": {
|
|
57
57
|
"command": "npx",
|
|
58
|
-
"args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.
|
|
58
|
+
"args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.19", "mcp", "--context", "work"]
|
|
59
59
|
}
|
|
60
60
|
}
|
|
61
61
|
}
|
package/docs/CLI.md
CHANGED
|
@@ -131,7 +131,7 @@ launching stdio servers with this entry (adjust environment/context as needed):
|
|
|
131
131
|
"mcpServers": {
|
|
132
132
|
"geniustasker": {
|
|
133
133
|
"command": "npx",
|
|
134
|
-
"args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.
|
|
134
|
+
"args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.19", "mcp", "--context", "work"]
|
|
135
135
|
}
|
|
136
136
|
}
|
|
137
137
|
}
|
|
@@ -665,3 +665,7 @@ with `archive comments --scope project:ID --id TASK`. The connector offers
|
|
|
665
665
|
`tasker_archive_detail` and `tasker_archive_comments`. A restored, expired or
|
|
666
666
|
inaccessible task may be absent from the archive. Reconnect with explicit
|
|
667
667
|
historical access when needed.
|
|
668
|
+
|
|
669
|
+
## Ticket files and storage
|
|
670
|
+
|
|
671
|
+
For project diagnostics, distinct permissions, resumable file uploads and per-item receipts, follow the [ticket attachment workflow](STORAGE.md).
|
package/docs/INTEGRATIONS.md
CHANGED
|
@@ -16,8 +16,8 @@ environment or replace a connection just to get around an access refusal.
|
|
|
16
16
|
For example, to connect a production context to a direct Codex MCP server:
|
|
17
17
|
|
|
18
18
|
```sh
|
|
19
|
-
npx -y @pulsarinteractive/geniustasker@0.1.0-beta.
|
|
20
|
-
codex mcp add geniustasker-production -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.
|
|
19
|
+
npx -y @pulsarinteractive/geniustasker@0.1.0-beta.19 auth login --environment production --context tasker-beta
|
|
20
|
+
codex mcp add geniustasker-production -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.19 mcp --environment production --context tasker-beta
|
|
21
21
|
```
|
|
22
22
|
|
|
23
23
|
Use either this configuration or the development example below for the intended
|
|
@@ -27,8 +27,8 @@ before working. Adding the production example does not retarget a bundled plugin
|
|
|
27
27
|
## Codex: direct MCP
|
|
28
28
|
|
|
29
29
|
```sh
|
|
30
|
-
npx -y @pulsarinteractive/geniustasker@0.1.0-beta.
|
|
31
|
-
codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.
|
|
30
|
+
npx -y @pulsarinteractive/geniustasker@0.1.0-beta.19 auth login --context work
|
|
31
|
+
codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.19 mcp --context work
|
|
32
32
|
```
|
|
33
33
|
|
|
34
34
|
Restart the host as needed, then inspect its MCP list. Ask the agent to read its
|
|
@@ -83,3 +83,7 @@ geniustasker auth logout --context work
|
|
|
83
83
|
This revokes the server session before removing its credentials. A failed revoke
|
|
84
84
|
keeps local evidence so it can be retried. Uninstalling a package alone does not
|
|
85
85
|
revoke a remote session.
|
|
86
|
+
|
|
87
|
+
## Ticket files and storage
|
|
88
|
+
|
|
89
|
+
For project diagnostics, distinct permissions, resumable file uploads and per-item receipts, follow the [ticket attachment workflow](STORAGE.md).
|
package/docs/PLANNING.md
CHANGED
|
@@ -78,7 +78,6 @@ availability state, independent of canonical progress and a known pause.
|
|
|
78
78
|
| New project | `project.create` | `projects:write`, all-resources consent including future projects, available account quota |
|
|
79
79
|
| Project settings | `project.update`, `project.features` | `projects:write`, native project administration |
|
|
80
80
|
| Agent instructions | `project.configureInstructions` | `projects:write`, actual project owner, agent contributions already enabled |
|
|
81
|
-
| Delete project | `project.delete` | `projects:write`, project ownership |
|
|
82
81
|
| Sprint lifecycle | `sprint.create/update/start/complete/delete` | `tasks:write`, native sprint management |
|
|
83
82
|
| Workflow stages | `workflow.create/update/delete` | `tasks:write`, native project administration |
|
|
84
83
|
| Recurring tasks | `schedule.create/update/delete` | `tasks:write`, native schedule rights |
|
|
@@ -216,3 +215,5 @@ no public changed items. These instructions do not change shared deadlines,
|
|
|
216
215
|
status, importance, XP or agent execution claims. Reassignment, deletion and
|
|
217
216
|
access changes make affected instructions stale. They belong only to the
|
|
218
217
|
connected owner; another collaborator's instructions are not exposed.
|
|
218
|
+
|
|
219
|
+
A project or an entire Memory can be removed only through the owner interface. Agents can edit or delete a single authorized Memory page with its current revision. Never emulate removal of a whole space by processing its children.
|
package/docs/STORAGE.md
ADDED
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Files on tickets
|
|
2
|
+
|
|
3
|
+
Use the `storage` workflow for one selected project. Read capabilities and verify the project, task and intended action with the user. A new grant applies only to the resources chosen in the consent screen.
|
|
4
|
+
|
|
5
|
+
| Operation | Required project permissions |
|
|
6
|
+
| ------------------------------------------------------- | ----------------------------------------------- |
|
|
7
|
+
| Read active tickets and their attachment metadata | `tasks:read` and `storage:read` |
|
|
8
|
+
| Include archived tickets or inspect project-wide totals | Add `history:read` |
|
|
9
|
+
| Preview and add one file | `tasks:read` and `attachments:add` |
|
|
10
|
+
| Preview and replace one file | `tasks:read` and `attachments:replace` |
|
|
11
|
+
| Preview and remove one file | `tasks:read` and `attachments:remove` |
|
|
12
|
+
| Delete one expressly selected task | `tasks:delete` with the task’s current revision |
|
|
13
|
+
|
|
14
|
+
Operations on an archived ticket also need historical access. A Memory asset grant does not authorize ticket files. A missing permission requires a new user-approved delegation.
|
|
15
|
+
|
|
16
|
+
## Find the right item
|
|
17
|
+
|
|
18
|
+
Use `tasker_storage_tickets` and `tasker_storage_files` with a project scope, state and size threshold. Follow the continuation with unchanged filters. On partial coverage, `tasker_storage_analyze` processes one bounded slice. Keep its cursor and report the coverage. Use `tasker_storage_selection` with exactly one ticket ID or attachment ID. If a ticket spans multiple slices, keep the same selection and cursor, add only the returned slice totals, then report the final estimate. Shared and protected bytes can remain charged. Account-wide cleanup and bulk operations belong to the owner's application.
|
|
19
|
+
|
|
20
|
+
## Transfer an original
|
|
21
|
+
|
|
22
|
+
1. Call `tasker_attachment_preview` with the project scope, task ID, attachment ID and action. For an addition choose a fresh attachment UUID. For a replacement keep the original attachment ID and revision.
|
|
23
|
+
2. In the local CLI, run `geniustasker attachment prepare-upload --file destination.json`. The JSON includes `scope`, `taskId`, `attachmentId`, the preview's `epoch`, selected local `file` and `contentType`. A replacement also includes `replaceRevision`. Resume with `geniustasker attachment upload --operation UUID`. Stdio MCP exposes the same local-file operations. Use a regular file the user selected.
|
|
24
|
+
3. In ChatGPT choose the attached conversation file. Discover `tasker_attachment_prepare_host_file` and `tasker_attachment_upload_host_file` with file support enabled. Keep the prepared metadata and original file selection on every continuation. The remote server transfers at most two missing parts per call. Use the local CLI for a large file whose temporary host cannot serve byte ranges, or select the file again if the URL expired.
|
|
25
|
+
4. Once the original is published, explicitly run `tasker_attachment_add` or `tasker_attachment_replace` with the preview's `epoch` and `expectedRevision`, the published `assetId`, and a fresh `operationId` and millisecond `issuedAt`. Retain both identifiers for a retry. If another editor changed the attachment, show the new preview before applying a different operation.
|
|
26
|
+
5. To remove an attachment, preview `remove`, confirm the chosen item, then use `tasker_attachment_remove` without an asset ID. Report the returned revision, released bytes and pending release. A successful transfer alone does not change the task.
|
|
27
|
+
|
|
28
|
+
For replacement, the prior original stays attached until the revision-checked change succeeds. The server enforces the original's type and byte size and applies storage quota. Images and other files have separate decimal MB caps. Free supports 5 MB images and 25 MB other originals, Starter 15 MB and 100 MB, Pro 25 MB and 200 MB. Originals on active tasks have no archival timer. After archival the retention period is 30 days for Free and 90 days for Starter or Pro, counted from the later of archival and original addition. Replacing the original keeps its addition date. Use current diagnostics for expiry and availability. Pasting an original’s URL into a different project or Memory preserves its original access rules and expiration. A structured reference in the source project or a separately authorized copy can retain bytes. Re-uploading creates a separate original subject to its destination’s quota and retention.
|
|
29
|
+
|
|
30
|
+
## Notes and project ownership
|
|
31
|
+
|
|
32
|
+
An agent may update a single Memory note or use `memory.page.delete` to retire it from the active tree and search. Include a concise `changeReason`, retain the page ID and read its version history to recover earlier content. The selected earlier revision can be restored with the current revision. The retained page and history still count toward quota. The owner manages deletion of an entire project or Memory in the application. Never simulate bulk cleanup by deleting its children.
|
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.19",
|
|
5
5
|
"description": "Track project work and independent product memories with your own agents.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Pulsar Interactive"
|