@pulsarinteractive/geniustasker 0.1.0-beta.11 → 0.1.0-beta.13

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 (40) hide show
  1. package/CHANGELOG.md +22 -0
  2. package/README.md +14 -1
  3. package/docs/ARCHITECTURE.md +15 -13
  4. package/docs/CHATGPT.md +6 -0
  5. package/docs/CLI.md +153 -5
  6. package/docs/INTEGRATIONS.md +25 -2
  7. package/docs/MEMORY.md +9 -0
  8. package/docs/WORKFLOWS.md +14 -0
  9. package/examples/codex.toml +1 -1
  10. package/examples/mcp.json +1 -1
  11. package/mcp.json +1 -1
  12. package/package.json +2 -2
  13. package/plugin.json +1 -1
  14. package/remote/tool-catalog.json +296 -1
  15. package/remote/workflows.json +53 -2
  16. package/skills/geniustasker/SKILL.md +15 -1
  17. package/skills/geniustasker/references/agent-runs.md +144 -0
  18. package/skills/geniustasker/references/host-events.md +116 -0
  19. package/skills/geniustasker/references/importance.md +90 -0
  20. package/skills/geniustasker/references/metric-goals.md +143 -0
  21. package/skills/geniustasker/references/metrics-observations.md +184 -0
  22. package/skills/geniustasker/references/metrics.md +136 -0
  23. package/skills/geniustasker/references/protocols.md +156 -0
  24. package/skills/geniustasker/references/updates.md +31 -0
  25. package/skills/geniustasker-graph/SKILL.md +10 -0
  26. package/skills/geniustasker-memory/SKILL.md +19 -6
  27. package/skills/geniustasker-memory/references/knowledge-workflows.md +42 -0
  28. package/skills/geniustasker-planning/SKILL.md +6 -1
  29. package/src/changes.mjs +3 -5
  30. package/src/cli.mjs +108 -14
  31. package/src/command-catalog.mjs +849 -562
  32. package/src/command-input-schemas.d.mts +8 -0
  33. package/src/command-input-schemas.mjs +1021 -0
  34. package/src/commands.mjs +78 -25
  35. package/src/mcp.mjs +48 -20
  36. package/src/protocols.mjs +122 -0
  37. package/src/resources.mjs +98 -0
  38. package/src/run-events.mjs +145 -0
  39. package/src/update-runtime.mjs +169 -0
  40. package/src/update.mjs +306 -0
package/CHANGELOG.md CHANGED
@@ -1,5 +1,27 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.0-beta.13 — 2026-11-16
4
+
5
+ - Add personal and project custom metrics with scoped discovery, exact aggregation, observation history, corrections and voids.
6
+ - Link metrics to lifetime or fixed-window goals with bounded backfill, exact target comparisons and explicit notification/coach choices.
7
+ - Provide metric and goal guides, generated command schemas and a dedicated MCP write tool. Read current service capabilities and permissions before use; availability depends on the connected deployment.
8
+
9
+ ## 0.1.0-beta.12 — 2026-11-16
10
+
11
+ - Add an opt-in host event adapter to CLI/local MCP with stable IDs/times, prepare-only support and the normal immutable journal. Process exit requests review, never task completion; no process/log capture or automatic polling.
12
+ - Clarify Memory cooperation, hosted versus local retries and server-owned latest-agent attribution; preserve concurrent contributions after explicit revision conflicts.
13
+
14
+ - Agent run workflows document explicit claims, real checkpoints, fenced task patches and truthful completion across CLI and MCP.
15
+
16
+ - Protocol command help now includes filtered, generated nested schemas, nullability and limits in the CLI and local MCP, with an explicit publish example.
17
+
18
+ - Add task protocol preview to CLI/local MCP and the hosted tool catalogue, with a read-only POST, digest-bound pagination, explicit 20-step apply commands and a shared protocol workflow.
19
+
20
+ - Explain impact-based task importance, short reasons for agent-classified Important/Critical work, preservation of human choices and the same workflow across CLI/local MCP/hosted guides. Field availability is discovered from the service; this is not a claim of Flutter notification-threshold delivery.
21
+ - Discover updates at most once per UTC day and installed version in interactive terminals, with bounded anonymous npm checks and an opt-out. JSON, MCP, CI and local-only commands do not check automatically.
22
+ - Add `update check` and explicit `update install` with beta/stable channel selection. Global npm installation is verified before and after the update; local/npx/managed copies receive manual guidance.
23
+ - Keep simultaneous CLI commands and long-lived MCP servers protected from installation through per-process activity leases. Credentials and immutable operation journals are unchanged.
24
+
3
25
  ## 0.1.0-beta.11 — 2026-10-26
