@agentlang/agentmanager 0.0.3 → 0.0.4

package/dist/apps/monolith/libs/agentcraft/src/index.js

@@ -0,0 +1,91 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.InvalidSessionStateError = exports.SessionNotFoundError = exports.DomainError = exports.SubmitResolverActionDto = exports.SubmitActionDto = exports.SubmitActionSchema = exports.SubmitActionBaseSchema = exports.stripModuleLine = exports.extractEntityNames = exports.extractModuleName = exports.pascalToKebabCase = exports.kebabToPascalCase = exports.trimSpec = exports.fetchSpec = exports.writeAppFiles = exports.parseAssemblyOutput = exports.basicValidation = exports.validateCode = exports.checkCommonErrors = exports.normalizeGeneratedCode = exports.loadAllKBDocuments = exports.RegistryClientService = exports.SpecFetcherService = exports.ApiAdapterFactory = exports.ApiAdapterService = exports.CraftConfigService = exports.OutputParserService = exports.PipelineStateService = exports.STEP_DEFINITIONS = exports.PipelineStepsService = exports.AutonomousRunnerService = exports.ExecutorService = exports.PlannerService = exports.KbWatcherService = exports.ReadmeGeneratorService = exports.UIBlueprintGeneratorService = exports.DesignGeneratorService = exports.RequirementsGeneratorService = exports.DecomposerService = exports.ArchitectLoopFactory = exports.AnthropicCraftLlmService = exports.CraftLlmAdapterService = exports.OpenaiLlmService = exports.AnthropicLlmService = exports.TestFailureAction = exports.ReviewAction = exports.PipelineStep = exports.CRAFT_LLM_PROVIDER = exports.LLM_PROVIDER = exports.AgentcraftModule = void 0;
+exports.LlmRequestFailedError = exports.LlmNotConfiguredError = exports.LlmError = void 0;
+var agentcraft_module_1 = require("./agentcraft.module");
+Object.defineProperty(exports, "AgentcraftModule", { enumerable: true, get: function () { return agentcraft_module_1.AgentcraftModule; } });
+var constants_1 = require("./constants");
+Object.defineProperty(exports, "LLM_PROVIDER", { enumerable: true, get: function () { return constants_1.LLM_PROVIDER; } });
+Object.defineProperty(exports, "CRAFT_LLM_PROVIDER", { enumerable: true, get: function () { return constants_1.CRAFT_LLM_PROVIDER; } });
+var pipeline_types_1 = require("./types/pipeline.types");
+Object.defineProperty(exports, "PipelineStep", { enumerable: true, get: function () { return pipeline_types_1.PipelineStep; } });
+Object.defineProperty(exports, "ReviewAction", { enumerable: true, get: function () { return pipeline_types_1.ReviewAction; } });
+Object.defineProperty(exports, "TestFailureAction", { enumerable: true, get: function () { return pipeline_types_1.TestFailureAction; } });
+var anthropic_llm_service_1 = require("./services/anthropic-llm.service");
+Object.defineProperty(exports, "AnthropicLlmService", { enumerable: true, get: function () { return anthropic_llm_service_1.AnthropicLlmService; } });
+var openai_llm_service_1 = require("./services/openai-llm.service");
+Object.defineProperty(exports, "OpenaiLlmService", { enumerable: true, get: function () { return openai_llm_service_1.OpenaiLlmService; } });
+var craft_llm_adapter_service_1 = require("./services/craft-llm-adapter.service");
+Object.defineProperty(exports, "CraftLlmAdapterService", { enumerable: true, get: function () { return craft_llm_adapter_service_1.CraftLlmAdapterService; } });
+var anthropic_craft_llm_service_1 = require("./services/anthropic-craft-llm.service");
+Object.defineProperty(exports, "AnthropicCraftLlmService", { enumerable: true, get: function () { return anthropic_craft_llm_service_1.AnthropicCraftLlmService; } });
+var architect_loop_service_1 = require("./services/architect-loop.service");
+Object.defineProperty(exports, "ArchitectLoopFactory", { enumerable: true, get: function () { return architect_loop_service_1.ArchitectLoopFactory; } });
+var decomposer_service_1 = require("./services/decomposer.service");
+Object.defineProperty(exports, "DecomposerService", { enumerable: true, get: function () { return decomposer_service_1.DecomposerService; } });
+var requirements_generator_service_1 = require("./services/requirements-generator.service");
+Object.defineProperty(exports, "RequirementsGeneratorService", { enumerable: true, get: function () { return requirements_generator_service_1.RequirementsGeneratorService; } });
+var design_generator_service_1 = require("./services/design-generator.service");
+Object.defineProperty(exports, "DesignGeneratorService", { enumerable: true, get: function () { return design_generator_service_1.DesignGeneratorService; } });
+var ui_blueprint_generator_service_1 = require("./services/ui-blueprint-generator.service");
+Object.defineProperty(exports, "UIBlueprintGeneratorService", { enumerable: true, get: function () { return ui_blueprint_generator_service_1.UIBlueprintGeneratorService; } });
+var readme_generator_service_1 = require("./services/readme-generator.service");
+Object.defineProperty(exports, "ReadmeGeneratorService", { enumerable: true, get: function () { return readme_generator_service_1.ReadmeGeneratorService; } });
+var kb_watcher_service_1 = require("./services/kb-watcher.service");
+Object.defineProperty(exports, "KbWatcherService", { enumerable: true, get: function () { return kb_watcher_service_1.KbWatcherService; } });
+var planner_service_1 = require("./services/planner.service");
+Object.defineProperty(exports, "PlannerService", { enumerable: true, get: function () { return planner_service_1.PlannerService; } });
+var executor_service_1 = require("./services/executor.service");
+Object.defineProperty(exports, "ExecutorService", { enumerable: true, get: function () { return executor_service_1.ExecutorService; } });
+var autonomous_runner_service_1 = require("./services/autonomous-runner.service");
+Object.defineProperty(exports, "AutonomousRunnerService", { enumerable: true, get: function () { return autonomous_runner_service_1.AutonomousRunnerService; } });
+var pipeline_steps_service_1 = require("./services/pipeline-steps.service");
+Object.defineProperty(exports, "PipelineStepsService", { enumerable: true, get: function () { return pipeline_steps_service_1.PipelineStepsService; } });
+Object.defineProperty(exports, "STEP_DEFINITIONS", { enumerable: true, get: function () { return pipeline_steps_service_1.STEP_DEFINITIONS; } });
+var pipeline_state_service_1 = require("./services/pipeline-state.service");
+Object.defineProperty(exports, "PipelineStateService", { enumerable: true, get: function () { return pipeline_state_service_1.PipelineStateService; } });
+var output_parser_service_1 = require("./services/output-parser.service");
+Object.defineProperty(exports, "OutputParserService", { enumerable: true, get: function () { return output_parser_service_1.OutputParserService; } });
+var craft_config_service_1 = require("./services/craft-config.service");
+Object.defineProperty(exports, "CraftConfigService", { enumerable: true, get: function () { return craft_config_service_1.CraftConfigService; } });
+var api_adapter_service_1 = require("./services/api-adapter.service");
+Object.defineProperty(exports, "ApiAdapterService", { enumerable: true, get: function () { return api_adapter_service_1.ApiAdapterService; } });
+Object.defineProperty(exports, "ApiAdapterFactory", { enumerable: true, get: function () { return api_adapter_service_1.ApiAdapterFactory; } });
+var spec_fetcher_service_1 = require("./services/spec-fetcher.service");
+Object.defineProperty(exports, "SpecFetcherService", { enumerable: true, get: function () { return spec_fetcher_service_1.SpecFetcherService; } });
+var registry_client_service_1 = require("./services/registry-client.service");
+Object.defineProperty(exports, "RegistryClientService", { enumerable: true, get: function () { return registry_client_service_1.RegistryClientService; } });
+var kb_loader_1 = require("./utils/kb-loader");
+Object.defineProperty(exports, "loadAllKBDocuments", { enumerable: true, get: function () { return kb_loader_1.loadAllKBDocuments; } });
+var validator_1 = require("./utils/validator");
+Object.defineProperty(exports, "normalizeGeneratedCode", { enumerable: true, get: function () { return validator_1.normalizeGeneratedCode; } });
+Object.defineProperty(exports, "checkCommonErrors", { enumerable: true, get: function () { return validator_1.checkCommonErrors; } });
+Object.defineProperty(exports, "validateCode", { enumerable: true, get: function () { return validator_1.validateCode; } });
+Object.defineProperty(exports, "basicValidation", { enumerable: true, get: function () { return validator_1.basicValidation; } });
+var output_writer_1 = require("./utils/output-writer");
+Object.defineProperty(exports, "parseAssemblyOutput", { enumerable: true, get: function () { return output_writer_1.parseAssemblyOutput; } });
+Object.defineProperty(exports, "writeAppFiles", { enumerable: true, get: function () { return output_writer_1.writeAppFiles; } });
+var spec_fetcher_1 = require("./utils/spec-fetcher");
+Object.defineProperty(exports, "fetchSpec", { enumerable: true, get: function () { return spec_fetcher_1.fetchSpec; } });
+var spec_trimmer_1 = require("./utils/spec-trimmer");
+Object.defineProperty(exports, "trimSpec", { enumerable: true, get: function () { return spec_trimmer_1.trimSpec; } });
+var text_utils_1 = require("./utils/text-utils");
+Object.defineProperty(exports, "kebabToPascalCase", { enumerable: true, get: function () { return text_utils_1.kebabToPascalCase; } });
+Object.defineProperty(exports, "pascalToKebabCase", { enumerable: true, get: function () { return text_utils_1.pascalToKebabCase; } });
+Object.defineProperty(exports, "extractModuleName", { enumerable: true, get: function () { return text_utils_1.extractModuleName; } });
+Object.defineProperty(exports, "extractEntityNames", { enumerable: true, get: function () { return text_utils_1.extractEntityNames; } });
+Object.defineProperty(exports, "stripModuleLine", { enumerable: true, get: function () { return text_utils_1.stripModuleLine; } });
+var submit_action_dto_1 = require("./dto/submit-action.dto");
+Object.defineProperty(exports, "SubmitActionBaseSchema", { enumerable: true, get: function () { return submit_action_dto_1.SubmitActionBaseSchema; } });
+Object.defineProperty(exports, "SubmitActionSchema", { enumerable: true, get: function () { return submit_action_dto_1.SubmitActionSchema; } });
+Object.defineProperty(exports, "SubmitActionDto", { enumerable: true, get: function () { return submit_action_dto_1.SubmitActionDto; } });
+Object.defineProperty(exports, "SubmitResolverActionDto", { enumerable: true, get: function () { return submit_action_dto_1.SubmitResolverActionDto; } });
+var domain_error_1 = require("./errors/domain.error");
+Object.defineProperty(exports, "DomainError", { enumerable: true, get: function () { return domain_error_1.DomainError; } });
+Object.defineProperty(exports, "SessionNotFoundError", { enumerable: true, get: function () { return domain_error_1.SessionNotFoundError; } });
+Object.defineProperty(exports, "InvalidSessionStateError", { enumerable: true, get: function () { return domain_error_1.InvalidSessionStateError; } });
+var llm_errors_1 = require("./errors/llm.errors");
+Object.defineProperty(exports, "LlmError", { enumerable: true, get: function () { return llm_errors_1.LlmError; } });
+Object.defineProperty(exports, "LlmNotConfiguredError", { enumerable: true, get: function () { return llm_errors_1.LlmNotConfiguredError; } });
+Object.defineProperty(exports, "LlmRequestFailedError", { enumerable: true, get: function () { return llm_errors_1.LlmRequestFailedError; } });
+//# sourceMappingURL=index.js.map

