@josephyan/qingflow-app-user-mcp 0.2.0-beta.5 → 0.2.0-beta.50

package/README.md

@@ -3,13 +3,13 @@
 Install:
 
 ```bash
-npm install @josephyan/qingflow-app-user-mcp@0.2.0-beta.5
+npm install @josephyan/qingflow-app-user-mcp@0.2.0-beta.50
 ```
 
 Run:
 
 ```bash
-npx -y -p @josephyan/qingflow-app-user-mcp@0.2.0-beta.5 qingflow-app-user-mcp
+npx -y -p @josephyan/qingflow-app-user-mcp@0.2.0-beta.50 qingflow-app-user-mcp
 ```
 
 Environment:
@@ -20,9 +20,12 @@ Environment:
 
 This package bootstraps a local Python runtime on first install and then starts the `qingflow-app-user-mcp` stdio MCP server.
 
-Bundled skill:
+Bundled skills:
 
 - `skills/qingflow-app-user`
+- `skills/qingflow-record-crud`
+- `skills/qingflow-task-ops`
+- `skills/qingflow-record-analysis`
 
 Note:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@josephyan/qingflow-app-user-mcp",
-  "version": "0.2.0-beta.5",
+  "version": "0.2.0-beta.50",
   "description": "Operational end-user MCP for Qingflow records, tasks, comments, and directory workflows.",
   "license": "MIT",
   "type": "module",

package/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qingflow-mcp"
-version = "0.2.0b5"
+version = "0.2.0b50"
 description = "User-authenticated MCP server for Qingflow"
 readme = "README.md"
 license = "MIT"
@@ -26,8 +26,10 @@ dependencies = [
   "mcp>=1.9.4,<2.0.0",
   "httpx>=0.27,<1.0",
   "keyring>=25.5,<26.0",
+  "openpyxl>=3.1,<4.0",
   "pydantic>=2.8,<3.0",
   "pycryptodome>=3.20,<4.0",
+  "python-socketio[client]>=5.11,<6.0",
 ]
 
 [project.optional-dependencies]

package/skills/qingflow-app-user/SKILL.md

@@ -1,158 +1,62 @@
 ---
 name: qingflow-app-user
-description: Use Qingflow apps as an operational end user after the MCP is already connected and authenticated. Use when the user wants to create, search, read, update, or delete business records, inspect or manage task-center work, add comments, or perform workflow usage actions inside an existing app. Do not use this skill to design apps, modify schemas, or build a brand new SolutionSpec.
+description: Route Qingflow end-user requests to the right specialized operational skill after the MCP is already connected and authenticated. Use when the task is operational but it is not yet clear whether it is record CRUD or final analysis.
 metadata:
-  short-description: Use Qingflow apps for business data and task operations
+  short-description: Router for Qingflow operational skills
 ---
 
 # Qingflow App User
 
 ## Overview
 