4
26
 
5
27
  - Update the transitive URI parser to its patched 3.1.9 release.
package/README.md CHANGED
@@ -19,6 +19,13 @@ Sign in in the browser, select your projects or memories, then approve the reque
19
19
  permissions. The terminal connects automatically. No token to copy.
20
20
  Installing the package does not grant application access.
21
21
 
22
+ The beta CLI and bundled local MCP examples default to **development**.
23
+ Production access is enabled for admitted accounts and is the environment used
24
+ by TestFlight. To work with that data, use `--environment production` and a
25
+ separate context at login and on subsequent commands and MCP configuration.
26
+ See [environment selection](docs/CLI.md#install-and-connect); a context name
27
+ alone does not change the environment.
28
+
22
29
  ## What you can do
23
30
 
24
31
  | Area | Features |
@@ -33,6 +40,12 @@ Installing the package does not grant application access.
33
40
  Availability follows your account, the permissions you approve and the service's
34
41
  current capabilities. [Memory & Graph guide](https://github.com/PulsarInteractive/geniustasker-agent-tools/blob/main/docs/MEMORY.md).
35
42
 
43
+ In a terminal, the CLI checks for a newer release at most once per UTC day and
44
+ installed version. It never installs automatically. Use `geniustasker update check
45
+ --json` to check explicitly, and `geniustasker update install` to update a global
46
+ npm installation after closing other CLI commands and local MCP servers.
47
+ See [updates and managed installations](docs/CLI.md#updates).
48
+
36
49
  ## Connect your AI assistant
37
50
 
38
51
  For a stdio MCP host, use this after signing in:
@@ -42,7 +55,7 @@ For a stdio MCP host, use this after signing in:
42
55
  "mcpServers": {
43
56
  "geniustasker": {
44
57
  "command": "npx",
45
- "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.11", "mcp", "--context", "work"]
58
+ "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.13", "mcp", "--context", "work"]
46
59
  }
47
60
  }
48
61
  }
@@ -19,19 +19,21 @@ flowchart LR
19
19
 
20
20
  ## Module responsibilities
21
21
 