package/dist/apps/monolith/libs/agentcraft/src/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../../libs/agentcraft/src/index.ts"],"names":[],"mappings":";;;;AACA,yDAAuD;AAA9C,qHAAA,gBAAgB,OAAA;AAIzB,yCAA+D;AAAtD,yGAAA,YAAY,OAAA;AAAE,+GAAA,kBAAkB,OAAA;AAkBzC,yDAIgC;AAH9B,8GAAA,YAAY,OAAA;AACZ,8GAAA,YAAY,OAAA;AACZ,mHAAA,iBAAiB,OAAA;AA2DnB,0EAAuE;AAA9D,4HAAA,mBAAmB,OAAA;AAC5B,oEAAiE;AAAxD,sHAAA,gBAAgB,OAAA;AACzB,kFAA8E;AAArE,mIAAA,sBAAsB,OAAA;AAC/B,sFAAkF;AAAzE,uIAAA,wBAAwB,OAAA;AAGjC,4EAAyE;AAAhE,8HAAA,oBAAoB,OAAA;AAO7B,oEAAkE;AAAzD,uHAAA,iBAAiB,OAAA;AAC1B,4FAAyF;AAAhF,8IAAA,4BAA4B,OAAA;AACrC,gFAA6E;AAApE,kIAAA,sBAAsB,OAAA;AAC/B,4FAAwF;AAA/E,6IAAA,2BAA2B,OAAA;AACpC,gFAA6E;AAApE,kIAAA,sBAAsB,OAAA;AAC/B,oEAAiE;AAAxD,sHAAA,gBAAgB,OAAA;AAGzB,8DAA4D;AAAnD,iHAAA,cAAc,OAAA;AACvB,gEAA8D;AAArD,mHAAA,eAAe,OAAA;AACxB,kFAA+E;AAAtE,oIAAA,uBAAuB,OAAA;AAGhC,4EAG2C;AAFzC,8HAAA,oBAAoB,OAAA;AACpB,0HAAA,gBAAgB,OAAA;AAElB,4EAAyE;AAAhE,8HAAA,oBAAoB,OAAA;AAC7B,0EAAuE;AAA9D,4HAAA,mBAAmB,OAAA;AAI5B,wEAAqE;AAA5D,0HAAA,kBAAkB,OAAA;AAG3B,sEAGwC;AAFtC,wHAAA,iBAAiB,OAAA;AACjB,wHAAA,iBAAiB,OAAA;AAKnB,wEAAqE;AAA5D,0HAAA,kBAAkB,OAAA;AAC3B,8EAA2E;AAAlE,gIAAA,qBAAqB,OAAA;AAG9B,+CAAuD;AAA9C,+GAAA,kBAAkB,OAAA;AAC3B,+CAK2B;AAJzB,mHAAA,sBAAsB,OAAA;AACtB,8GAAA,iBAAiB,OAAA;AACjB,yGAAA,YAAY,OAAA;AACZ,4GAAA,eAAe,OAAA;AAEjB,uDAA2E;AAAlE,oHAAA,mBAAmB,OAAA;AAAE,8GAAA,aAAa,OAAA;AAC3C,qDAAiD;AAAxC,yGAAA,SAAS,OAAA;AAClB,qDAAgD;AAAvC,wGAAA,QAAQ,OAAA;AACjB,iDAM4B;AAL1B,+GAAA,iBAAiB,OAAA;AACjB,+GAAA,iBAAiB,OAAA;AACjB,+GAAA,iBAAiB,OAAA;AACjB,gHAAA,kBAAkB,OAAA;AAClB,6GAAA,eAAe,OAAA;AAIjB,6DAKiC;AAJ/B,2HAAA,sBAAsB,OAAA;AACtB,uHAAA,kBAAkB,OAAA;AAClB,oHAAA,eAAe,OAAA;AACf,4HAAA,uBAAuB,OAAA;AAIzB,sDAI+B;AAH7B,2GAAA,WAAW,OAAA;AACX,oHAAA,oBAAoB,OAAA;AACpB,wHAAA,wBAAwB,OAAA;AAE1B,kDAI6B;AAH3B,sGAAA,QAAQ,OAAA;AACR,mHAAA,qBAAqB,OAAA;AACrB,mHAAA,qBAAqB,OAAA"}

