@pulsarinteractive/geniustasker 0.1.0-beta.2 → 0.1.0-beta.4

package/docs/CLI.md

@@ -1,4 +1,4 @@
-# GeniusTasker CLI & MCP · private beta
+# GeniusTasker CLI and MCP reference
 
 Connect your own AI tools to your projects: read progress, work on tickets,
 comment, ask questions and keep a useful handoff. Your account and project
@@ -51,7 +51,7 @@ launching stdio servers with this entry (adjust environment/context as needed):
   "mcpServers": {
     "geniustasker": {
       "command": "npx",
-      "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.2", "mcp", "--context", "work"]
+      "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.4", "mcp", "--context", "work"]
     }
   }
 }
@@ -156,7 +156,6 @@ Protocol references: [OAuth device authorization](https://www.rfc-editor.org/rfc
 [OAuth metadata](https://www.rfc-editor.org/rfc/rfc8414), and the
 [official MCP TypeScript SDK](https://github.com/modelcontextprotocol/typescript-sdk).
 
-
 ## Prepare, execute and recover writes
 
 Request the relevant permissions when connecting, for example:
@@ -222,8 +221,7 @@ record bodies; read them separately if your grant permits it.
 Local validation includes separate processes sharing one write, immutable retry
 after lost responses, strict inputs, receipt validation and an official MCP
 client communicating through stdio to actual Worker/SQLite domain services.
-Hosted owner acceptance and named product integrations remain separate gates.
-
+Compatibility with each agent host requires its own connection test.
 
 ## Agent profiles and terminal identity
 
@@ -267,7 +265,6 @@ the previous usable credentials; read the profile list again. An unknown rotatio
 outcome requires logout/login, just like an unknown refresh. Credentials never
 appear in selection results, CLI output, MCP tool results or package artifacts.
 
-
 ## Ask a human on a ticket
 
 Request `questions:write` explicitly when connecting; an existing comments grant
@@ -314,7 +311,6 @@ an open anonymous question's public checkpoint.
 profile can close only questions it created. It cannot answer on behalf of its
 owner, impersonate another profile, or use a poll result as new authorization.
 
-
 ## Work updates and handoffs
 
 Prepare `task.report` through the normal command journal with the current task
@@ -329,7 +325,6 @@ comment. Completing/reopening a ticket clears its current phase. A report is
 progress information, not approval or proof independently verified by Tasker.
 Correct published reports with a new report; never rewrite an older receipt.
 
-
 ## Ask for approval of one precise action
 
 Connect with `approvals:write` explicitly, alongside the read grants needed to
@@ -374,8 +369,8 @@ Only the CLI/MCP source, its generated public command catalog, bundled agent ski
 and the selected guide/plugin files are distributed. Application source, infrastructure configuration,
 private product documents, test identities and credentials are excluded. No
 installation script runs and no background daemon or telemetry is installed.
-The package is distributed for the GeniusTasker beta; no open-source license has
-been granted. The public agent-tools repository contains only the standalone client.
+The standalone client and skills are distributed under the MIT license.
+Third-party components retain their original licenses.
 
 ## Independent memories
 
@@ -394,7 +389,31 @@ source provenance. Preserve IDs when editing; do not relabel a proposal as a
 verified fact. `pages --id ID` also reads one page. A targeted read has no change
 cursor; obtain one from a complete collection inventory when watching updates.
 Commands `memory.create/update/delete` and `memory.page.create/update/delete`
-require `memory:write`. For a new space, choose one UUID for its root ID, scope
+require `memory:write`. For a new space, choose one UUID v4 for its root ID, scope
 suffix and initial epoch, then use the returned epoch/revision for later writes.
 All edits use the same local command journal and optimistic revision checks as
 project commands. Never copy private source files into this npm package.
+
+## Page access and visual Graph levels
+
+A memory can define `contentRoles` (stable IDs and display names). Membership
+assignments are managed in the application. Page `visibility` is `inherit`,
+`restricted`, or `private`; `readRoles` selects defined roles for a restricted
+page. Restrictions apply through parent folders and to attached files. Content
+roles never grant editing rights. Only memory administrators can change page
+restrictions or move existing pages between parents. Never change sharing as a
+workaround for denied reads.
+
+Resources, search, references and media reads enforce current page access.
+After permission changes, discard cached results and restart incremental reads
+when `reset_required` is returned. An offline copy cannot establish current
+access. Keep Graph nodes and their own notes when a linked page is unavailable.
+
+Nodes accept `imageAssetId` for an image uploaded to the same memory and
+`detailLevel`: `auto`, `overview`, `identity`, or `detail`. The node `kind` is its content type. Overview shows products, projects and brands;
+Identities shows characters, people and entities (never places or scenes). Details
+shows every type and supports type/status filters. Prefer `auto`; an explicit
+`overview` can highlight another type there. Display level is not authorization.
+Upload only approved imagery. Attaching a private image to a shared Graph makes
+it visible to that Graph's readers and requires the user's authorization.
+Read the full current record before editing and preserve its revision.

package/docs/INTEGRATIONS.md

@@ -7,8 +7,8 @@ are selected in the browser and enforced by the service on every request.
 ## Codex: direct MCP
 
 ```sh
-npx -y @pulsarinteractive/geniustasker@0.1.0-beta.2 auth login --context work
-codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.2 mcp --context work
+npx -y @pulsarinteractive/geniustasker@0.1.0-beta.4 auth login --context work
+codex mcp add geniustasker -- npx -y @pulsarinteractive/geniustasker@0.1.0-beta.4 mcp --context work
 ```
 
 Restart the host as needed, then inspect its MCP list. Ask the agent to read its
@@ -43,7 +43,7 @@ available in the execution environment. Authenticate the `work` context first.
 The repository also has `.agents/plugins/marketplace.json` for local distribution:
 
 ```sh
-codex plugin marketplace add alexisnaud/geniustasker-agent-tools
+codex plugin marketplace add PulsarInteractive/geniustasker-agent-tools
 ```
 
 Use the host's Plugins interface to select and enable GeniusTasker. This local

package/docs/LIMITS.md

@@ -0,0 +1,49 @@
+# Usage limits
+
+CLI and MCP share your GeniusTasker account limits. Creating more agent profiles,
+opening more terminals or changing devices does not give additional allowance.
+The service reports current limits through `geniustasker capabilities --json`.
+
+## Agent requests
+
+| Allowance                     |  Free |            Premium |                Pro |
+| ----------------------------- | ----: | -----------------: | -----------------: |
+| Requests per 60 seconds       |    30 |                120 |                300 |
+| Write requests per 60 seconds |     5 |                 20 |                 60 |
+| Monthly request credits       | 5,000 | No monthly ceiling | No monthly ceiling |
+| Monthly write requests        |   500 | No monthly ceiling | No monthly ceiling |
+
+Write requests also count toward the request limit. For Free accounts, a read
+costs one monthly credit and a write costs five; both monthly limits must have
+capacity. Monthly counters reset at the beginning of the next calendar month
+in UTC. Premium appears as `Starter` in API responses; Pro appears as `Pro`.
+
+These are the current service settings, not a pricing commitment. Short-window
+limits provide traffic protection and can apply approximately by location;
+clients must follow the service response. Resource limits for projects, members,
+Memory, storage and attachments are separate and still apply. Availability also
+requires account approval and an explicitly granted agent connection.
+
+## When a limit is reached
+
+| Response                         | Next step                                                             |
+| -------------------------------- | --------------------------------------------------------------------- |
+| Temporary rate limit (`429`)     | Wait for the reported retry time; do not loop or open another context |
+| Free monthly allowance exhausted | Wait for the reported reset or change plan when available             |
+| Resource capacity reached        | Free capacity or change plan before creating more data                |
+| Permission refused (`403`)       | Ask the account or resource owner to review access                    |
+| Interrupted write                | Keep its operation ID and retry that same operation                   |
+
+The client preserves a write's immutable journal for safe retries. A timeout is
+not proof that the write failed. Read the latest record after a revision conflict
+before preparing a new operation.
+
+## Keep reads focused
+
+- List one page of spaces or resources at a time and follow its cursor as needed.
+- Use Memory search and its page index before downloading document bodies.
+- Explore a bounded Graph neighborhood instead of loading every node.
+- Reuse checkpoints for change reads; honor `restart_read` when the service asks.
+- Local cache hits revalidate access. Revoked permissions never become an offline grant.
+
+See [CLI reference](CLI.md) for commands and [Memory & Graph](MEMORY.md) for examples.

package/docs/MEMORY.md

@@ -0,0 +1,38 @@
+# Memory and Graph
+
+Memory stores structured documents independently of projects. Graph connects
+nodes and links them to a page or a stable document block. These commands require
+the matching deployed service capabilities; check `geniustasker capabilities --json` before using them.
+
+```sh
+geniustasker memory search --scope memory:ID --query "release checklist" --json
+geniustasker graph explore --scope memory:ID --center NODE_ID --depth 2 --json
+geniustasker memory resolve --scope memory:ID --page PAGE_ID --block BLOCK_ID --json
+```
+
+The matching MCP tools are `tasker_search`, `tasker_graph` and `tasker_reference`.
+Search is paginated; Graph returns a bounded neighborhood and reports truncation.
+Use `resources list` for complete selected records and `commands describe` for
+contract-derived node/edge write fields. Writes keep the same immutable journal.
+
+References recheck current access. If a friend withdraws access, the content
+becomes unavailable while the node and its own text remain intact. A new grant
+restores resolution; a link never grants access by itself. The client does not
+cache resolved content. Discover capabilities before selecting a workflow.
+
+## Attachments
+
+Discover `mediaUploadAvailable` and `maxUploadBytes` first. Prepare one explicitly
+selected file with `media prepare --scope memory:ID --epoch EPOCH --file diagram.png
+--content-type image/png`, then `media upload --operation UUID`. Keep that operation
+ID after a timeout: retries verify the same bytes and do not create a second file.
+Use the returned `assetId` in an image or attachment block. Images, PDF and plain
+text are supported up to 15 MB; storage is charged to the Memory owner.
+
+MCP equivalents are `tasker_media_prepare`, `tasker_media_upload`,
+`tasker_media_action` and `tasker_media_download`. Downloads require an explicit
+new local path and fresh read access. Removal leaves document blocks in place
+so people can see and repair the unavailable attachment. No credentials, URLs
+with public access tokens or file bytes are embedded in documents.
+
+See the [CLI reference](CLI.md) for document blocks, page roles, node types, images and detailed command examples.

package/docs/OPENAI.md

@@ -9,20 +9,19 @@ Nothing here is an OpenAI directory approval or a hosted remote MCP endpoint.
 
 ## Hosted plugin milestone
 
-| Work | Acceptance |
-| --- | --- |
-| HTTPS Streamable HTTP MCP adapter | Real initialize, tools/list and tool calls; reuse existing product commands and quotas |
-| MCP OAuth compatibility | Protected-resource and authorization discovery, audience/resource binding, supported client registration, allowed callbacks, PKCE, expiry and revocation |
-| Host authentication | Real browser consent, resource-limited reads, denied access and reauthentication |
-| Writes | Explicit grants, correctly annotated tools, immutable retries and conflicts; no blanket approval |
-| Optional company-knowledge search | Authorized search/fetch with user-openable citations and bounded results |
-| Plugin review | Accurate install copy, privacy/terms links, domain verification, real test account, honest limitations |
+| Work                              | Acceptance                                                                                                                                               |
+| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| HTTPS Streamable HTTP MCP adapter | Real initialize, tools/list and tool calls; reuse existing product commands and quotas                                                                   |
+| MCP OAuth compatibility           | Protected-resource and authorization discovery, audience/resource binding, supported client registration, allowed callbacks, PKCE, expiry and revocation |
+| Host authentication               | Real browser consent, resource-limited reads, denied access and reauthentication                                                                         |
+| Writes                            | Explicit grants, correctly annotated tools, immutable retries and conflicts; no blanket approval                                                         |
+| Optional company-knowledge search | Authorized search/fetch with user-openable citations and bounded results                                                                                 |
+| Plugin review                     | Accurate install copy, privacy/terms links, domain verification, real test account, honest limitations                                                   |
 
 The current CLI OAuth flow is a foundation; it is not proof that every hosted
 MCP client's registration and resource-discovery requirements are implemented.
-Do not add a pretend `/mcp` URL or registered OpenAI application ID to manifests.
-Only map a registered server after it exists and passes host acceptance. Embedded
-UI is optional and should follow actual product tasks.
+A hosted manifest requires a deployed and tested MCP server and a registered
+application identifier. Embedded UI is optional.
 
 The remotely hosted backend can remain private. A public source repository is a
 client distribution and review surface, not an access grant to user data.

package/docs/RELEASING.md

@@ -1,7 +1,7 @@
 # Release process
 
 1. Update package, lockfile, MCP server version, plugin version and example pins together.
-2. Review public contract/skill changes and run `npm ci`, `npm test`, `npm run check` and `npm audit`.
+2. Review public contract/skill changes and run `npm ci`, `npm run verify` and `npm audit`.
 3. Inspect `git diff` and the complete `npm pack --dry-run --json` list. No private repository history or product files may enter this repo.
 4. Pack and inspect the actual archive. `npm publish <archive> --access public --tag beta` requires the maintainer's npm authentication.
 5. Confirm registry version/tag/integrity, install using a fresh cache and exercise real MCP through an explicitly authorized beta account. Keep private results outside this repository.
@@ -11,5 +11,13 @@ CI runs tests and package/privacy checks. It never publishes npm or deploys the
 service. Future trusted publishing should use a reviewed OIDC setup rather than
 committing an npm token; it is not configured by this repository.
 
-The `v0.1.0-beta.1` tag preserves the original published runtime. Its informational
-`doctor.publication` text is outdated; beta.2 corrects it. npm versions are immutable.
+Published npm versions are immutable. Use a new version for package changes.
+
+Canonical repository: https://github.com/PulsarInteractive/geniustasker-agent-tools
+
+The npm package page and unqualified installs use the `latest` tag. After verifying
+the release archive, explicitly update both the intended channel and the default
+version; do not leave `latest` pointing at a superseded license or README. Verify
+`npm view @pulsarinteractive/geniustasker dist-tags license repository.url --json`
+and inspect the actual npm page. An old published archive is immutable; tags do
+not rewrite its contents.

package/docs/TESTING.md

@@ -0,0 +1,52 @@
+# Testing
+
+## Run the quality checks
+
+```sh
+npm ci
+npm run verify
+```
+
+`verify` runs formatting, ESLint, tests, package inventory, public-file checks and
+plugin/schema validation. CI runs the same command on Linux and macOS with Node
+22, followed by a dependency vulnerability audit. It has read-only repository
+permissions and no live service credentials.
+
+## Focused checks
+
+```sh
+npm run format:check
+npm run lint
+node --test test/login.test.mjs
+node --test test/process.test.mjs
+npm run check
+npm audit
+```
+
+`npm run format` applies formatting. The generated command catalog and vendored
+schemas are excluded from formatting so their provenance remains stable.
+
+## What the suites cover
+
+| Suite           | Observable guarantees                                                                                           |
+| --------------- | --------------------------------------------------------------------------------------------------------------- |
+| Login           | Consent URL validation, PKCE state/callback handling, denial, cancellation, device-flow deadlines and slow-down |
+| Client/store    | Private file checks, origin binding, serialized renewal and uncertain-token recovery                            |
+| Commands        | Immutable requests, concurrent writes, identity binding, uncertain receipts and conflicts                       |
+| Profiles        | Grant validation, narrowed selection, revision conflicts and rotation uncertainty                               |
+| Changes         | Cursor validation, bounded waits, cancellation and no blind retries after quota or permission failures          |
+| Process         | Real stdio MCP discovery/calls and coordination between separate OS processes                                   |
+| Public boundary | Rejection of excluded files, credentials, symlinks and escaping imports                                         |
+
+Tests create and clean up their own temporary directories and loopback servers.
+They do not require browser sign-in or real project data. Use meaningful scenario
+names, assert behavior at public boundaries and include the failure that motivates
+a regression test. Avoid sleeps as synchronization when an explicit signal works.
+
+## What local tests do not establish
+
+They do not prove admission to the hosted beta, production availability, browser
+provider compatibility on every device or acceptance by each agent host. Release
+verification separately installs the published archive with a fresh cache,
+compares registry integrity and exercises a deliberately authorized test account.
+Record those checks without publishing account data.

package/examples/codex.toml

@@ -1,3 +1,3 @@
 [mcp_servers.geniustasker]
 command = "npx"
-args = ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.2", "mcp", "--context", "work"]
+args = ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.4", "mcp", "--context", "work"]

package/examples/mcp.json

@@ -2,13 +2,7 @@
   "mcpServers": {
     "geniustasker": {
       "command": "npx",
-      "args": [
-        "-y",
-        "@pulsarinteractive/geniustasker@0.1.0-beta.2",
-        "mcp",
-        "--context",
-        "work"
-      ]
+      "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.4", "mcp", "--context", "work"]
     }
   }
 }

package/mcp.json

@@ -4,13 +4,7 @@
     "geniustasker": {
       "type": "stdio",
       "command": "npx",
-      "args": [
-        "-y",
-        "@pulsarinteractive/geniustasker@0.1.0-beta.2",
-        "mcp",
-        "--context",
-        "work"
-      ]
+      "args": ["-y", "@pulsarinteractive/geniustasker@0.1.0-beta.4", "mcp", "--context", "work"]
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pulsarinteractive/geniustasker",
-  "version": "0.1.0-beta.2",
+  "version": "0.1.0-beta.4",
   "private": false,
   "description": "GeniusTasker delegated CLI and local agent tools",
   "type": "module",
@@ -21,13 +21,20 @@
     "CONTRIBUTING.md",
     "SECURITY.md",
     "plugin.json",
-    "mcp.json"
+    "mcp.json",
+    "LICENSE",
+    "THIRD_PARTY_NOTICES.md",
+    "LICENSES/"
   ],
   "scripts": {
     "test": "node --test test/*.test.mjs",
     "check": "node tools/check-package.mjs && node tools/check-public.mjs && node tools/check-plugin.mjs",
-    "prepublishOnly": "npm test && npm run check",
-    "check:public": "node tools/check-public.mjs"
+    "prepublishOnly": "npm run verify",
+    "check:public": "node tools/check-public.mjs",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "lint": "eslint .",
+    "verify": "npm run format:check && npm run lint && npm test && npm run check"
   },
   "dependencies": {
     "@modelcontextprotocol/server": "2.1.0",
@@ -35,10 +42,14 @@
     "zod": "4.6.5"
   },
   "devDependencies": {
+    "@eslint/js": "10.0.1",
     "@modelcontextprotocol/client": "2.1.0",
-    "ajv": "8.20.0"
+    "ajv": "8.20.0",
+    "eslint": "10.11.0",
+    "globals": "17.12.0",
+    "prettier": "3.9.9"
   },
-  "license": "UNLICENSED",
+  "license": "MIT",
   "publishConfig": {
     "access": "public",
     "tag": "beta",
@@ -46,11 +57,11 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/alexisnaud/geniustasker-agent-tools.git"
+    "url": "https://github.com/PulsarInteractive/geniustasker-agent-tools.git"
   },
-  "homepage": "https://github.com/alexisnaud/geniustasker-agent-tools#readme",
+  "homepage": "https://github.com/PulsarInteractive/geniustasker-agent-tools#readme",
   "bugs": {
-    "url": "https://github.com/alexisnaud/geniustasker-agent-tools/issues"
+    "url": "https://github.com/PulsarInteractive/geniustasker-agent-tools/issues"
   },
   "keywords": [
     "geniustasker",

package/plugin.json

@@ -1,18 +1,14 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "geniustasker",
-  "version": "0.1.0-beta.2",
+  "version": "0.1.0-beta.4",
   "description": "Track project work and independent product memories with your own agents.",
   "author": {
     "name": "Pulsar Interactive"
   },
-  "repository": "https://github.com/alexisnaud/geniustasker-agent-tools",
-  "license": "UNLICENSED",
-  "keywords": [
-    "productivity",
-    "projects",
-    "memory"
-  ],
+  "repository": "https://github.com/PulsarInteractive/geniustasker-agent-tools",
+  "license": "MIT",
+  "keywords": ["productivity", "projects", "memory"],
   "extensions": {
     "com.openai": {
       "interface": {
@@ -20,13 +16,8 @@
         "shortDescription": "Projects, progress and memory for your agents",
         "developerName": "Pulsar Interactive",
         "category": "Productivity",
-        "capabilities": [
-          "Read",
-          "Write"
-        ],
-        "defaultPrompt": [
-          "Use GeniusTasker to review my project progress and next tasks."
-        ]
+        "capabilities": ["Read", "Write"],
+        "defaultPrompt": ["Use GeniusTasker to review my project progress and next tasks."]
       }
     }
   }

package/skills/geniustasker/SKILL.md

@@ -25,6 +25,9 @@ List projects, then select a scope from the returned data. Read a collection
 listed in capabilities with `resources list --scope project:ID --collection
 tasks --json`, or MCP `tasker_resources`. Collections include tasks, comments,
 goals, documents, workflows, sprints and summary history when permitted.
+For document indexes, schedules, membership and planning collections, read
+[Focused project reads](references/project-reads.md). `documents` means task
+attachments; `projectDocumentIndex` and `projectDocuments` cover the project library.
 
 Read bounded pages. Follow `nextAfter` even if the project page is empty: ACL
 filtering can hide every item in a scanned page. For resource continuation,
@@ -99,8 +102,6 @@ to evade quotas. If the requested capability is unavailable, say what is pending
 and preserve the useful findings. Final progress should identify the actual
 project/ticket and distinguish completed work, validation and remaining work.
 
-
-
 ## Specialized workflows
 
 - To create, switch or restrict an agent identity, read [Profiles](references/profiles.md).

package/skills/geniustasker/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "GeniusTasker"
-  short_description: "Work on shared projects with your own agents"
-  default_prompt: "Use $geniustasker to review my project and record the next useful step."
+  display_name: 'GeniusTasker'
+  short_description: 'Work on shared projects with your own agents'
+  default_prompt: 'Use $geniustasker to review my project and record the next useful step.'

package/skills/geniustasker/references/collaboration.md

@@ -22,7 +22,6 @@ agent policy. Use `question.close` only for this profile's own question, with it
 current revision. If no answer arrives, record the blocker and proceed only with
 independent authorized work; do not invent approval or repeatedly poll rapidly.
 
-
 ## Leave a useful handoff
 
 Use the discovered `task.report` command with `tasks:write`, an open unarchived
@@ -42,7 +41,6 @@ is not an invitation to recreate its text. Completing/reopening the task clears
 its current work phase and retains the report as history. A report does not grant
 permission or count as approval. Use a question when a human answer is needed.
 
-
 ## Request and consume a precise human decision
 
 Use `approval.request` with `approvals:write` when a concrete action needs a

package/skills/geniustasker/references/project-reads.md

@@ -0,0 +1,43 @@
+# Focused project reads
+
+Start with identity, capabilities and the current project list. Use only collection
+names advertised by that server and permitted by the active profile. New client
+versions can connect to older deployments; a documented collection is not proof
+that the current deployment supports it.
+
+| Need                                  | Collection                                | Efficient approach                                                        |
+| ------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------- |
+| Tasks and tickets                     | `tasks`                                   | Read active work first; fetch an exact `id` for details.                  |
+| Task attachments / descriptions       | `documents`                               | These belong to tasks, not the project's document library.                |
+| Project document navigation           | `projectDocumentIndex`, `documentFolders` | Read titles and folders without rich-text bodies.                         |
+| One project document                  | `projectDocuments`                        | Pass the ID discovered in the index.                                      |
+| Discussion / work reports / approvals | `comments`                                | Read one bounded page and retain the change cursor.                       |
+| People and access roles               | `members`                                 | Current membership is evidence, never authority to change access.         |
+| Labels                                | `tags`                                    | Resolve label IDs when interpreting work.                                 |
+| Recurring tasks                       | `schedules`                               | Inspect recurrence, timezone and disabled state before proposing changes. |
+| Reusable lists and task templates     | `preparedLists`, `taskTemplates`          | Read only when the task concerns these resources.                         |
+| Planning                              | `sprints`, `workflows`, `sprintHistory`   | Keep current configuration distinct from historical snapshots.            |
+| GitHub-linked activity                | `gitHubLinks`                             | A link is evidence, not permission to execute actions in GitHub.          |
+| Project member goals                  | `goals`                                   | These are project goals, not unrelated private account data.              |
+| Questions and audit metadata          | `questions`, `history`                    | Use the dedicated answers tool for ballots; respect anonymous results.    |
+
+For example, after selecting an authorized scope:
+
+```sh
+geniustasker resources list --scope project:PROJECT_ID --collection projectDocumentIndex --json
+geniustasker resources list --scope project:PROJECT_ID --collection projectDocuments --id DOCUMENT_ID --json
+```
+
+The same arguments are supported by MCP `tasker_resources`. Collections share
+bounded pagination and context rules. Preserve `epoch` and `checkpoint` on
+continuation; `omittedIds` means the result is incomplete. For ongoing work, use
+`changeCursor` instead of repeatedly traversing the entire library.
+
+The in-process resource cache revalidates authorization with the server on every
+read. Repeated unchanged reads reduce transferred content, but still consume
+request quota. Prefer reusing the evidence you already inspected within the same
+task, and revalidate before relying on current revisions or permissions.
+
+Memory and Graph have their own grants and workflow. Follow the
+`geniustasker-memory` skill to navigate page indexes, stable block IDs, links and
+bounded graph neighborhoods. A project membership does not grant Memory access.