22
- | Module | Responsibility |
23
- | --------------------- | --------------------------------------------------------------------------- |
24
- | `cli.mjs` | Argument validation, context/environment selection, output and exit status |
25
- | `login.mjs` | Browser PKCE consent, loopback callback validation and optional device flow |
26
- | `store.mjs` | Private local files, atomic replacement and inter-process locking |
27
- | `client.mjs` | Origin-bound sessions, serialized renewal, profile selection and reads |
28
- | `transport.mjs` | Allowed origins/routes, timeouts, size limits and sanitized API failures |
29
- | `commands.mjs` | Validated command envelopes and durable immutable operation journals |
30
- | `profiles.mjs` | Bounded profile discovery, creation, restriction and selection |
31
- | `changes.mjs` | Validated incremental reads and bounded, cancellable waits |
32
- | `mcp.mjs` | Strict tool schemas and protocol-safe responses over stdio |
33
- | `errors.mjs` | Stable errors, safe serialization and CLI exit codes |
34
- | `command-catalog.mjs` | Generated public interface definitions and limits |
22
+ | Module | Responsibility |
23
+ | --------------------- | ------------------------------------------------------------------------------------ |
24
+ | `cli.mjs` | Argument validation, context/environment selection, output and exit status |
25
+ | `login.mjs` | Browser PKCE consent, loopback callback validation and optional device flow |
26
+ | `store.mjs` | Private local files, atomic replacement and inter-process locking |
27
+ | `client.mjs` | Origin-bound sessions, serialized renewal, profile selection and reads |
28
+ | `transport.mjs` | Allowed origins/routes, timeouts, size limits and sanitized API failures |
29
+ | `commands.mjs` | Validated command envelopes and durable immutable operation journals |
30
+ | `profiles.mjs` | Bounded profile discovery, creation, restriction and selection |
31
+ | `changes.mjs` | Validated incremental reads and bounded, cancellable waits |
32
+ | `mcp.mjs` | Strict tool schemas and protocol-safe responses over stdio |
33
+ | `errors.mjs` | Stable errors, safe serialization and CLI exit codes |
34
+ | `update.mjs` | Anonymous bounded npm discovery, daily attempt cache and explicit global npm updates |
35
+ | `update-runtime.mjs` | Concurrent CLI/MCP activity leases and an exclusive installation barrier |
36
+ | `command-catalog.mjs` | Generated public interface definitions and limits |
35
37
 
36
38
  ## Authentication and renewal
37
39
 
package/docs/CHATGPT.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  Use the hosted MCP connector to work with GeniusTasker from ChatGPT. Your computer does not need to run the CLI. Access still requires an admitted GeniusTasker account.
4
4
 
5
+ The URL below targets production, where agent access is enabled for admitted
6
+ accounts. This is the same environment used by TestFlight. Sign in with the
7
+ intended account and review its resource permissions. The beta CLI's development
8
+ default does not change this hosted connector's environment, and connecting a
9
+ custom server does not imply approval in OpenAI's public directory.
10
+
5
11
  ## Connect your account
6
12
 
7
13
  1. In ChatGPT on the web, open **Plugins → Add → Add custom MCP server**.
package/docs/CLI.md CHANGED
@@ -5,6 +5,53 @@ comment, ask questions and keep a useful handoff. Your account and project
5
5
  permissions remain the limit. GeniusTasker does not run your agent or bill its
6
6
  external model tokens.
7
7
 
8
+ ## Custom metric definitions
9
+
10
+ For custom measurement definitions, use `metrics list --scope project:ID --json`
11
+ or `metrics list --scope personal:OWNER --json` (`OWNER` is identity's
12
+ `actor.ownerId`). Current capabilities must advertise the feature and the
13
+ separate `metrics:read` / `metrics:write` grants. `metric.create`,
14
+ `metric.update`, `metric.delete`, `metric.record`, `metric.correct` and
15
+ `metric.void`, plus the discoverable `metric.goal.create/update/delete` commands,
16
+ use the standard `commands prepare/execute/retry` journal.
17
+ MCP exposes `tasker_read_metrics` and `tasker_edit_metrics`.
18
+ Read the [metric configuration guide](../skills/geniustasker/references/metrics.md)
19
+ or `workflow show --topic metrics --json` before choosing the measurement meaning.
20
+ For observations or previous correction snapshots, choose `--collection`
21
+ explicitly; definitions remain the default. Read the
22
+ [observation guide](../skills/geniustasker/references/metrics-observations.md)
23
+ before recording or correcting evidence. For linked goals, select `metricGoals`
24
+ or `personalMetricGoals` and read the [metric goal guide](../skills/geniustasker/references/metric-goals.md).
25
+ A goal is a separate explicit command; definitions and observations never create
26
+ one implicitly. Goal thresholds are decimal strings, fixed windows use source
27
+ observation time, and `Pending` progress is not final. None of these commands
28
+ starts an automatic collector or executes an external agent.
29
+
30
+ ## Task protocols
31
+
32
+ Discover `taskTemplates`, `protocolInstances` and the `protocol.*` commands in
33
+ capabilities before using this workflow. Protocols are versioned procedures for
34
+ Details projects, with stable task keys, dependencies and acceptance criteria.
35
+
36
+ ```sh
37
+ geniustasker workflow show --topic protocols --json
38
+ geniustasker protocols preview --file protocol-preview.json --context work --json
39
+ ```
40
+
41
+ The file contains `scope`, `protocolVersionId` and `bindings` with `instanceId`,
42
+ matching `scope`, current `epoch`, a timezone-qualified `anchor` and primitive
43
+ `values`. Preview performs one read-only POST with `tasks:read`, returns at most
44
+ 20 steps and never creates tasks. For another page, preserve these fields and
45
+ add `after: nextAfter` plus the returned `digest`. Each call consumes the normal
46
+ read budget. There is no automatic pagination or apply loop.
47
+
48
+ Use `protocol.publish/start/apply/cancel` through the existing `commands prepare`
49
+ and `commands retry` workflow only for requested changes. `protocol.apply` takes
50
+ `digest`, `from` and `count` (1–20) with the current instance revision. `Applied`
51
+ means the tasks exist, not that their work is done. Cancellation preserves tasks
52
+ already created. Follow the [protocol guide](../skills/geniustasker/references/protocols.md)
53
+ for binding, importance, permissions, recovery and hosted MCP equivalents.
54
+
8
55
  ## Install and connect