package/dist/apps/monolith/libs/agentcraft/src/instructions/step6-data-model.d.ts

@@ -0,0 +1 @@
+export declare const step6DataModelInstructions = "You are the sixth agent in a pipeline that generates agentlang applications. Your job is to generate a valid, parseable agentlang data model definition from the requirements, domain objects, and API specification produced by the previous agents.\n\n## Input Context\n\nThe requirements analysis:\n\n<file>requirementsAnalysis.md</file>\n\nThe core domain objects:\n\n<file>coreObjects.md</file>\n\nThe API specification:\n\n<file>apiSpec.md</file>\n\n## Resolver Context (if applicable)\n\n<file>?resolverMeta.md</file>\n\nIf resolver metadata is shown above, a resolver module already handles these entities and their CRUD bindings. In the core module:\n- Do NOT redefine resolver entities (they already exist in the resolver module)\n- Do NOT write `resolver` blocks \u2014 the resolver module already defines all resolver bindings with the correct import aliases\n- You MAY reference resolver entities in relationships and workflows using fully-qualified names (e.g. `Resolvers.Petstore/Pet`)\n\n## Your Role\n\nYou translate the identified domain objects and their relationships into a syntactically valid agentlang module definition. Your output will be **automatically validated by the agentlang parser**. If your output contains syntax errors, you will receive the error details and must fix them.\n\n## CRITICAL: Output Requirements\n\nYour response must contain ONLY a valid agentlang module definition. Do not include any explanatory text, markdown formatting, or code fences. The entire response must be parseable agentlang code starting with `module`.\n\n**IMPORTANT**: Your output is validated by the agentlang parser. If validation fails, you will receive the parse errors and must correct the code. Pay careful attention to syntax.\n\n## How to Respond\n\n### On the FIRST message:\n\nGenerate the complete agentlang data model as a module definition. Use the domain objects, their attributes, and relationships from the input context.\n\n### On FOLLOW-UP messages:\n\nThe user may request changes (add entities, modify attributes, change relationships). Regenerate the complete module with the requested changes. Always output the full module, not just the changed parts.\n\n### On VALIDATION FAILURE:\n\nIf your output fails parsing, you will receive an error like:\n`Validation for your last response failed with this result: {\"status\":\"error\",\"reason\":\"...\"}`\n\nRead the error carefully, identify the syntax issue, and output the corrected full module definition.\n\n## Agentlang Data Model Syntax\n\n### Module Declaration\n\nEvery module starts with:\n```\nmodule <AppName>.core\n```\n\n### Entity Definition\n\n```\nentity <EntityName> {\n    <attrName> <Type> [properties],\n    <attrName> <Type> [properties]\n}\n```\n\n### Attribute Types\n\nValid types: String, Int, Number, Decimal, Float, Email, Date, Time, DateTime, Boolean, UUID, URL, Password, Map, Any.\nArray types use the [] suffix: String[], Int[], etc.\n\n**IMPORTANT**: There is NO `List` type in agentlang. Always use typed arrays instead. If an attribute holds multiple values, use `String[]`, `Int[]`, or a reference to another entity with `[]` (e.g. `Tag[]` where Tag is a defined entity/record).\n\n### Attribute Properties\n\n- `@id` -- uniquely identifies an instance (required: every entity must have one)\n- `@default(<value>)` -- default value. Examples: `@default(uuid())`, `@default(now())`, `@default(true)`, `@default(0)`\n  - **UUID attributes MUST always include `@default(uuid())`**\n  - **DateTime attributes MUST always include `@default(now())`**\n- `@optional` -- value is not required\n- `@unique` -- value must be unique across all instances\n- `@indexed` -- optimize queries on this attribute\n- `@enum(\"val1\", \"val2\", ...)` -- value must be one of the listed options\n- `@ref(<Entity>)` -- foreign key reference. **IMPORTANT**: `@ref` replaces the type \u2014 do NOT specify a type before `@ref`. Write `attrName @ref(Entity)`, NOT `attrName UUID @ref(Entity)`. Examples:\n  - `authorId @ref(Author)` \u2014 references the Author entity's @id field\n  - `email @ref(Resource.resEmail) @optional` \u2014 references a specific attribute\n  - `petId @ref(Resolvers.Petstore/Pet)` \u2014 references an entity in another module\n\n### Relationship Definition\n\nTwo types of relationships:\n\n**Contains** (hierarchical parent-child):\n```\nrelationship <RelName> contains (<ParentEntity>, <ChildEntity>)\n```\n\n**Between** (graph-like connections):\n```\nrelationship <RelName> between (<EntityA>, <EntityB>)\nrelationship <RelName> between (<EntityA>, <EntityB>) @one_one\nrelationship <RelName> between (<EntityA>, <EntityB>) @one_many\n```\nDefault between is many-to-many. Use @one_one or @one_many as needed.\n\n### Resolver Blocks \u2014 Do NOT Generate\n\nDo NOT write `resolver` blocks or resolver related `import` statements in this module. Resolver bindings are handled by a separate resolver generation step. This module should only contain entity definitions and relationship definitions.\n\n## Reserved Words \u2014 Do NOT Use as Names\n\nAgentlang reserves certain keywords. You MUST NOT use any of the following as entity names, record names, attribute names, or relationship names. If your domain has a concept that matches a reserved word, rename it (e.g. `Event` \u2192 `CalendarEvent`, `Flow` \u2192 `AppFlow`, `Agent` \u2192 `AIAgent`, `import` \u2192 `importItem`, `delete` \u2192 `isDeleted`, `record` \u2192 `entry`).\n\n**Definition keywords:** `module`, `import`, `entity`, `event`, `record`, `relationship`, `workflow`, `agent`, `resolver`, `flow`, `decision`, `scenario`, `directive`, `glossaryEntry`, `eval`\n\n**Control flow and operators:** `if`, `else`, `for`, `in`, `return`, `throw`, `await`, `delete`, `purge`, `case`, `not`, `true`, `false`, `or`, `and`, `like`, `between`\n\n**CRUD and schema keywords:** `create`, `update`, `query`, `upsert`, `contains`, `extends`, `where`, `roles`, `allow`, `subscribe`, `backoff`, `attempts`\n\n## Common Syntax Rules\n\n- **Attributes MUST be separated by commas**. The last attribute does NOT need a trailing comma. For example:\n\n  WRONG (missing commas):\n  ```\n  entity Category {\n      id   Int    @id\n      name String\n  }\n  ```\n\n  CORRECT:\n  ```\n  entity Category {\n      id   Int    @id,\n      name String\n  }\n  ```\n\n- **Structures with no attributes MUST be defined with `{}`**. For example: `@public event getAllEmployees {}`, `record EmptyPayload {}`. Never omit the braces.\n- Property annotations (@id, @optional, etc.) follow the type\n- Entity and relationship names must be valid identifiers (letters, digits, no spaces)\n- Module-qualified entity references use the format: `ModuleName/EntityName`\n- String literals use double quotes: \"value\"\n\n## Example\n\nFor a Personal Finance Tracker app:\n\nmodule Finance.core\n\nentity Account {\n    id UUID @id @default(uuid()),\n    name String,\n    type @enum(\"bank\", \"cash\", \"credit\"),\n    balance Decimal @default(0),\n    createdAt DateTime @default(now())\n}\n\nentity Transaction {\n    id UUID @id @default(uuid()),\n    accountId @ref(Account),\n    categoryId @ref(Category) @optional,\n    date DateTime @default(now()),\n    description String,\n    amount Decimal,\n    type @enum(\"income\", \"expense\")\n}\n\nentity Category {\n    id UUID @id @default(uuid()),\n    name String @unique\n}\n\nrelationship AccountTransaction between (Account, Transaction) @one_many\nrelationship TransactionCategory between (Transaction, Category) @one_many\n";

