@qingflow-tech/qingflow-app-builder-mcp 1.0.1 → 1.0.3

package/skills/qingflow-app-builder/references/tool-selection.md

@@ -4,7 +4,7 @@ Use the smallest v2 builder tool chain that can finish the task.
 
 ## Default path
 
-`resolve -> summary read -> apply -> attach -> publish_verify`
+`summary read -> apply -> publish_verify`
 
 Public builder `apply` tools already perform server-side planning, normalization, and dependency checks internally. Do not route normal public builder work through explicit `*_plan` tools.
 
@@ -21,13 +21,12 @@ If the user asks for multiple forms/modules that relate to each other, this is a
 
 ## Resolve
 
-- `package_create`: create a new package only after the user confirms package creation; exact-name duplicates return `noop=true`
-- `package_resolve`: exact package lookup by name
-- `package_list`: read-only fallback when package resolution is ambiguous
+- `package_get`: read one known package by `package_id`
+- `package_apply`: create or update one package; use `create_if_missing=true` only after explicit user intent
 - `member_search`: resolve named people from the directory
 - `role_search`: resolve reusable roles from the directory
 - `role_create`: create a reusable role when the business owner wants role-based routing
-- `app_resolve`: locate an existing app by exactly one selector mode: `app_key`, or `app_name + package_tag_id`
+- `app_resolve`: locate an existing app by exactly one selector mode: `app_key`, or `app_name + package_id`
 
 ## Summary reads
 
@@ -48,21 +47,20 @@ These execute normalized patches and publish by default unless `publish=false`.
 - `app_flow_apply`: replace workflow
 - `app_views_apply`: upsert or remove views
 - `app_charts_apply`: upsert/remove/reorder QingBI charts; charts are immediate-live and do not publish; use `chart_id` when names are not unique
-- `portal_apply`: create or replace-update portal pages; use `dash_key` for update mode or `package_tag_id + dash_name` for create mode; sections are replace-only and omission deletes old sections; `publish=false` only guarantees draft/base-info updates
+- `portal_apply`: create or replace-update portal pages; use `dash_key` for update mode or `package_id + dash_name` for create mode; edit mode may omit `sections` for base-info-only updates; when sections are supplied they still use replace semantics
 
 ## Explicit post-apply tools
 
-- `package_attach_app`: attach an app to a package with `tag_id + app_key`; do not assume create or publish attaches it
 - `app_publish_verify`: explicit final publish verification when the user asks for live confirmation
 
 ## Decision shortcuts
 
 - Create one app inside an existing package:
-  `package_resolve -> app_resolve -> app_schema_apply -> package_attach_app`
+  `package_get -> app_resolve -> app_schema_apply`
 - Create a brand new package, then create one app in it:
-  `package_create -> package_resolve -> app_schema_apply -> package_attach_app`
+  `package_apply(create_if_missing=true) -> app_schema_apply`
 - Create a brand new multi-app system/package:
-  `package_create/resolve -> per-app app_schema_apply -> package_attach_app per app -> relation field patches`
+  `package_apply(create_if_missing=true) -> per-app app_schema_apply -> relation field patches`
 - Update fields on an existing app:
   `app_resolve -> app_get_fields -> app_schema_apply`
 - Tidy layout:
@@ -81,6 +79,7 @@ These execute normalized patches and publish by default unless `publish=false`.
 - Do not handcraft raw Qingflow schema payloads
 - Do not rely on internal `solution_*` tools in public builder flows
 - Do not create a new package without first asking the user to confirm package creation
+- Do not regress to `package_create` or `package_attach_app` as the public default story
 - Do not treat a package/system name as `app_name` when the user clearly wants multiple apps inside it
 - Do not compress multiple business objects into one app with several text fields
 - Do not skip summary reads before flow or view work

package/src/qingflow_mcp/__init__.py

@@ -1,5 +1,37 @@
 from __future__ import annotations
 
+from importlib.metadata import PackageNotFoundError, packages_distributions, version as _dist_version
+from pathlib import Path
+
 __all__ = ["__version__"]
 
-__version__ = "0.2.0b87"
+_FALLBACK_VERSION = "0.2.0b998"
+
+
+def _resolve_local_pyproject_version() -> str | None:
+    module_path = Path(__file__).resolve()
+    for parent in module_path.parents:
+        candidate = parent / "pyproject.toml"
+        if not candidate.is_file():
+            continue
+        for line in candidate.read_text(encoding="utf-8").splitlines():
+            stripped = line.strip()
+            if stripped.startswith("version = "):
+                return stripped.split("=", 1)[1].strip().strip('"')
+        break
+    return None
+
+
+def _resolve_runtime_version() -> str:
+    local_version = _resolve_local_pyproject_version()
+    if local_version:
+        return local_version
+    for dist_name in packages_distributions().get("qingflow_mcp", []):
+        try:
+            return _dist_version(dist_name)
+        except PackageNotFoundError:
+            continue
+    return _FALLBACK_VERSION
+
+
+__version__ = _resolve_runtime_version()

package/src/qingflow_mcp/builder_facade/models.py

@@ -819,6 +819,10 @@ class FieldMutation(StrictModel):
         validation_alias=AliasChoices("custom_button_text", "customButtonText", "custom_btn_text", "customBtnText"),
     )
     subfields: list[FieldPatch] | None = None
+    subfield_updates: list["FieldUpdatePatch"] | None = Field(
+        default=None,
+        validation_alias=AliasChoices("subfield_updates", "subfieldUpdates"),
+    )
 
     @model_validator(mode="after")
     def validate_shape(self) -> "FieldMutation":
@@ -848,8 +852,12 @@ class FieldMutation(StrictModel):
             or self.custom_button_text is not None
         ):
             raise ValueError("code_block_config, code_block_binding, auto_trigger, custom_button_text_enabled, and custom_button_text are only allowed for code_block fields")
-        if self.type == PublicFieldType.subtable and not self.subfields:
-            raise ValueError("subtable field requires subfields")
+        if self.type == PublicFieldType.subtable and not self.subfields and not self.subfield_updates:
+            raise ValueError("subtable field requires subfields or subfield_updates")
+        if self.type is not None and self.type != PublicFieldType.subtable and self.subfield_updates:
+            raise ValueError("subfield_updates are only allowed for subtable fields")
+        if self.subfields and self.subfield_updates:
+            raise ValueError("subfields and subfield_updates cannot be used together")
         return self
 
     @model_validator(mode="before")
@@ -1528,14 +1536,16 @@ class PortalApplyRequest(StrictModel):
             raise ValueError("package_tag_id is required when dash_key is empty")
         if not self.dash_key and not self.dash_name:
             raise ValueError("dash_name is required when creating a portal")
-        if not self.sections:
-            raise ValueError("portal apply requires a non-empty sections list")
+        if not self.dash_key and not self.sections:
+            raise ValueError("portal apply requires a non-empty sections list when creating a portal")
         if self.visibility is not None and self.auth is not None:
             raise ValueError("visibility and auth cannot be provided together")
         return self
 
 
 FieldPatch.model_rebuild()
+FieldMutation.model_rebuild()
+FieldUpdatePatch.model_rebuild()
 
 
 class AppGetResponse(StrictModel):