@josephyan/qingflow-app-builder-mcp 0.2.0-beta.5 → 0.2.0-beta.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
- package/pyproject.toml +1 -1
- package/skills/qingflow-app-builder/SKILL.md +4 -1
- package/src/qingflow_mcp/__init__.py +1 -1
- package/src/qingflow_mcp/builder_facade/service.py +657 -74
- package/src/qingflow_mcp/server_app_builder.py +15 -0
- package/src/qingflow_mcp/tools/ai_builder_tools.py +289 -33
- package/src/qingflow_mcp/tools/workflow_tools.py +78 -4
package/README.md
CHANGED
|
@@ -3,13 +3,13 @@
|
|
|
3
3
|
Install:
|
|
4
4
|
|
|
5
5
|
```bash
|
|
6
|
-
npm install @josephyan/qingflow-app-builder-mcp@0.2.0-beta.
|
|
6
|
+
npm install @josephyan/qingflow-app-builder-mcp@0.2.0-beta.7
|
|
7
7
|
```
|
|
8
8
|
|
|
9
9
|
Run:
|
|
10
10
|
|
|
11
11
|
```bash
|
|
12
|
-
npx -y -p @josephyan/qingflow-app-builder-mcp@0.2.0-beta.
|
|
12
|
+
npx -y -p @josephyan/qingflow-app-builder-mcp@0.2.0-beta.7 qingflow-app-builder-mcp
|
|
13
13
|
```
|
|
14
14
|
|
|
15
15
|
Environment:
|
package/package.json
CHANGED
package/pyproject.toml
CHANGED
|
@@ -21,7 +21,7 @@ Pick the smallest tool layer that can finish the task.
|
|
|
21
21
|
- File upload: `file_upload_local`
|
|
22
22
|
- Resource resolve/read: `package_list`, `package_resolve`, `app_resolve`, `app_read_summary`, `app_read_fields`, `app_read_layout_summary`, `app_read_views_summary`, `app_read_flow_summary`
|
|
23
23
|
- Resource plan: `app_schema_plan`, `app_layout_plan`, `app_flow_plan`, `app_views_plan`
|
|
24
|
-
- Resource patch: `app_schema_apply`, `app_layout_apply`, `app_flow_apply`, `app_views_apply`, `package_attach_app`
|
|
24
|
+
- Resource patch: `app_schema_apply`, `app_layout_apply`, `app_flow_apply`, `app_views_apply`, `package_attach_app`, `app_release_edit_lock_if_mine`
|
|
25
25
|
- Publish and verify: `app_publish_verify`
|
|
26
26
|
|
|
27
27
|
Note:
|
|
@@ -55,6 +55,7 @@ For builder work:
|
|
|
55
55
|
8. Use `app_flow_apply` after schema exists. It publishes by default.
|
|
56
56
|
9. Use `app_views_apply` when the user wants explicit list/card/board views. It publishes by default.
|
|
57
57
|
10. Use `app_publish_verify` only when the user explicitly wants final publish/live verification or you need an explicit verification pass.
|
|
58
|
+
11. If a write fails with `APP_EDIT_LOCKED`, stop normal writes. Only use `app_release_edit_lock_if_mine` when the failed result shows the lock owner is the current logged-in user.
|
|
58
59
|
|
|
59
60
|
In `prod`, keep `plan` and `apply` as separate phases unless the user explicitly asks for a direct live execution.
|
|
60
61
|
|
|
@@ -74,6 +75,7 @@ For additive work on existing systems:
|
|
|
74
75
|
- `package_attach_app` is the source of truth for package ownership; do not assume app creation or publish implicitly attaches the app.
|
|
75
76
|
- `relation` and `subtable` must be explicit; do not infer them from vague natural language.
|
|
76
77
|
- In `prod`, prefer explicit patch tools and avoid any speculative create flow.
|
|
78
|
+
- Never try to bypass collaborative edit locks. `app_release_edit_lock_if_mine` is only for the case where the lock owner is the current authenticated user.
|
|
77
79
|
|
|
78
80
|
## Response Interpretation
|
|
79
81
|
|
|
@@ -101,6 +103,7 @@ For additive work on existing systems:
|
|
|
101
103
|
- Replace workflow: `app_flow_apply`
|
|
102
104
|
- Upsert/remove views: `app_views_apply`
|
|
103
105
|
- Attach one app to a package: `package_attach_app`
|
|
106
|
+
- Release your own stale edit lock: `app_release_edit_lock_if_mine`
|
|
104
107
|
- Publish and verify: `app_publish_verify` when you need a separate verification pass beyond the default auto-publish behavior in apply tools
|
|
105
108
|
|
|
106
109
|
Detailed playbooks:
|