9
56
 
10
57
  Requires Node.js 22.13 or newer. Install the beta:
@@ -21,10 +68,28 @@ permissions, then approve the connection. The CLI receives a one-use code with
21
68
  PKCE; it never asks for your password. The consent page does not load the app tutorial. Decline there or use Ctrl-C to stop.
22
69
  If the browser cannot open, use the link printed in your terminal.
23
70
 
24
- **This beta defaults to the development environment.** Your account must be
25
- admitted to the beta; installing the package does not grant access. Production
26
- agent access is closed. Use `--environment production` only when that rollout is
27
- announced. No subscription purchase is performed by the CLI.
71
+ **This beta defaults to the development environment.** Production agent access
72
+ is enabled for admitted accounts; installation alone does not grant access in
73
+ either environment. Account admission, project membership, subscription and
74
+ browser consent still apply. No subscription purchase is performed by the CLI.
75
+
76
+ TestFlight uses production. To work on that same application's data, choose a
77
+ separate context and pass `--environment production` at login **and on every
78
+ subsequent CLI or local MCP invocation**:
79
+
80
+ ```sh
81
+ geniustasker auth login --environment production --context tasker-beta --browser chrome
82
+ geniustasker whoami --environment production --context tasker-beta --json
83
+ geniustasker projects list --environment production --context tasker-beta --json
84
+ geniustasker mcp --environment production --context tasker-beta
85
+ ```
86
+
87
+ A context name does not select an environment. Existing development sessions do
88
+ not become production sessions, and changing an environment does not migrate
89
+ records or expand consent. Keep the chosen environment/context in the host's
90
+ MCP arguments too. Inspect identity before making changes; an empty project
91
+ list is not a reason to switch accounts or environments automatically. Use the
92
+ same flags for logout when revoking that connection.
28
93
 
29
94
  For a remote machine, use `geniustasker auth login --flow device --no-browser`.
30
95
  For Chrome specifically, use `--browser chrome`. `--context work` creates a
@@ -55,7 +120,7 @@ launching stdio servers with this entry (adjust environment/context as needed):
55
120
  "mcpServers": {
56
121
  "geniustasker": {
57
122
  "command": "npx",
58
- "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.11", "mcp", "--context", "work"]
123
+ "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.13", "mcp", "--context", "work"]
59
124
  }
60
125
  }
61
126
  }
@@ -442,3 +507,86 @@ it visible to that Graph's readers and requires the user's authorization.
442
507
  Read the full current record before editing and preserve its revision.
443
508
 
444
509
  For project-owned reusable task selections, see [Shared project filters](PROJECT_FILTERS.md).
