makedsl usage

Use this skill when you need to design or generate dsl for make platform or make 开发平台. make platform 从 kubernetes 和 ansible 中借鉴了设计思路, 业务的模型通过 DSL 建模定义, 然后通过 DataAPI 来对数据进行 CRUD-LS. 生成的 DSL(yaml) 文件应该通过 makecli 提交到 make platform (make 开发者平台)

Use canvas-table-integration for CanvasTable display, columns, renderers, or cell editing. makedsl only owns schema modeling semantics.

Runtime Boundary

确认方案后生成应用的审批入口、审批新建字段与状态展示，使用 make-app-approval。bpmDefinitionKey 由运行时 Meta 返回；qfei_process_instance_status 和 qfei_is_locked 为平台系统字段，不在 DSL 新建同名业务字段，不为“已保存”新增审批状态。业务已有生命周期字段继续保留。

• DSL YAML is a design and deployment input, not a required runtime file for a published App Service.
• Do not generate Service startup logic that hard-codes container paths such as /dsl/00-app.yaml.
• Published Service should load schema from Make remote schema APIs or environment-provided config. Local DSL files are acceptable for development, fixtures, tests, and makecli apply, but must not be the only source required for k8s startup.
• If a Service needs a fallback local schema for offline development, make it explicit and test both the remote-schema path and the fallback path.
• When frontend build or published App runtime needs remote schema, use Meta Service APIs from @references/MetaAPIDesign.md instead of reading local DSL files.

Reference map