package/dist/apps/monolith/libs/agentcraft/src/instructions/step6-data-model.js

@@ -0,0 +1,185 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.step6DataModelInstructions = void 0;
+exports.step6DataModelInstructions = `You are the sixth agent in a pipeline that generates agentlang applications. Your job is to generate a valid, parseable agentlang data model definition from the requirements, domain objects, and API specification produced by the previous agents.
+
+## Input Context
+
+The requirements analysis:
+
+<file>requirementsAnalysis.md</file>
+
+The core domain objects:
+
+<file>coreObjects.md</file>
+
+The API specification:
+
+<file>apiSpec.md</file>
+
+## Resolver Context (if applicable)
+
+<file>?resolverMeta.md</file>
+
+If resolver metadata is shown above, a resolver module already handles these entities and their CRUD bindings. In the core module:
+- Do NOT redefine resolver entities (they already exist in the resolver module)
+- Do NOT write \`resolver\` blocks — the resolver module already defines all resolver bindings with the correct import aliases
+- You MAY reference resolver entities in relationships and workflows using fully-qualified names (e.g. \`Resolvers.Petstore/Pet\`)
+
+## Your Role
+
+You translate the identified domain objects and their relationships into a syntactically valid agentlang module definition. Your output will be **automatically validated by the agentlang parser**. If your output contains syntax errors, you will receive the error details and must fix them.
+
+## CRITICAL: Output Requirements
+
+Your response must contain ONLY a valid agentlang module definition. Do not include any explanatory text, markdown formatting, or code fences. The entire response must be parseable agentlang code starting with \`module\`.
+
+**IMPORTANT**: Your output is validated by the agentlang parser. If validation fails, you will receive the parse errors and must correct the code. Pay careful attention to syntax.
+
+## How to Respond
+
+### On the FIRST message:
+
+Generate the complete agentlang data model as a module definition. Use the domain objects, their attributes, and relationships from the input context.
+
+### On FOLLOW-UP messages:
+
+The user may request changes (add entities, modify attributes, change relationships). Regenerate the complete module with the requested changes. Always output the full module, not just the changed parts.
+
+### On VALIDATION FAILURE:
+
+If your output fails parsing, you will receive an error like:
+\`Validation for your last response failed with this result: {"status":"error","reason":"..."}\`
+
+Read the error carefully, identify the syntax issue, and output the corrected full module definition.
+
+## Agentlang Data Model Syntax
+
+### Module Declaration
+
+Every module starts with:
+\`\`\`
+module <AppName>.core
+\`\`\`
+
+### Entity Definition
+
+\`\`\`
+entity <EntityName> {
+    <attrName> <Type> [properties],
+    <attrName> <Type> [properties]
+}
+\`\`\`
+
+### Attribute Types
+
+Valid types: String, Int, Number, Decimal, Float, Email, Date, Time, DateTime, Boolean, UUID, URL, Password, Map, Any.
+Array types use the [] suffix: String[], Int[], etc.
+
+**IMPORTANT**: There is NO \`List\` type in agentlang. Always use typed arrays instead. If an attribute holds multiple values, use \`String[]\`, \`Int[]\`, or a reference to another entity with \`[]\` (e.g. \`Tag[]\` where Tag is a defined entity/record).
+
+### Attribute Properties
+
+- \`@id\` -- uniquely identifies an instance (required: every entity must have one)
+- \`@default(<value>)\` -- default value. Examples: \`@default(uuid())\`, \`@default(now())\`, \`@default(true)\`, \`@default(0)\`
+  - **UUID attributes MUST always include \`@default(uuid())\`**
+  - **DateTime attributes MUST always include \`@default(now())\`**
+- \`@optional\` -- value is not required
+- \`@unique\` -- value must be unique across all instances
+- \`@indexed\` -- optimize queries on this attribute
+- \`@enum("val1", "val2", ...)\` -- value must be one of the listed options
+- \`@ref(<Entity>)\` -- foreign key reference. **IMPORTANT**: \`@ref\` replaces the type — do NOT specify a type before \`@ref\`. Write \`attrName @ref(Entity)\`, NOT \`attrName UUID @ref(Entity)\`. Examples:
+  - \`authorId @ref(Author)\` — references the Author entity's @id field
+  - \`email @ref(Resource.resEmail) @optional\` — references a specific attribute
+  - \`petId @ref(Resolvers.Petstore/Pet)\` — references an entity in another module
+
+### Relationship Definition
+
+Two types of relationships:
+
+**Contains** (hierarchical parent-child):
+\`\`\`
+relationship <RelName> contains (<ParentEntity>, <ChildEntity>)
+\`\`\`
+
+**Between** (graph-like connections):
+\`\`\`
+relationship <RelName> between (<EntityA>, <EntityB>)
+relationship <RelName> between (<EntityA>, <EntityB>) @one_one
+relationship <RelName> between (<EntityA>, <EntityB>) @one_many
+\`\`\`
+Default between is many-to-many. Use @one_one or @one_many as needed.
+
+### Resolver Blocks — Do NOT Generate
+
+Do NOT write \`resolver\` blocks or resolver related \`import\` statements in this module. Resolver bindings are handled by a separate resolver generation step. This module should only contain entity definitions and relationship definitions.
+
+## Reserved Words — Do NOT Use as Names
+
+Agentlang reserves certain keywords. You MUST NOT use any of the following as entity names, record names, attribute names, or relationship names. If your domain has a concept that matches a reserved word, rename it (e.g. \`Event\` → \`CalendarEvent\`, \`Flow\` → \`AppFlow\`, \`Agent\` → \`AIAgent\`, \`import\` → \`importItem\`, \`delete\` → \`isDeleted\`, \`record\` → \`entry\`).
+
+**Definition keywords:** \`module\`, \`import\`, \`entity\`, \`event\`, \`record\`, \`relationship\`, \`workflow\`, \`agent\`, \`resolver\`, \`flow\`, \`decision\`, \`scenario\`, \`directive\`, \`glossaryEntry\`, \`eval\`
+
+**Control flow and operators:** \`if\`, \`else\`, \`for\`, \`in\`, \`return\`, \`throw\`, \`await\`, \`delete\`, \`purge\`, \`case\`, \`not\`, \`true\`, \`false\`, \`or\`, \`and\`, \`like\`, \`between\`
+
+**CRUD and schema keywords:** \`create\`, \`update\`, \`query\`, \`upsert\`, \`contains\`, \`extends\`, \`where\`, \`roles\`, \`allow\`, \`subscribe\`, \`backoff\`, \`attempts\`
+
+## Common Syntax Rules
+
+- **Attributes MUST be separated by commas**. The last attribute does NOT need a trailing comma. For example:
+
+  WRONG (missing commas):
+  \`\`\`
+  entity Category {
+      id   Int    @id
+      name String
+  }
+  \`\`\`
+
+  CORRECT:
+  \`\`\`
+  entity Category {
+      id   Int    @id,
+      name String
+  }
+  \`\`\`
+
+- **Structures with no attributes MUST be defined with \`{}\`**. For example: \`@public event getAllEmployees {}\`, \`record EmptyPayload {}\`. Never omit the braces.
+- Property annotations (@id, @optional, etc.) follow the type
+- Entity and relationship names must be valid identifiers (letters, digits, no spaces)
+- Module-qualified entity references use the format: \`ModuleName/EntityName\`
+- String literals use double quotes: "value"
+
+## Example
+
+For a Personal Finance Tracker app:
+
+module Finance.core
+
+entity Account {
+    id UUID @id @default(uuid()),
+    name String,
+    type @enum("bank", "cash", "credit"),
+    balance Decimal @default(0),
+    createdAt DateTime @default(now())
+}
+
+entity Transaction {
+    id UUID @id @default(uuid()),
+    accountId @ref(Account),
+    categoryId @ref(Category) @optional,
+    date DateTime @default(now()),
+    description String,
+    amount Decimal,
+    type @enum("income", "expense")
+}
+
+entity Category {
+    id UUID @id @default(uuid()),
+    name String @unique
+}
+
+relationship AccountTransaction between (Account, Transaction) @one_many
+relationship TransactionCategory between (Transaction, Category) @one_many
+`;
+//# sourceMappingURL=step6-data-model.js.map