510
+
511
+ ## Updates
512
+
513
+ ```sh
514
+ geniustasker update check --json
515
+ geniustasker update check --channel stable --json
516
+ # Close local MCP servers and let other CLI commands finish before installing.
517
+ geniustasker update install --json
518
+ ```
519
+
520
+ The default channel follows the installed version: a `-beta.N` release checks
521
+ `beta`; a stable release checks `latest` and rejects prereleases on that tag.
522
+ `--channel beta|stable` selects a channel for that invocation. The updater pins the
523
+ checked version and never downgrades. Switching from beta to stable therefore
524
+ waits for a stable version newer than the installed beta. The returned
525
+ `installedVersion`, `availableVersion`, `channel` and `updateAvailable` explain
526
+ that comparison.
527
+
528
+ After a successful interactive command, automatic discovery makes at most one
529
+ anonymous registry attempt per UTC day and installed version, even across
530
+ concurrent terminals or a failed check. Its deadline is 900 ms. The notice goes
531
+ to stderr; the command result is unchanged. MCP, `--json`, redirected output,
532
+ CI, help and local-only inspection/preparation commands never check automatically.
533
+ Set `GENIUSTASKER_NO_UPDATE_CHECK=1` to disable terminal discovery. Explicit checks
534
+ remain available and have a 1.5-second deadline. No account credentials are sent
535
+ to npm, and no GeniusTasker API quota is used.
536
+
537
+ `update install` supports only the active global npm installation. It checks
538
+ `npm root --global` against the actual package path; source checkouts, npm links,
539
+ project dependencies, npx copies and other managed installations require their
540
+ own update workflow. An npx pin in an MCP configuration does not change when a
541
+ global installation is updated. The installer fixes both npm registry settings to
542
+ `https://registry.npmjs.org`, disables lifecycle scripts, enforces Node engines,
543
+ and verifies the installed package name/version. It never elevates privileges.
544
+ The npm log is not copied into CLI output.
545
+
546
+ An installation barrier prevents replacement while another command or local MCP
547
+ process from this installation is active. Ordinary commands still run in
548
+ parallel. A running MCP process must be closed, even if currently idle; restart
549
+ it after the update. Stop older clients that predate this activity guard as well.
550
+ Credentials and pending immutable command journals are neither read nor modified
551
+ by the updater. An update does not replay any saved operation.
552
+
553
+ The small disposable discovery markers live in
554
+ `~/.cache/geniustasker/cli-updates`; normal checks retain only the current and
555
+ previous UTC day, inspecting at most 64 entries per pass. Runtime activity lives
556
+ separately under `~/.cache/geniustasker/cli-runtime/<installation-hash>/active`.
557
+ Only records belonging to positively dead processes are reclaimed during an
558
+ installation. Unknown files and possibly reused PIDs conservatively block it.
559
+ Do not clear runtime activity while clients are running.
560
+
561
+ If an installer is interrupted, its empty `install.lock` directory in that same
562
+ installation-specific runtime directory remains. First confirm that every local
563
+ GeniusTasker client and npm installer has stopped, then remove only that empty
564
+ lock directory with `rmdir`. Do not delete credentials, journals, or active-process
565
+ records. After `update_install_unconfirmed`, inspect the global installed version
566
+ and package integrity before retrying; an interrupted npm operation may already
567
+ have changed files. A successful result uses `state: installed`; an already
568
+ current or newer installation uses `state: up_to_date`.
569
+
570
+ Protocol command schemas are available offline with
571
+ `geniustasker commands describe --kind protocol.publish --json` (also
572
+ `protocol.start`, `protocol.apply`, `protocol.cancel`). `tasker_command_help`
573
+ provides the same local MCP guidance. Use the required fields and nested limits;
574
+ current authorization and semantic validation remain server-side.
575
+
576
+ ## Agent runs
577
+
578
+ Discover the `agentRuns` collection and `run.claim`, `run.checkpoint`, `run.patch`,
579
+ `run.finish` commands before using them. Inspect each schema with
580
+ `geniustasker commands describe --kind run.claim --json`, then use the normal
581
+ immutable command journal. [The run workflow](../skills/geniustasker/references/agent-runs.md)
582
+ explains separate run/task revisions, real checkpoints, stale leases, human
583
+ takeover and recovery. Finishing a run does not mark its task Done; no background
584
+ agent execution or monitoring is implied.
585
+
586
+ For an explicitly instrumented host, `geniustasker runs event --file event.json
587
+ --context work --json` maps one saved real event to those same run commands.
588
+ Add `--prepare` to journal it without sending. Keep its stable `eventId` and
589
+ `occurredAt`; retries use the normal command journal. Local MCP exposes
590
+ `tasker_run_event`. A `process_exited` event only requests review, with explicit
591
+ next steps. See [host event fields, examples and recovery](../skills/geniustasker/references/host-events.md)
592
+ before connecting a host callback; no host hook is installed automatically.
@@ -4,11 +4,31 @@ Choose either direct MCP configuration or the plugin bundle, to avoid registerin
4
4
  the same server twice. Authenticate once per chosen local context. Permissions