-This skill is for business-user operations inside existing Qingflow apps. It focuses on records, task-center usage, comments, and usage-side workflow actions, not app design or system configuration. If the task is about building or changing app structure, switch to `$qingflow-app-builder`.
-
-Before operating on data, identify whether the task targets `test` or `prod` and read [references/environments.md](references/environments.md). If the user did not specify one, default to `prod`.
-When the task is in `prod`, browser parity matters, or the user says "the page has data but MCP does not", restate the expected `base_url` and `qf_version`, then prefer tools that expose `request_route` so you can confirm the live route before concluding.
-
-## Tool Scope
-
-Primary record and data tools:
-
-- `record_query`
-- `record_query_plan`
-- `record_write_plan`
-- `record_field_resolve`
-- `record_aggregate`
-- `record_create`
-- `record_get`
-- `record_update`
-- `record_delete`
-
-Directory and organization lookup tools when the user is asking about internal members, departments, org structure, ownership, approver candidates, or wants full contact exports:
-
-- `directory_search`
-- `directory_list_internal_users`
-- `directory_list_all_internal_users`
-- `directory_list_internal_departments`
-- `directory_list_all_departments`
-- `directory_list_sub_departments`
-- `directory_list_external_members`
-
-Usage-side collaboration and flow tools when needed:
-
-- `record_comment_*`
-- `task_approve`
-- `task_reject`
-- `task_rollback*`
-- `task_transfer*`
-
-Task-center and inbox tools when the user is asking about pending work, processed work, cc, or workflow workload:
-
-- `task_list`
-- `task_list_grouped`
-- `task_statistics`
-- `task_urge`
-
-Do not use builder-side tools here:
-
-- `app_*`
-- `view_*`
-- `workflow_*`
-- `portal_*`
-- `navigation_*`
-- `package_*`
-- `solution_*`
-
-## Standard Operating Order
-
-1. Ensure auth exists
-2. Ensure workspace is selected
-3. Confirm target app, task scope, and operation type
-4. For org, member, department, approver, or ownership questions, start with `directory_*`
-5. For inbox, pending, processed, cc, or workload questions, start with `task_statistics`, `task_list`, or `task_list_grouped`
-6. When a task query identifies the target record, switch to `record_get` or `record_query` for business data details
-7. For non-trivial record reads, start with `record_query` and use `record_query_plan` first when field ids, filters, or scan scope are uncertain
-8. For non-trivial writes, start with `record_write_plan`, especially when using `fields`
-9. Prefer read-first when changing existing records
-10. Report the affected task ids, record ids, member ids, department ids, or counts after actions
-11. For `prod`, complex forms, attachments, or any unfamiliar schema, prefer `record_create(..., verify_write=true)` or read back immediately after create/update
-
-## Data Rules
-
-- Prefer `record_query` as the default read entry
-- Treat `record_query(list)` as the default wide-table browse and export endpoint; pass explicit `select_columns`, do not expect raw answer arrays there, and let the tool auto-batch columns when the backend per-request field cap is hit
-- Use `request_route` from tool responses to verify the active `base_url` and `qf_version` whenever route mismatches are plausible
-- Use `directory_search` for fuzzy internal lookup across both members and departments
-- Use `directory_list_all_internal_users` when the user explicitly wants a complete internal member list within the current workspace or within a specific department or role
-- Use `directory_list_all_departments` when the user explicitly wants the full department tree or all departments under a root
-- Use `directory_list_internal_departments` for keyword-based department search, not full exports
-- Use `task_statistics` before `task_list` when the user only needs counts
-- Use `task_list_grouped` when worksheet or group buckets matter
-- Use `task_urge` only when the user clearly wants a reminder sent for a pending task
-- Use `record_query_plan` before final statistics or when field selectors are ambiguous
-- For precise record lookup, use `record_get` when `apply_id` is known
-- Use `record_field_resolve` when the user gives field titles and you are not fully sure about the exact schema; do not guess ambiguous fields silently
-- Treat field selectors as schema-first and platform-generic. Prefer exact field titles, then neutral aliases such as `创建时间`, `新增时间`, `负责人`, `部门`, `时间`, or `阶段` only when the tool resolves them clearly. Do not assume CRM shorthand like `销售`, `商机阶段`, `客户全称`, or similar domain shortcuts apply across arbitrary Qingflow apps
-- For updates, inspect current data first unless the user already provided the exact target and patch
-- For deletes, confirm the exact record scope and report the deleted ids
-- When validating business data volume, use `effective_count` over raw backend totals
-- For summary or aggregate conclusions, prefer `strict_full=true`
-- In `prod`, prefer read-first even more strictly and avoid deletes unless the record scope is explicit in the conversation
-- For attachments, first run `file_upload_local`, then pass the returned `attachment_value` into `record_create` or `record_update`; do not try to write local file paths directly into attachment fields
-- For relation fields, first query the target app and resolve the referenced record `apply_id`; do not assume titles, numbers, or business keys can be written directly into a relation field
-- For subtable fields, write a list of row objects keyed by the subfield titles. When updating existing rows, include `rowId` / `row_id` / `__row_id__` only if the source record already exposes it
-- Treat `14/34/35/36` as unsupported direct-write field types in app-user flows:
-  - `14`: time range
-  - `34`: image recognition
-  - `35`: image generation
-  - `36`: document parsing
-- For those unsupported types, stop and explain the limitation instead of inventing payloads
-- Use `record_write_plan` to inspect `write_format.support_level` before non-trivial writes:
-  - `full`: generic scalar/select/date writes are directly supported
-  - `restricted`: member/department/attachment/relation/subtable writes need the documented presteps
-  - `unsupported`: stop and explain the limitation
-- For relation-heavy, attachment, subtable, or production writes, default to `verify_write=true` so field drops are surfaced immediately instead of being reported as success
-
-## Mock and Demo Data
-
-When the user asks for demo data, seed, smoke data, or mock data:
-
-- default to at least `5` records for the relevant entity unless the user asks for fewer
-- keep titles realistic and business-like
-- vary statuses, dates, and categories enough to make views and charts useful
-- if the task is `prod`, do not create mock or smoke data unless the user explicitly asks for it
-
-## Response Interpretation
-
-- low-level list totals from the backend may report `0` while rows are present; prefer `record_query(summary)` or `record_aggregate` for final conclusions
-- `record_query(summary)` and `record_aggregate` expose `completeness`; do not treat partial scans as final conclusions
-- `record_write_plan` is static preflight, not a guarantee that submit will pass runtime linkage or visibility checks
-- `record_create` now returns integer `apply_id`; you can pass that id directly into `record_get`, `record_update`, or `record_delete`
-- `verify_write=true` means the tool read the record back and compared the written fields; if it returns `status=verification_failed` or `ok=false`, do not report the create or update as successful
-- Relation writes are `apply_id`-based; if the user only gives a title, number, or business key, query the target app first and resolve the real record id before writing
-- Task counts and record counts are not interchangeable; a task query reflects task-center workload, not the underlying record total
-- When reporting task results, include the task dimension that was used, such as pending, processed, cc, node, or worksheet
-- Prefer summarizing titles and counts instead of dumping raw answer arrays
-- When records reference other entities, verify references are coherent before reporting success
-- `file_upload_local` may transparently change `effective_upload_kind` and `upload_protocol`; surface those fields when debugging production upload behavior instead of assuming all uploads are direct `PUT`
-
-## Practical Patterns
-
-- Bulk mock data creation: query current data first, run `record_write_plan`, then create missing records
-- Data correction: query, inspect, preflight, update, and re-read
-- Inbox triage: use `task_statistics` first, then `task_list` or `task_list_grouped`, then switch to `record_*` for the underlying record when needed
-- Bottleneck analysis: start with `task_statistics` and `task_list_grouped` before drilling into specific records
-- Workflow collaboration: comment, transfer, or reassign only after identifying the exact record
-- Approval actions: identify the exact record and current node first, then use `task_approve` or `task_reject`; do not guess `nodeId`
-- Demo validation: create at least `5` rows and confirm they are queryable
-- Org export: use `directory_list_all_internal_users` for full member exports and `directory_list_all_departments` for full org-tree exports before mapping owners or departments into record operations
-- Attachment write: upload first, write the returned URL object second, and prefer `verify_write=true`
-- Relation write: query the target app first, capture the referenced record `apply_id`, then write the relation field and verify the readback
-- Production discrepancy triage: compare the response `request_route` with the browser environment before assuming the data query is wrong
+This skill is a lightweight router for operational Qingflow work.
+Assumes MCP is connected, authenticated, and on the correct workspace.
+
+## Default Paths
+
+Route to exactly one of these specialized paths:
+
+1. Record CRUD and import  
+   Switch to [$qingflow-record-crud](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-crud/SKILL.md)
+
+2. Task workflow operations  
+   Switch to [$qingflow-task-ops](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-task-ops/SKILL.md)
+
+3. Analysis  
+   Switch to [$qingflow-record-analysis](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-analysis/SKILL.md)
+
+4. MCP connection / auth / workspace selection  
+   Switch to [$qingflow-mcp-setup](/Users/yanqidong/.codex/skills/qingflow-mcp-setup/SKILL.md)
+
+## Routing Rules
+
+- If the user does not know the target `app_key`, discover apps first with `app_list` or `app_search`, then route to the specialized skill
+- If the app is known but the available data range is unclear, call `app_get` first and inspect `accessible_views`
+- If the task is about browsing, reading, creating, updating, deleting, attachments, relations, subtable writes, member/department-field candidate lookup, code-block field execution, import templates, import capability discovery, import-file verification, authorized local file repair, import execution, or import status, switch to `$qingflow-record-crud`
+- If the task is about todo discovery, task context, approval actions, rollback or transfer, associated report review, or workflow log review, switch to `$qingflow-task-ops`
+- If the task is about creating new records or importing data, prefer `$qingflow-record-crud` under applicant-node schema semantics
+- If the task is about updating an existing record directly, require an explicit accessible `view_id` and then route to `$qingflow-record-crud`
+- If the task is about subtable writes, still route to `$qingflow-record-crud`, but shape the payload through the parent subtable field `rows/tableValues`; do not route users toward top-level leaf selectors
+- If the user sounds like an ordinary workflow assignee rather than a system operator, prefer `$qingflow-task-ops` over direct record mutation whenever both paths could fit
+- If the task is about grouped distributions, ratios, rankings, trends, insights, or any final statistical conclusion, switch to `$qingflow-record-analysis`
+- If the MCP is not connected, authenticated, or bound to the right workspace, switch to `$qingflow-mcp-setup`
+
+## Shared Preconditions
+
+- prefer canonical app ids, record ids, task ids, and workflow node ids over guessed names
+- if a field or target is still ambiguous after schema/task lookup, ask the user to confirm from a short candidate list instead of guessing
+- if the task can stay read-only, do not write or act
+- if the task involves a user-uploaded import file, do not modify the file unless the user explicitly authorizes repair or normalization
+- if the task involves record import, call `app_get` first and inspect `data.import_capability` before template download, file repair, or import start
+- if the current MCP capability is unsupported, the workflow is awkward, or the user's need still cannot be satisfied after reasonable use, summarize the gap, ask whether to submit feedback, and call `feedback_submit` only after explicit user confirmation
+
+## Shared Helper
+
+- `feedback_submit` is a cross-cutting helper for product feedback submission
+- It does not require Qingflow login or workspace selection
+- Use it only after the user explicitly confirms they want to submit feedback
 
 ## Resources
 
