@qingflow-tech/qingflow-app-user-mcp 1.0.9 → 1.0.10

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 (12) hide show
  1. package/README.md +2 -2
  2. package/package.json +1 -1
  3. package/pyproject.toml +1 -1
  4. package/skills/qingflow-record-update/SKILL.md +2 -0
  5. package/src/qingflow_mcp/builder_facade/models.py +2 -0
  6. package/src/qingflow_mcp/builder_facade/service.py +223 -39
  7. package/src/qingflow_mcp/cli/commands/builder.py +40 -11
  8. package/src/qingflow_mcp/cli/main.py +204 -3
  9. package/src/qingflow_mcp/response_trim.py +15 -10
  10. package/src/qingflow_mcp/server_app_builder.py +27 -2
  11. package/src/qingflow_mcp/tools/ai_builder_tools.py +1189 -29
  12. package/src/qingflow_mcp/tools/record_tools.py +200 -6
package/README.md CHANGED
@@ -3,13 +3,13 @@
3
3
  Install:
4
4
 
5
5
  ```bash
6
- npm install @qingflow-tech/qingflow-app-user-mcp@1.0.9
6
+ npm install @qingflow-tech/qingflow-app-user-mcp@1.0.10
7
7
  ```
8
8
 
9
9
  Run:
10
10
 
11
11
  ```bash
12
- npx -y -p @qingflow-tech/qingflow-app-user-mcp@1.0.9 qingflow-app-user-mcp
12
+ npx -y -p @qingflow-tech/qingflow-app-user-mcp@1.0.10 qingflow-app-user-mcp
13
13
  ```
14
14
 
15
15
  Environment:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@qingflow-tech/qingflow-app-user-mcp",
3
- "version": "1.0.9",
3
+ "version": "1.0.10",
4
4
  "description": "Operational end-user MCP for Qingflow records, tasks, comments, and directory workflows.",
5
5
  "license": "MIT",
6
6
  "type": "module",
package/pyproject.toml CHANGED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "qingflow-mcp"
7
- version = "1.0.9"
7
+ version = "1.0.10"
8
8
  description = "User-authenticated MCP server for Qingflow"
9
9
  readme = "README.md"
10
10
  license = "MIT"
package/skills/qingflow-record-update/SKILL.md CHANGED
@@ -35,6 +35,8 @@ metadata:
35
35
  13. Do not look for any extra context bucket in update schema; lookup behavior stays inline on the field definitions themselves
36
36
  14. When update context feels unstable, trust `record_update_schema_get`'s route-aware matched-view result over guessed `view_id` or remembered UI scope
37
37
  15. If single-record detail/readback matters, prefer `record_get` after the write and read top-level `fields[]`, `media_assets.items[].local_path`, `file_assets.items[].local_path`, `file_assets.items[].extraction.text_path`, and `semantic_context`; `record_get` follows the frontend storage cookie redirect path for Qingflow attachments, so prefer local paths over remote URLs; use `record_list(..., output_profile="normalized")` only for batch row-shaped normalized readback
38
+ 16. For batch updates, read top-level `mode`, `dry_run`, `total`, `succeeded`, `failed`, `needs_confirmation`, `updated_record_ids`, `write_executed`, `safe_to_retry`, `verification_status`, and `items[].row_number/status/record_id`
39
+ 17. If `write_executed=true`, do not blindly retry the whole batch; use `items[]` and `updated_record_ids` to decide whether only failed rows need repair
38
40
 
39
41
  ## Do Not
40
42
 
package/src/qingflow_mcp/builder_facade/models.py CHANGED
@@ -2034,6 +2034,8 @@ FieldUpdatePatch.model_rebuild()
2034
2034
 
2035
2035
  class AppGetResponse(StrictModel):
2036
2036
  app_key: str
2037
+ app_name: str | None = None
2038
+ name: str | None = None
2037
2039
  title: str | None = None
2038
2040
  app_icon: str | None = None
2039
2041
  visibility: dict[str, Any] = Field(default_factory=dict)