5
5
  are selected in the browser and enforced by the service on every request.
6
6
 
7
+ ## Choose the environment
8
+
9
+ The beta CLI and shipped plugin/MCP examples default to development. Production
10
+ access is enabled for admitted accounts and uses the same data as TestFlight.
11
+ For production, use a separate context and include `--environment production`
12
+ in both login and the MCP server arguments. Context names do not select an
13
+ environment; existing development sessions stay separate. Never switch an
14
+ environment or replace a connection just to get around an access refusal.
15
+
16
+ For example, to connect a production context to a direct Codex MCP server:
17
+
18
+ ```sh
19
+ npx -y @pulsarinteractive/geniustasker@0.1.0-beta.13 auth login --environment production --context tasker-beta
20
+ codex mcp add geniustasker-production -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.13 mcp --environment production --context tasker-beta
21
+ ```
22
+
23
+ Use either this configuration or the development example below for the intended
24
+ account. If intentionally keeping both, name them distinctly and verify identity
25
+ before working. Adding the production example does not retarget a bundled plugin.
26
+
7
27
  ## Codex: direct MCP
8
28
 
9
29
  ```sh
10
- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.11 auth login --context work
11
- codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.11 mcp --context work
30
+ npx -y @pulsarinteractive/geniustasker@0.1.0-beta.13 auth login --context work
31
+ codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.13 mcp --context work
12
32
  ```
13
33
 
14
34
  Restart the host as needed, then inspect its MCP list. Ask the agent to read its
@@ -39,6 +59,9 @@ without skills, and skills can use the CLI when an MCP host is not configured.
39
59
  The root `plugin.json` and `mcp.json` follow Agent Plugins 1.0.0. The bundled MCP
40
60
  runs locally over stdio and pins a published npm version. Node and npm must be
41
61
  available in the execution environment. Authenticate the `work` context first.
62
+ Its shipped arguments target development; for production, use a host-supported
63
+ configuration override or the explicit direct MCP configuration above. Do not
64
+ assume that a production login changes the plugin's environment.
42
65
 
43
66
  The repository also has `.agents/plugins/marketplace.json` for local distribution:
44
67
 
package/docs/MEMORY.md CHANGED
@@ -1,5 +1,14 @@
1
1
  # Memory and Graph
2
2
 
3
+ Graph creation, node/edge changes and Graph reads through CLI/MCP/connectors
4
+ require Starter or Pro for the acting user, plus the normal resource permissions.
5
+ The space owner's plan does not grant a collaborator this capability. Document
6
+ pages, attachments and document references retain their independent access.
7
+ `memory_graph_premium_required` is a subscription refusal, not a reason to switch
8
+ tools or profiles. After downgrade, ordinary application sync and account export
9
+ remain available for existing data. Discover the current server capabilities;
10
+ package installation alone does not activate a server release.
11
+
3
12
  Memory stores structured documents independently of projects. Graph connects
4
13
  nodes and links them to a page or a stable document block. These commands require