-- Environment switching: [references/environments.md](references/environments.md)
-- Record operation patterns: [references/record-patterns.md](references/record-patterns.md)
-- Workflow usage actions: [references/workflow-usage.md](references/workflow-usage.md)
-- Data gotchas: [references/data-gotchas.md](references/data-gotchas.md)
+- Record CRUD: [$qingflow-record-crud](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-crud/SKILL.md)
+- Dedicated analysis workflow: [$qingflow-record-analysis](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-analysis/SKILL.md)

package/skills/qingflow-app-user/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Qingflow App User"
-  short_description: "Use Qingflow apps for business data and task operations"
-  default_prompt: "Use $qingflow-app-user to query members or departments, inspect workload, and safely create, query, update, validate, approve, reject, or otherwise operate records in an existing Qingflow app, paying attention to request_route, verify_write, nodeId accuracy, and attachment upload flows when needed."
+  short_description: "Route Qingflow operational tasks to CRUD, task ops, or analysis"
+  default_prompt: "Use $qingflow-app-user as a router: switch to $qingflow-record-crud for record browse/read/write, switch to $qingflow-task-ops for task-center, comments, directory, and workflow usage actions, and switch to $qingflow-record-analysis for grouped analysis or final statistical conclusions."

package/skills/qingflow-app-user/references/data-gotchas.md