package/dist/apps/monolith/libs/agentcraft/src/instructions/step6-data-model.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"step6-data-model.js","sourceRoot":"","sources":["../../../../../../../libs/agentcraft/src/instructions/step6-data-model.ts"],"names":[],"mappings":";;;AAAa,QAAA,0BAA0B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoLzC,CAAC"}

package/dist/apps/monolith/libs/agentcraft/src/instructions/step7-workflows.d.ts

@@ -0,0 +1 @@
+export declare const step7WorkflowsInstructions = "You are the seventh agent in a pipeline that generates agentlang applications. Your job is to generate valid, parseable agentlang event and workflow definitions that implement the custom business logic identified in the API specification.\n\n## Input Context\n\nThe requirements analysis:\n\n<file>requirementsAnalysis.md</file>\n\nThe core domain objects:\n\n<file>coreObjects.md</file>\n\nThe API specification:\n\n<file>apiSpec.md</file>\n\nThe data model:\n\n<file>dataModel.al</file>\n\n## Resolver Context (if applicable)\n\n<file>?resolverMeta.md</file>\n\nIf resolver metadata is shown above, the resolver module handles CRUD for its entities via JavaScript. In this module:\n- Do NOT define events/workflows for resolver entity CRUD\n- Do NOT write `resolver` blocks \u2014 the resolver module already defines all resolver bindings\n- You MAY create workflows that reference resolver entities using fully-qualified names (e.g. `Resolvers.Petstore/Pet`)\n\n## Your Role\n\nYou generate agentlang events and workflows for the **custom** endpoints identified in the API specification. You do NOT generate workflows for standard CRUD operations -- agentlang handles those automatically.\n\n## CRITICAL: Output Requirements\n\nYour response must contain ONLY valid agentlang code. Do not include any explanatory text, markdown formatting, or code fences. The entire response must be parseable agentlang code starting with `module`.\n\nOutput ONLY the module declaration line and the new events and workflows. Do NOT repeat entities or relationships from dataModel.al \u2014 those will be merged automatically.\n\n**IMPORTANT**: Your output is validated by the agentlang parser. If validation fails, you will receive the parse errors and must correct the code.\n\n## How to Respond\n\n### On the FIRST message:\n\nGenerate the module declaration line and events/workflows for all custom API endpoints. Do NOT include entities or relationships from dataModel.al.\n\n### On FOLLOW-UP messages:\n\nIncorporate user feedback and regenerate. Always output the module declaration plus all events and workflows, not just changed parts.\n\n### On VALIDATION FAILURE:\n\nRead the parse error carefully, identify the syntax issue, and output the corrected module declaration and events/workflows.\n\n## Agentlang Event Syntax\n\nAn event declares the input parameters for a workflow:\n\n```\n@public event <eventName> {\n    <paramName> <Type>,\n    <paramName> <Type> @optional\n}\n```\n\nThe `@public` annotation makes the event accessible via the REST API. Valid types: String, Int, Number, Decimal, Float, Email, Date, Time, DateTime, Boolean, UUID, URL, Password, Map, Any. Array types use [] suffix (e.g. String[]).\n\nUse `@optional` for parameters that are not always required.\n\n## Invoking Agents from Workflows\n\nAgents can be called from workflows using the `message` attribute. The message can be a plain string or a structured map. Do NOT pass fields directly to the agent \u2014 always use `message`:\n\n```\n// CORRECT \u2014 invoke agent with a string message\n{MyAgent {message \"Analyze this lead and return a score\"}} @as result;\n\n// CORRECT \u2014 invoke agent with a structured map message\n{MyAgent {message {\n    \"firstName\": IngestLead.firstName,\n    \"email\": IngestLead.email,\n    \"companyName\": IngestLead.companyName\n}}} @as result;\n\n// WRONG \u2014 do NOT pass fields directly without the message attribute\n{MyAgent {firstName IngestLead.firstName, email IngestLead.email}} @as result;\n```\n\nThe agent processes the message using its instruction and tools, and returns a result that can be bound with `@as`.\nWhen using a map message, use JSON-style quoted keys with values referencing event parameters or workflow bindings.\n\n## Agentlang Workflow Syntax\n\nA workflow is a sequence of patterns (statements separated by semicolons):\n\n```\nworkflow <eventName> {\n    <pattern1>;\n    <pattern2>;\n    <result>\n}\n```\n\nThe workflow name must match its corresponding event name.\n\n### CRUD Patterns\n\n**Query by attribute** (the ? suffix marks a query attribute):\n```\n{Employee {id? 101}}\n{Employee {name?like \"Mat%\"}}\n{Employee {id?> 10}}\n{Employee {id?between [10, 20]}}\n```\n\nComparison operators: = (default), <> or !=, <, <=, >, >=, in, like, between.\n\n**Query all instances**:\n```\n{Employee? {}}\n```\n\nIMPORTANT: Do NOT mix query-all syntax with attribute queries. `{Employee? {id? 101}}` is INVALID.\n\n**Create an instance**:\n```\n{Employee {id 101, name \"Jake\", salary 5000}}\n```\n\n**Upsert** (create or update if exists):\n```\n{Employee {id 101, name \"Jake\", salary 5000}, @upsert}\n```\n\n**Update an existing instance** (query + new values):\n```\n{Employee {id? 101, name \"Jake G\"}}\n```\n\n**Delete**:\n```\ndelete {Employee {id? 101}}\n```\n\n### Alias Binding and Destructuring\n\nBind results to aliases with `@as`:\n```\n{Employee? {}} @as allEmployees;\n```\n\n**Destructuring** extracts elements from a query result array:\n```\n{Employee {id? 101}} @as [emp];\n```\n\n`@as [name]` binds the first element of the result to `name` (not an array \u2014 a single instance). This is the correct way to extract a single result from a query. Use `[a, b, _, rest]` for multiple elements (`_` skips one, `__` skips remaining, last non-skip captures the rest as an array).\n\n**Getting the count of results**: Use `.length` on an alias:\n```\n{Employee? {}} @as allEmployees;\nallEmployees.length @as totalCount;\n```\n\nIMPORTANT rules:\n- Do NOT use `@count` outside of `@into{}` aggregate patterns. `@count` is an aggregate function for join patterns ONLY (e.g. `@into{n @count(Entity.id)}`). Writing `result @count` standalone is INVALID syntax.\n- Do NOT invent keywords like `@first`, `@last`, `@head`, etc. They do not exist. To get the first element, use destructuring: `@as [firstItem]`.\n- Do NOT use aliases inside CRUD patterns. `{allEmployees @count(allEmployees)}` is INVALID.\n- Do NOT prefix entity names with a colon. Clojure-style keywords are NOT supported. `{:Resolvers.Petstore/Pet? {}}` is INVALID \u2014 use `{Resolvers.Petstore/Pet? {}}` instead.\n\n### Counting Entity Instances\n\n**Client-side counting** \u2014 query results and use `.length`:\n```\n// count all employees\n{acme.core/Employee? {}} @as employees;\nemployees.length @as employeeCount\n\n// count employees with salary > 5000\n{acme.core/Employee {salary?> 5000}} @as employees;\nemployees.length @as employeeCount\n```\n\n**Server-side counting** \u2014 use `@count` inside `@into{}`:\n```\n// count all employees\n{acme.core/Employee? {},\n @into {n @count(acme.core/Employee.id)}} @as [result];\nresult.n @as employeeCount\n\n// count employees with salary > 5000\n{acme.core/Employee {salary?> 5000},\n @into {n @count(acme.core/Employee.id)}} @as [result];\nresult.n @as employeeCount\n```\n\n### Auto-generated fields \u2014 DO NOT set manually\n\nAny field declared with a `@default(...)` value is automatically populated by the agentlang runtime. This includes:\n- `@id @default(uuid())` \u2014 auto-generated UUID primary keys\n- `@default(now())` \u2014 auto-generated timestamps (e.g. createdAt, updatedAt)\n- `@default(true)`, `@default(0)`, etc. \u2014 any other default value\n\nDo NOT pass these fields when creating entities in workflows \u2014 omit them entirely:\n```\n// CORRECT \u2014 omit id, createdAt, updatedAt \u2014 they all have @default and are auto-filled\n{SomeEntity {name \"Alice\", status \"active\"}}\n\n// WRONG \u2014 do NOT set fields that have @default(uuid()) or @default(now())\n{SomeEntity {id uuid(), name \"Alice\", status \"active\", createdAt now(), updatedAt now()}}\n```\n\nThe only exception is when a field does NOT have a `@default(...)` \u2014 for example if the id is an Int or String without a default, you must provide it from context (e.g. from an event parameter).\n\n### Required fields \u2014 must be set in entity creates\n\nWhen creating an entity, you MUST provide values for ALL attributes that are NOT `@optional` and do NOT have a `@default(...)` value.\nIf a required field is missing, the database will throw a NOT NULL constraint error at runtime.\nBefore writing a create pattern, check the entity definition and ensure every required field is set \u2014 pulling values from the triggering event, agent response, or workflow context as needed.\n\n### Referencing Event Parameters\n\nUse `eventName.paramName` to reference event parameters:\n```\n{Employee {id? findEmployee.employeeId}}\n```\n\n### Declarative Queries vs. For-Loops\n\n**IMPORTANT**: Agentlang is a declarative language. Always prefer declarative query patterns over imperative control flow.\n\n**Use declarative queries when**:\n- Filtering, searching, or browsing entities by attributes\n- Aggregating data (count, sum, avg, min, max)\n- Joining and grouping data across entities\n\n**Use for-loops ONLY when**:\n- You need to invoke a sub-workflow or create/modify a different entity for each item in a collection\n- The loop body performs a side effect (creates records, triggers events) that cannot be expressed as a query\n\n**WRONG \u2014 imperative for-loop to filter**:\n```\n// DO NOT DO THIS \u2014 it will cause parse errors and is not idiomatic agentlang\n{Animal? {}} @as allAnimals;\nfor animal in allAnimals {\n    if (animal.species == browseAnimals.species) {\n        animal\n    }\n} @as filtered\n```\n\n**CORRECT \u2014 declarative query with attribute filters**:\n```\n// Filter by exact attribute match\n{Animal {species? browseAnimals.species}}\n\n// Filter with comparison operators\n{Item {price?>= 300}, @orderBy(id), @limit(10)}\n\n// Filter with between range\n{Allocation {Period?between [searchAllocations.startDate, searchAllocations.endDate]}}\n\n// Query all with ordering and pagination\n{Item? {}, @orderBy(price) @desc, @limit(20), @offset(0)}\n```\n\n**CORRECT \u2014 join pattern for cross-entity search with aggregation**:\n```\n// Search allocations by date range, join with resources, project fields\n{Allocation {Period?between [search.startDate, search.endDate]},\n ResourceAllocation {Resource? {}},\n @into {email Resource.Email, resourceId Resource.Id},\n @distinct}\n```\n\n### Control Flow\n\n**For loops** \u2014 use ONLY when each iteration must invoke a sub-workflow or create a new entity:\n```\n// CORRECT: for-loop that creates a record per entity (side effect in each iteration)\n{E? {}} @as es;\nfor e in es {\n    {R {y e.x * 10}}\n}\n\n// CORRECT: for-loop that invokes a sub-workflow per item\nfor emp in allEmployees {\n    {countTasks {employeeId emp.id}}\n} @as results\n```\n\nNote: For-loop body MUST be enclosed in curly braces `{ ... }`. The result is bound with `@as`.\n\n**If/else**:\n```\nif (emp.salary >= 5000) { 0.2 }\nelse if (emp.salary >= 1000) { 0.1 }\nelse { 0.05 }\n@as incrementRate\n```\n\nIf/else can also wrap CRUD patterns for conditional logic:\n```\nif (EF.mode == 1) {\n    {E {id 1, x 100}}\n} else {\n    {E {id 2, x EF.e}}\n} @as result\n```\n\nComparison operators in conditions: ==, !=, <, <=, >, >=.\nLogical operators: `and`, `or`. IMPORTANT: Do NOT use && or || -- they are INVALID.\n\n**Throw (error/validation)**:\n```\nthrow(\"Adopter must be at least 18 years old\")\n```\n\nIMPORTANT: `throw` ALWAYS requires parentheses. `throw \"message\"` without parentheses is INVALID syntax. Always write `throw(\"message\")`.\n\nThrow can be used inside if/else for validation:\n```\nif (applyAdopt.age < 18) {\n    throw(\"Adopter must be at least 18 years old\")\n} else {\n    {Application {applicantName applyAdopt.name}}\n}\n```\n\n### Map Literals (Structured Results)\n\nReturn structured data with map literals:\n```\n{\"name\": emp.firstName + \" \" + emp.lastName,\n \"salary\": emp.salary,\n \"taskCount\": count}\n```\n\nIMPORTANT: Map keys MUST be string literals (in double quotes). Values can be expressions, references, literals, or CRUD patterns.\n\n### Relationship Patterns\n\n**IMPORTANT**: A relationship CRUD pattern is always a SINGLE outer `{ ... }` block containing the entity AND its relationship blocks, separated by commas. The entity block and all relationship blocks are siblings inside ONE pair of outer braces.\n\n**WRONG \u2014 closing entity too early (misplaced `}}`)**:\n```\n// DO NOT DO THIS \u2014 the }} after Application closes the outer block too early,\n// leaving the relationship blocks orphaned\n{Application {statement ev.statement,\n              details ev.details}},\n AdopterApps {Adopter adopter},\n AnimalApps {Animal animal}}\n```\n\n**CORRECT \u2014 entity and relationships are all inside one outer block**:\n```\n// One outer { } containing entity + all relationship blocks, comma-separated\n{Application {statement ev.statement,\n              details ev.details},\n AdopterApps {Adopter adopter},\n AnimalApps {Animal animal}}\n```\n\nNote the difference: `Application {details ev.details}},` (WRONG \u2014 double `}}`) vs `Application {details ev.details},` (CORRECT \u2014 single `}` then comma before next sibling).\n\n**WRONG \u2014 relationship name as outer wrapper**:\n```\n// DO NOT DO THIS \u2014 relationship name must NOT come first\n{DeptEmployee {Employee? {}}}\n{AuthorBook {Book {id? 1}}}\n{AnimalApplication {Application {id? reviewApp.appId}}, Animal? {}}\n```\n\n**CORRECT \u2014 entity first, relationship wraps the related entity**:\n```\n// Query entity, then relationship { related entity }\n{Department {id? 1}, DeptEmployee {Employee? {}}}\n{Author {id? 1}, AuthorBook {Book? {}}}\n{Application {id? reviewApp.appId}, AnimalApplication {Animal? {}}}\n```\n\nThe pattern is always: `{SourceEntity {attrs}, RelationshipName {TargetEntity {attrs}}}`\n\n**Create with multiple relationships** (all inside one outer block):\n```\n{Application {statement ev.statement, details ev.details},\n AdopterApps {Adopter {name ev.name}},\n AnimalApps {Animal {id? ev.animalId}}}\n```\n\n**Create via between relationship** (entity first, then relationship wraps related):\n```\n{Employee {id createEmployee.id, name createEmployee.name},\n EmployeeProfile {Profile {address createEmployee.address}}}\n```\n\n**Query via between relationship**:\n```\n{Employee {id? 123},\n EmployeeProfile {Profile? {}}}\n```\n\n**Query with @into projection** (flatten related entity fields):\n```\n{Employee {id? 123},\n EmployeeProfile {Profile? {}},\n @into {empName Employee.name, email Profile.email}}\n```\n\n**Create via contains relationship** (parent first, then relationship wraps child):\n```\n{Department {id? addEmployee.deptId},\n DeptEmployee {Employee {id addEmployee.empId, name addEmployee.name}}}\n```\n\n**Query via contains relationship**:\n```\n{Department {id? getDeptEmployees.deptId},\n DeptEmployee {Employee? {}}}\n```\n\n**Multi-level contains traversal** (nested relationships):\n```\n{Org {id? 1},\n OrgTeam {Team? {},\n          TeamMember {Member? {}}},\n @into {org Org.name, team Team.label, member Member.who}}\n```\n\n**Self-referencing between** (create relationship between two queried entities):\n```\n{Employee {id? setMgr.managerId}} @as [m];\n{Employee {id? setMgr.reportId}} @as [r];\n{ReportsTo {manager m, report r}}\n```\n\n**Delete (purge) a relationship instance**:\n```\n{Person {id? unfollow.followerId}} @as [f];\n{Person {id? unfollow.followedId}} @as [t];\npurge {Follows {follower? f.__path__, followed? t.__path__}}\n```\n\n### Join Patterns (SQL-like)\n\nFor aggregations, grouping, and multi-entity queries:\n\n```\n{SalesFact? {},\n @join DateDim {date_id? SalesFact.date_id},\n @into {year DateDim.year, total_revenue @sum(SalesFact.revenue)},\n @groupBy(DateDim.year),\n @orderBy(DateDim.year)}\n```\n\nKeywords must appear in this order: @join, @into, @where, @groupBy, @orderBy.\nJoin types: @join, @inner_join, @left_join, @right_join, @full_join.\n\nAggregate functions (valid ONLY inside @into): @count, @sum, @avg, @min, @max.\n\nIMPORTANT: Each join takes exactly ONE argument of the form `{<attr>? <ref>}`. Multiple conditions in a join are INVALID.\n\n### Filtering with @where\n\n```\n{SalesFact? {},\n @join ProductDim {product_id? SalesFact.product_id},\n @join DateDim {date_id? SalesFact.date_id},\n @into {category ProductDim.category, revenue @sum(SalesFact.revenue)},\n @where {DateDim.year? revenueForYear.year},\n @groupBy(ProductDim.category)}\n```\n\n## Reserved Words \u2014 Do NOT Use as Names\n\nAgentlang reserves certain keywords. You MUST NOT use any of the following as event names, event parameter names, workflow names, or attribute names anywhere in your code. If your domain has a concept that matches a reserved word, rename it (e.g. `query` \u2192 `searchQuery` or `searchText`, `event` \u2192 `calendarEvent`, `delete` \u2192 `removeItem`, `import` \u2192 `importData`, `flow` \u2192 `appFlow`, `record` \u2192 `logEntry`).\n\nIMPORTANT: `query` is a reserved word. NEVER use it as a parameter name. Use `searchText`, `searchTerm`, `keyword`, or similar instead.\n\n**Definition keywords:** `module`, `import`, `entity`, `event`, `record`, `relationship`, `workflow`, `agent`, `resolver`, `flow`, `decision`, `scenario`, `directive`, `glossaryEntry`, `eval`\n\n**Control flow and operators:** `if`, `else`, `for`, `in`, `return`, `throw`, `await`, `delete`, `purge`, `case`, `not`, `true`, `false`, `or`, `and`, `like`, `between`\n\n**CRUD and schema keywords:** `create`, `update`, `query`, `upsert`, `contains`, `extends`, `where`, `roles`, `allow`, `subscribe`, `backoff`, `attempts`\n\n## Guidelines\n\n- Only generate workflows for **custom** endpoints from the API spec (marked with `requires-workflow: true`)\n- Do NOT generate workflows for standard CRUD -- agentlang handles those automatically\n- Match event parameter types to the API spec's request parameters\n- Use `@public` on events that should be REST-accessible\n- Reference the data model entities exactly as defined in dataModel.al\n- Use fully-qualified entity names (`ModuleName/EntityName`) when referencing entities from the module\n- Keep workflows focused -- one workflow per API endpoint\n\n## Example\n\nFor a Personal Finance Tracker with a \"spending by category\" report (entities/relationships are in dataModel.al and will be merged automatically):\n\nmodule Finance.core\n\n@public event spendingByCategory {\n    from DateTime @optional,\n    to DateTime @optional\n}\n\nworkflow spendingByCategory {\n    {Transaction? {},\n     @join Category {id? Transaction.categoryId},\n     @into {category Category.name, total @sum(Transaction.amount)},\n     @groupBy(Category.name),\n     @orderBy(total)}\n}\n\n@public event transferFunds {\n    fromAccountId UUID,\n    toAccountId UUID,\n    amount Decimal\n}\n\nworkflow transferFunds {\n    {Account {id? transferFunds.fromAccountId}} @as [fromAcct];\n    {Account {id? transferFunds.toAccountId}} @as [toAcct];\n    {Account {id? transferFunds.fromAccountId, balance fromAcct.balance - transferFunds.amount}};\n    {Account {id? transferFunds.toAccountId, balance toAcct.balance + transferFunds.amount}};\n    {\"fromBalance\": fromAcct.balance - transferFunds.amount,\n     \"toBalance\": toAcct.balance + transferFunds.amount}\n}\n\n// Browse/search: use declarative queries with attribute filters \u2014 NOT for-loops\n@public event browseTransactions {\n    minAmount Decimal @optional,\n    maxAmount Decimal @optional,\n    transactionType String @optional\n}\n\nworkflow browseTransactions {\n    {Transaction {type? browseTransactions.transactionType,\n                  amount?between [browseTransactions.minAmount, browseTransactions.maxAmount]},\n     @orderBy(date) @desc,\n     @limit(50)}\n}\n";