5
14
  the matching deployed service capabilities; check `geniustasker capabilities --json` before using them.
package/docs/WORKFLOWS.md CHANGED
@@ -2,6 +2,7 @@
2
2
 
3
3
  | What you want | Guide topic | Operations |
4
4
  | --------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------- |
5
+ | Reuse a task procedure | `protocols` | Inspect immutable versions, bind variables, preview and explicitly materialize bounded batches |
5
6
  | Work on a project | `projects` | Read project/member configuration; create/edit/archive/restore tasks; create and plan tickets in existing backlogs/sprints |
6
7
  | Prepare a shared workflow | `projects` | Project tags and saved filters; sprint, recurring schedule and workflow lifecycle |
7
8
  | Collaborate | `projects` | Comments, work reports, questions, exact action approvals and member goals |
@@ -15,6 +16,13 @@ Discover commands before editing. A readable collection does not imply a matchin
15
16
  write command. See [projects and planning](PLANNING.md) for lifecycle commands.
16
17
  Membership and consent changes remain in the application.
17
18
 
19
+ For importance, use the `projects` guide and
20
+ [the classification workflow](../skills/geniustasker/references/importance.md).
21
+ The four values are `Minor`, `Normal`, `Important` and `Critical`. Importance is
22
+ impact, independently of urgency or hierarchy. Agents justify the two higher
23
+ levels and preserve human classifications. Check live field availability before
24
+ using them; these fields do not establish a particular notification or Flutter UI.
25
+
18
26
  ## Example requests
19
27
 
20
28
  - “Find my tasks in the current sprint and summarize what blocks them.”
@@ -35,3 +43,9 @@ Existing project agent contributions must be enabled by an authorized member.
35
43
  New projects created with projects:write start with contributions enabled. No tool
36
44
  can grant itself membership, approve an action as a human, or bypass account
37
45
  [limits](LIMITS.md).
46
+
47
+ Read [Task protocols](../skills/geniustasker/references/protocols.md) for exact preview, binding and immutable recovery examples.
48
+
49
+ For real agent claims, checkpoints, scoped task patches and completion, read
50
+ [Agent runs](../skills/geniustasker/references/agent-runs.md). A recorded run does
51
+ not start or monitor an external agent automatically.
@@ -1,3 +1,3 @@
1
1
  [mcp_servers.geniustasker]
2
2
  command = "npx"
3
- args = ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.11", "mcp", "--context", "work"]
3
+ args = ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.13", "mcp", "--context", "work"]
package/examples/mcp.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "mcpServers": {
3
3
  "geniustasker": {
4
4
  "command": "npx",
5
- "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.11", "mcp", "--context", "work"]
5
+ "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.13", "mcp", "--context", "work"]
6
6
  }
7
7
  }
8
8
  }
package/mcp.json CHANGED
@@ -4,7 +4,7 @@
4
4
  "geniustasker": {
5
5
  "type": "stdio",
6
6
  "command": "npx",
7
- "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.11", "mcp", "--context", "work"]
7
+ "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.13", "mcp", "--context", "work"]
8
8
  }
9
9
  }
10
10
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pulsarinteractive/geniustasker",
3
- "version": "0.1.0-beta.11",
3
+ "version": "0.1.0-beta.13",
4
4
  "private": false,
5
5
  "description": "GeniusTasker delegated CLI and local agent tools",
6
6
  "type": "module",
@@ -46,7 +46,7 @@
46
46
  "@eslint/js": "10.0.1",
47
47
  "@modelcontextprotocol/client": "2.3.1",
48
48
  "ajv": "8.20.0",
49
- "eslint": "10.11.0",
49
+ "eslint": "10.15.0",
50
50
  "globals": "17.12.0",
51
51
  "prettier": "3.9.9"
52
52
  },
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.11",
4
+ "version": "0.1.0-beta.13",
5
5
  "description": "Track project work and independent product memories with your own agents.",
6
6
  "author": {
7
7
  "name": "Pulsar Interactive"