@@ -1,30 +1,31 @@
 # Data Gotchas
 
-## Counts
+For final statistics, grouped distributions, rankings, trends, or insight-style conclusions, use [$qingflow-record-analysis](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-analysis/SKILL.md) instead of keeping that reasoning inside `$qingflow-app-user`.
 
-- Prefer `effective_count`
-- For `record_query(summary)` and `record_aggregate`, inspect `completeness` before concluding
-- If the browser and MCP disagree, compare `request_route.base_url` and `request_route.qf_version` first
-
-## Record titles
+## Record Reads
 
-- Do not dump raw answer arrays to the user unless needed
-- Prefer concise business titles and counts
+- `record_list` is for browsing, export, and sample inspection only
+- `record_get` is for one exact record
+- Do not present paged browse output as if it were a grouped or full-population conclusion
+- If the browser and MCP disagree, compare `request_route.base_url` and `request_route.qf_version` first
 
-## Preflight
+## Write Preflight
 
-- `record_write_plan` is static preflight only; linked visibility and runtime required rules can still reject writes
-- `record_write_plan` now exposes `write_format.support_level`; check `full / restricted / unsupported` before attempting non-trivial writes
-- Use `record_field_resolve` when field titles are uncertain instead of guessing ids
-- Prefer `strict_full=true` for final statistics or business conclusions
-- `record_create` and `record_update` can do post-write verification with `verify_write=true`; use that for complex, subtable, or production writes
-- `apply_id` is normalized to an integer; pass it directly into later record tools
+- `record_write` always performs internal static preflight before any apply
+- If `record_write` returns `ok=false`, the write was blocked and not executed
+- Use `record_schema_get` when field titles are uncertain instead of guessing ids
+- Prefer `verify_write=true` for complex, relation-heavy, subtable, or production writes
+- Even when `record_write` returns `ok=true`, it may still surface verification failures; do not report success before checking them
 
-## Mock data
+## Write Semantics
 
-- Default to at least `5` rows per relevant entity unless the user asked for fewer
-- Avoid identical titles and identical statuses across all rows
-- Keep relation references valid
+- `insert` uses `values`
+- `update` uses `set`
+- `delete` uses `record_id` or `record_ids`
+- Do not send raw SQL strings
+- Do not fake formula or expression fields
+- Do not perform free-form bulk updates or deletes
+- Do not guess relation targets from display text; resolve the real `record_id` first
 
 ## Attachments
 
@@ -36,10 +37,10 @@
 
 - Subtable fields accept row objects keyed by subfield title, or native `tableValues`
 - Use the current form schema's subfield titles; do not guess nested ids
-- When updating existing subtable rows, preserve `rowId` if the source record returns it
+- When updating existing subtable rows, preserve row ids if the source record returns them
 - Nested subtable writes are still unsupported
 
-## Unsupported direct-write fields
+## Unsupported Direct-Write Fields
 
 - `14` time range
 - `34` image recognition

package/skills/qingflow-app-user/references/environments.md

@@ -50,7 +50,7 @@ Production behavior:
 Production guardrails:
 
 - never assume a record id, app id, or workspace id
-- treat `record_delete` as high risk
+- treat `record_write(operation="delete")` as high risk
 - if the task can be answered read-only, do not write
 
 ## Reporting Rule

package/skills/qingflow-app-user/references/record-patterns.md

@@ -1,54 +1,96 @@
 # Record Patterns
 
-## Query first
+If the task shifts into grouped analysis, ratio, ranking, trend, or any final statistical conclusion, switch to [$qingflow-record-analysis](/Users/yanqidong/Documents/qingflow-next/.codex/skills/qingflow-record-analysis/SKILL.md).
 
-Use `record_query` first when:
+## Browse Pattern
 
-- the user only gives a title or business key
-- the target record id is unknown
-- updates or deletes need confirmation
-- summary analysis or final counts are needed
+Use `record_schema_get -> record_list` when:
 
-Use `record_query_plan` first when:
+- the user wants to browse records
+- the target `record_id` is unknown
+- a delete or update target still needs confirmation
+- the user needs sample rows or a small export
 
-- field titles may be ambiguous
-- filters are still in natural-language shape
-- the result may be used as a final conclusion
-- scan scope or completeness is unclear
+Keep the browse DSL simple:
 
-## Create pattern
+- `columns`: field ids only
+- `where`: flat AND filters only
+- `order_by`: field sorting only
+- `limit` and `page`: browsing intent only
 
-1. Confirm target app
-2. Resolve fields with `record_field_resolve` if needed. Prefer exact schema titles first; only rely on platform-neutral aliases such as `创建时间`, `负责人`, or `部门` when they resolve cleanly, and do not assume business-domain shorthand like `销售` is portable across apps
-3. Run `record_write_plan` for non-trivial payloads or any `fields`-based write
-4. For relation fields, query the target app first and resolve the referenced record `apply_id`
-5. For attachments, call `file_upload_local` first and reuse the returned `attachment_value`
-6. For subtable fields, pass a list of row objects keyed by subfield title. When updating existing rows, include `rowId` / `row_id` / `__row_id__` only if the current record already exposes it
-7. Inspect `record_write_plan.data.support_matrix` or each field's `write_format.support_level` before submit:
-   - `full`: direct write is supported
-   - `restricted`: follow the documented presteps first
-   - `unsupported`: stop and explain the limitation
-8. For complex forms, production writes, attachments, relation-heavy payloads, or subtables, create with `verify_write=true`
-9. If verification fails, treat the write as not yet successful and inspect the missing or empty fields before reporting back
-10. Re-query or fetch the record when validation matters
+Do not use `record_list` for grouped conclusions, ratios, rankings, trends, or any final statistical claim.
 
-## Update pattern
+## Detail Pattern
 
-1. Query the target records
-2. Resolve exact `apply_id`
-3. Run `record_write_plan`
-4. Update only the intended fields
-5. Prefer `verify_write=true` for attachment, relation, subtable, or production updates
-6. Re-read the record if the change is important, attachment-related, subtable-related, or the form has linkage
+Use `record_schema_get -> record_get` when:
 
-## Delete pattern
+- the exact `record_id` is known
+- the user needs one record in detail
+- a write target needs verification before action
 
-1. Query or fetch the exact record first
-2. Confirm the target ids
-3. Delete
-4. Report affected ids and remaining count when relevant
+Prefer passing explicit `columns` when the user only needs a subset of fields.
 
-## Unsupported direct writes
+## Write Pattern
+
+Use `record_schema_get -> record_write`.
+
+1. Confirm the target app
+2. Resolve fields with `record_schema_get`
+3. Decide whether the task is `insert`, `update`, or `delete`
+4. Build SQL-like JSON clauses
+5. Run `record_write`
+6. If `ok=false`, explain `field_errors` first, then summarize blockers; stop because the write was not executed
+7. If `ok=true`, report the affected resource and any verification outcome
+8. For important writes, keep `verify_write=true`
+
+### Insert
+
+```json
+{
+  "operation": "insert",
+  "values": [
+    { "field_id": 12, "value": "测试客户" },
+    { "field_id": 18, "value": 1000 }
+  ],
+  "submit_type": "submit",
+  "verify_write": true
+}
+```
+
+### Update
+
+```json
+{
+  "operation": "update",
+  "record_id": 123,
+  "set": [
+    { "field_id": 18, "value": 2000 }
+  ],
+  "verify_write": true
+}
+```
+
+### Delete
+
+```json
+{
+  "operation": "delete",
+  "record_ids": [123, 124]
+}
+```
+
+## Write Anti-Patterns
+
+Do not do this:
+
+- do not send raw SQL text
+- do not build free-form `WHERE` updates or deletes
+- do not invent formulas or expressions
+- do not auto-fill missing required fields
+- do not guess relation targets without first resolving them
+- do not claim a blocked `record_write` was executed
+
+## Unsupported Direct Writes
 
 Do not attempt direct app-user writes for these field types:
 
@@ -57,13 +99,10 @@ Do not attempt direct app-user writes for these field types:
 - `35` image generation
 - `36` document parsing
 
-If the payload includes them, stop at `record_write_plan` and explain that the tool does not build a reliable native payload for those fields yet.
-
-## Relation fields
+If the payload includes them, stop after the blocked `record_write` response and explain that the tool does not support a reliable direct write for those fields yet.
 
-Relation fields are record-id based.
+## Relation, Attachment, and Subtable Rules
 
-- Query the referenced app first
-- Resolve the target record `apply_id`
-- Write the relation field with that id
-- Do not write relation fields with display titles, business keys, or guessed identifiers unless they have already been resolved to the real record id
+- Relation fields are record-id based. Resolve the referenced target first, then write the relation field with the real `record_id`.
+- Attachment fields are two-step: upload first with `file_upload_local`, then reuse the returned attachment payload in `record_write`.
+- Subtable writes require the current schema shape; when updating existing subtable rows, preserve row ids if the current record exposes them.

package/skills/qingflow-app-user/references/workflow-usage.md

@@ -7,18 +7,20 @@ Examples:
 - add a comment to a record
 - approve or reject a workflow task
 - transfer a task
-- roll back a record
-- list pending, processed, or cc tasks
+- roll back a task
+- list todo, initiated, done, or cc tasks
+- inspect workload by worksheet or workflow node
 - urge a pending task
 
 Rules:
 
 - if the user starts from inbox, todo, workload, cc, or bottleneck language, use `task_*` first
-- use `task_statistics` for counts and `task_list` or `task_list_grouped` for browsing
-- use `task_list_grouped` when grouped workload browsing matters
+- use `task_summary` for headline counts
+- use `task_list` for flat browsing
+- use `task_facets` when worksheet or workflow-node buckets matter
 - treat task counts as task-center counts, not record counts
-- switch to `record_*` after locating the exact business record behind a task
-- identify the exact record first
-- for approve or reject, identify the exact `nodeId` first; prefer task-center results or audit info, then use `task_approve` or `task_reject`
-- avoid usage-side flow actions on ambiguous records
+- switch to `record_*` only after locating the exact business record behind a task
+- identify the exact target first
+- for approve or reject, identify the exact `workflow_node_id` first; prefer task-center results or current audit info, then use `task_approve` or `task_reject`
+- avoid usage-side workflow actions on ambiguous records
 - summarize the final action and target task ids or record ids