deepclause-sdk 0.0.88 → 0.1.0

package/dist/system/assets/skills/security-planner.dml

@@ -1,337 +0,0 @@
-% Security planner — generates a multi-strategy DML plan for finding bugs and vulnerabilities.
-% The planner itself does NOT analyze code. It only generates strategies and task descriptions.
-% Analysis happens when the generated plan is executed.
-
-tool(consult_recipes(Query, Result),
-     "Search the recipe library for workflow guidance and conventions.") :-
-    exec(consult_recipes(query: Query, max_results: 3), Result).
-
-tool(search_web(Query, Results),
-     "Search the web for context about the target project or technology stack.") :-
-    exec(web_search(query: Query), Results).
-
-tool(ask_user(Prompt, Response),
-    "Ask the user for clarification about scope, severity thresholds, or context.") :-
-    exec(ask_user(prompt: Prompt), Result),
-    get_dict(user_response, Result, Response).
-
-agent_main(Request) :-
-    load_dml_reference(DmlReference),
-    resolve_model_info(ModelId, Complexity, Reasoning, TaskCount),
-    format(string(SystemPrompt), "You are a SECURITY PLAN GENERATOR. You do NOT analyze code yourself. You only create plans for other agents to execute.~n~nTarget: ~w~n~nYour job:~n1. Generate a short slug for the plan file.~n2. Generate ~w fundamentally different strategies for finding bugs and vulnerabilities.~n3. For each strategy, generate a task list with tool assignments and reasoning effort.~n4. The assembler creates a DML file with one agent_main clause per strategy.~n~nRules:~n- Do NOT run shell commands, read files, or examine the codebase. That is the job of the generated plan.~n- Generate strategies based on the target description and your knowledge of common vulnerability patterns.~n- Each strategy must use a different analysis approach (static patterns, data flow, dependency audit, config review, input validation, auth review, etc.).~n- Each strategy gets 3 to 7 analysis tasks plus a final verification task (added automatically).~n- The final task in each strategy asks the model to write findings to a file if vulnerabilities are found, or fail if nothing is found.~n~nDML language reference:~n~n~s", [Request, TaskCount, DmlReference]),
-    system(SystemPrompt),
-
-    task("Create a short file-safe slug for this security analysis target: '{Request}'.~nRequirements:~n- lowercase letters, digits, and underscores only~n- 2 to 6 words when possible~n- no file extension~n- prefix with 'audit_' if not already present~nStore only the slug in PlanSlug.", string(PlanSlug)),
-
-    generate_strategies(Request, TaskCount, Strategies),
-
-    generate_all_strategy_tasks(Request, Strategies, StrategyPlans),
-
-    make_directory_path('plans'),
-    format(string(FilePath), "plans/~w.dml", [PlanSlug]),
-
-    build_review_message(FilePath, StrategyPlans, ReviewMessage),
-    output(ReviewMessage),
-
-    output("Assembling multi-strategy security plan file..."),
-    assemble_multi_strategy_dml(StrategyPlans, PlanDml),
-    exec(write_file(path: FilePath, content: PlanDml), _),
-    exec(validate_dml(dml_file: FilePath), ValidationResult),
-    finish_plan_creation(FilePath, PlanSlug, ValidationResult, ReviewMessage).
-
-%% resolve_model_info(-ModelId, -Complexity, -Reasoning, -TaskCount)
-resolve_model_info(ModelId, Complexity, Reasoning, TaskCount) :-
-    (   catch(
-            (   param(model_info, ModelInfo),
-                is_dict(ModelInfo),
-                get_dict(modelId, ModelInfo, ModelId),
-                (   get_dict(complexity, ModelInfo, C) -> Complexity = C ; Complexity = medium ),
-                (   get_dict(reasoning, ModelInfo, R), R == true -> Reasoning = true ; Reasoning = false )
-            ),
-            _,
-            fail
-        )
-    ->  true
-    ;   ModelId = "unknown",
-        Complexity = medium,
-        Reasoning = false
-    ),
-    task_count_for_complexity(Complexity, TaskCount).
-
-task_count_for_complexity("high", "3").
-task_count_for_complexity("medium", "3").
-task_count_for_complexity("low", "3").
-task_count_for_complexity(high, "3").
-task_count_for_complexity(medium, "3").
-task_count_for_complexity(low, "3").
-
-%% generate_strategies(+Request, +TaskCount, -Strategies)
-generate_strategies(Request, TaskCount, Strategies) :-
-    task("Generate {TaskCount} fundamentally different security analysis strategies for this target:
-
-'{Request}'
-
-Each strategy must use a different analysis approach:
-- Different tooling (grep vs static analyzer vs dependency scanner vs manual review)
-- Different vulnerability classes (injection vs auth vs config vs crypto vs deps)
-- Different code perspectives (input paths vs output paths vs state management vs error handling)
-
-For each strategy provide:
-- A short name identifying the approach
-- A colon
-- A brief description of what it looks for and how
-
-One strategy per line. Each strategy should be independently capable of finding real issues.
-
-Store the list of strategy strings in Strategies.", list(string(Strategies))).
-
-%% generate_all_strategy_tasks(+Request, +Strategies, -StrategyPlans)
-generate_all_strategy_tasks(_Request, [], []).
-generate_all_strategy_tasks(Request, [Strategy|RestStrategies], [plan{strategy: Strategy, steps: Steps}|RestPlans]) :-
-    generate_strategy_tasks(Request, Strategy, Steps),
-    generate_all_strategy_tasks(Request, RestStrategies, RestPlans).
-
-%% generate_strategy_tasks(+Request, +Strategy, -Steps)
-generate_strategy_tasks(Request, Strategy, Steps) :-
-    (   param(model_info, ModelInfo)
-    ->  (   get_dict(reasoning, ModelInfo, R), R == true
-        ->  ReasoningNote = "The execution model supports reasoning. Assign reasoning effort per task: none, low, medium, or high."
-        ;   ReasoningNote = "The execution model does not support reasoning. Set reasoning to 'none' for all tasks."
-        )
-    ;   ReasoningNote = "Set reasoning to 'none' for all tasks."
-    ),
-    task("List 3 to 7 focused execution tasks for this security analysis strategy.
-
-Target: {Request}
-Strategy: {Strategy}
-
-Each task should be one concrete analysis step. Be specific about what to look for and which files to examine.
-
-Available tools (use ONLY these exact names):
-- consult_recipes: Search recipe guidance and conventions
-- search_web: Search the web for advisories, docs, and references
-- search_news: Search recent news for relevant incidents or advisories
-- fetch_url: Fetch a specific advisory or documentation page
-- run_bash: Run grep, find, test, and scanner commands in the workspace
-- ask_user: Ask the user to narrow scope or clarify assumptions
-- inform_user: Send a status update
-
-{ReasoningNote}
-
-Also specify a recipe query for each task if relevant (NONE otherwise).
-
-Return four ordered lists aligned 1:1:
-- TaskDescriptions: plain task descriptions.
-- ToolSpecs: each item must be either ALL or a comma-separated list of exact tool names from the available tools list above.
-- ReasoningSpecs: each item must be exactly one of none, low, medium, high.
-- RecipeSpecs: each item must be either NONE or a recipe query string.
-
-Store the ordered task descriptions in TaskDescriptions.
-Store the ordered tool specs in ToolSpecs.
-Store the ordered reasoning specs in ReasoningSpecs.
-Store the ordered recipe specs in RecipeSpecs.", list(string(TaskDescriptions)), list(string(ToolSpecs)), list(string(ReasoningSpecs)), list(string(RecipeSpecs))),
-    (   build_steps_from_specs(TaskDescriptions, ToolSpecs, ReasoningSpecs, RecipeSpecs, Steps)
-    ->  true
-    ;   fallback_plan_steps_from_strategy(Strategy, Steps)
-    ).
-
-valid_plan_tool(consult_recipes).
-valid_plan_tool(search_web).
-valid_plan_tool(search_news).
-valid_plan_tool(fetch_url).
-valid_plan_tool(run_bash).
-valid_plan_tool(ask_user).
-valid_plan_tool(inform_user).
-
-default_plan_tools([consult_recipes, search_web, search_news, fetch_url, run_bash, ask_user, inform_user]).
-
-build_steps_from_specs([], [], [], [], []).
-build_steps_from_specs([Desc|RestDesc], [ToolSpec|RestTools], [ReasoningSpec|RestReasoning], [RecipeSpec|RestRecipes], [plan_step{description: Desc, tools: Tools, reasoning: Reasoning, recipe: Recipe}|RestSteps]) :-
-    normalize_tools_spec(ToolSpec, Tools),
-    normalize_reasoning_spec(ReasoningSpec, Reasoning),
-    normalize_recipe_spec(RecipeSpec, Recipe),
-    build_steps_from_specs(RestDesc, RestTools, RestReasoning, RestRecipes, RestSteps).
-
-normalize_tools_spec(Raw, Tools) :-
-    format(string(Text), "~w", [Raw]),
-    string_lower(Text, Lower),
-    (   Lower = "all"
-    ->  default_plan_tools(Tools)
-    ;   split_string(Text, ",", " []\t\n", Parts0),
-        include(non_empty_string, Parts0, Parts),
-        findall(ToolAtom,
-            ( member(Part, Parts),
-              tool_name_string_to_atom(Part, ToolAtom),
-              valid_plan_tool(ToolAtom)
-            ),
-            ValidTools),
-        (   ValidTools = []
-        ->  default_plan_tools(Tools)
-        ;   Tools = ValidTools
-        )
-    ).
-
-normalize_reasoning_spec(Raw, Reasoning) :-
-    format(string(Text), "~w", [Raw]),
-    string_lower(Text, Lower),
-    normalize_reasoning_label(Lower, Reasoning).
-
-normalize_reasoning_label("high", "high").
-normalize_reasoning_label("medium", "medium").
-normalize_reasoning_label("low", "low").
-normalize_reasoning_label("none", "none").
-normalize_reasoning_label(_, "none").
-
-normalize_recipe_spec(Raw, Recipe) :-
-    format(string(Text0), "~w", [Raw]),
-    normalize_space(string(Text), Text0),
-    string_lower(Text, Lower),
-    (   Lower = ""
-    ->  Recipe = "none"
-    ;   Lower = "none"
-    ->  Recipe = "none"
-    ;   Recipe = Text
-    ).
-
-tool_name_string_to_atom(Text, Atom) :-
-    string_lower(Text, Lower),
-    atom_string(Atom, Lower).
-
-non_empty_string(Text) :-
-    Text \= "".
-
-fallback_plan_steps_from_strategy(Strategy, [plan_step{description: Strategy, tools: Tools, reasoning: "none", recipe: "none"}]) :-
-    default_plan_tools(Tools).
-
-%% assemble_multi_strategy_dml(+StrategyPlans, -PlanDml)
-assemble_multi_strategy_dml(StrategyPlans, PlanDml) :-
-    conductor_tool_definitions(ToolBlock),
-    build_strategy_clauses(StrategyPlans, Clauses),
-    format(string(PlanDml), "% Generated DeepClause security analysis plan.~n% Prolog tries strategies in order; answer/1 commits on success.~n~n~s~n~n~s~nagent_main :-~n    answer(\"No vulnerabilities found by any strategy.\").~n", [ToolBlock, Clauses]).
-
-%% build_strategy_clauses(+StrategyPlans, -Clauses)
-build_strategy_clauses([], "").
-build_strategy_clauses([Plan|Rest], Clauses) :-
-    Strategy = Plan.strategy,
-    Steps = Plan.steps,
-    build_system_prompt_for_strategy(Strategy, SystemPrompt),
-    build_task_lines(Steps, TaskLines, LastSumVar),
-    format(string(StratOutput), "Starting strategy: ~w", [Strategy]),
-    format(string(StratAnswer), "Vulnerabilities found and reported via strategy: ~w. See .deepclause.tmp/findings.md for details.", [Strategy]),
-    (   LastSumVar = ""
-    ->  format(string(VerifyTask), "    task(\"If vulnerabilities were found, write a findings report to .deepclause.tmp/findings.md and succeed. If no vulnerabilities were found, fail this task.\"),~n", [])
-    ;   format(string(VerifyTask), "    task(\"Based on the analysis summary: {~w}. If vulnerabilities were found, write a findings report to .deepclause.tmp/findings.md and succeed. If no vulnerabilities were found, fail this task.\"),~n", [LastSumVar])
-    ),
-    format(string(Clause), "agent_main :-~n    system(~q),~n    output(~q),~n~s~s    answer(~q).~n~n", [SystemPrompt, StratOutput, TaskLines, VerifyTask, StratAnswer]),
-    build_strategy_clauses(Rest, RestClauses),
-    string_concat(Clause, RestClauses, Clauses).
-
-%% build_system_prompt_for_strategy(+Strategy, -SystemPrompt)
-build_system_prompt_for_strategy(Strategy, SystemPrompt) :-
-    format(string(SystemPrompt), "You are a security analyst executing a generated DeepClause plan using this strategy:~n~nStrategy: ~w~n~nWorkflow:~n- Start by understanding the codebase structure and identifying the relevant files~n- Read source files and configuration to understand the attack surface~n- Apply the strategy's analysis approach systematically~n- For each finding, record: severity (critical/high/medium/low/info), file path, line number (if applicable), description, and recommendation~n- Write findings to .deepclause.tmp/scratchpad.md (append with >>) so other strategies can see them~n- Read the scratchpad at the start: run_bash('cat .deepclause.tmp/scratchpad.md 2>/dev/null || echo empty')~n- A final verification task runs automatically after your analysis tasks: it asks you to write .deepclause.tmp/findings.md if vulnerabilities were found~n- If no vulnerabilities are found, the findings file is NOT written and this strategy fails — a different strategy is tried automatically~n- Be thorough but avoid false positives — verify each finding before reporting", [Strategy]).
-
-%% build_task_lines(+PlanSteps, -TaskLines, -LastSumVar)
-build_task_lines(Steps, TaskLines, LastSumVar) :-
-    length(Steps, Count),
-    (   Count > 0
-    ->  format(string(LastSumVar), "Sum~w", [Count])
-    ;   LastSumVar = ""
-    ),
-    build_task_lines(Steps, 1, "", TaskLines).
-
-build_task_lines([], _, _, "").
-build_task_lines([Step|Rest], Num, PrevSum, TaskLines) :-
-    build_single_task_line(Step, Num, PrevSum, Line),
-    NextNum is Num + 1,
-    format(string(VarName), "Sum~w", [Num]),
-    build_task_lines(Rest, NextNum, VarName, RestLines),
-    string_concat(Line, RestLines, TaskLines).
-
-build_single_task_line(Step, Num, PrevSum, Line) :-
-    Desc = Step.description,
-    format(string(VarName), "Sum~w", [Num]),
-    format(string(DescWithCtx), "~w. Store your findings summary in ~w.", [Desc, VarName]),
-    Tools = Step.tools,
-    Reasoning = Step.reasoning,
-    Recipe = Step.recipe,
-    format(string(BaseTask), "task(~q, string(~w))", [DescWithCtx, VarName]),
-    format(string(WithTools), "with_tools(~w, ~w)", [Tools, BaseTask]),
-    (   Reasoning \= "none"
-    ->  format(string(WithReasoning), "with_reasoning(~n        ~w~n    , ~w)", [WithTools, Reasoning])
-    ;   WithReasoning = WithTools
-    ),
-    (   Recipe \= "none"
-    ->  format(string(Line), "    with_recipe(~n        ~w~n    , '~w'),~n", [WithReasoning, Recipe])
-    ;   format(string(Line), "    ~w,~n", [WithReasoning])
-    ).
-
-%% build_review_message(+FilePath, +StrategyPlans, -ReviewMessage)
-build_review_message(FilePath, StrategyPlans, ReviewMessage) :-
-    length(StrategyPlans, Count),
-    build_strategy_review_lines(StrategyPlans, 1, StrategyLines),
-    format(string(ReviewMessage), "Proposed security analysis plan~n- Output file: ~w~n- Strategies: ~w~n~n~s", [FilePath, Count, StrategyLines]).
-
-build_strategy_review_lines([], _, "").
-build_strategy_review_lines([Plan|Rest], Num, Lines) :-
-    Strategy = Plan.strategy,
-    Steps = Plan.steps,
-    length(Steps, StepCount),
-    format(string(Current), "~w. ~w (~w tasks)~n", [Num, Strategy, StepCount]),
-    NextNum is Num + 1,
-    build_strategy_review_lines(Rest, NextNum, RestLines),
-    string_concat(Current, RestLines, Lines).
-
-finish_plan_creation(FilePath, PlanSlug, ValidationResult, FinalPlanReview) :-
-    get_dict(valid, ValidationResult, true),
-    output("Security plan validated successfully."),
-    format(string(Message), "I've created a security analysis plan in ~w.\n\n~s\nRun it with /run ~w or /~w.", [FilePath, FinalPlanReview, FilePath, PlanSlug]),
-    answer(Message).
-
-finish_plan_creation(FilePath, _, ValidationResult, _) :-
-    format(string(Message), "I wrote ~w, but the plan failed validation: ~w", [FilePath, ValidationResult]),
-    answer(Message).
-
-conductor_tool_definitions(ToolBlock) :-
-    atomics_to_string([
-        '% --- Tool predicates ---',
-        '',
-        'tool(consult_recipes(Query, Result), "Search the recipe library for workflow guidance and conventions.") :-',
-        '',
-        '    exec(consult_recipes(query: Query, max_results: 3), Result).',
-        '',
-        'tool(search_web(Query, Results), "Search the web for CVEs, security advisories, and documentation.") :-',
-        '',
-        '    exec(web_search(query: Query), Results).',
-        '',
-        'tool(search_news(Query, Results), "Search recent news for security advisories.") :-',
-        '',
-        '    exec(news_search(query: Query), Results).',
-        '',
-        'tool(fetch_url(Url, Content), "Fetch a web page for security documentation or advisory details.") :-',
-        '',
-        '    exec(url_fetch(url: Url), Result),',
-        '    get_dict(body, Result, Content).',
-        '',
-        'tool(run_bash(Command, Output), "Run a shell command. Use for grep, find, cat, static analyzers, etc.") :-',
-        '',
-        '    exec(bash(command: Command), Output).',
-        '',
-        'tool(ask_user(Prompt, Response), "Ask the user for clarification about scope or severity thresholds.") :-',
-        '',
-        '    exec(ask_user(prompt: Prompt), Result),',
-        '    get_dict(user_response, Result, Response).',
-        '',
-        'tool(inform_user(Message, Result), "Send a status update.") :-',
-        '    output(Message),',
-        '    Result = "ok".'
-    ], "\n", ToolBlock).
-
-load_dml_reference(DmlReference) :-
-    (   exists_file('.deepclause/docs/DML_REFERENCE.md')
-    ->  read_file('.deepclause/docs/DML_REFERENCE.md', DmlReference)
-    ;   DmlReference = "DML reference unavailable. Use standard DeepClause DML conventions."
-    ).
-
-agent_main(Request) :-
-    format(string(Message), "I could not create a valid security analysis plan for this target: ~w. Try specifying the target more precisely (e.g., a directory path, file pattern, or specific concern).", [Request]),
-    answer(Message).

package/dist/system/assets/skills/skill-creator.dml

@@ -1,187 +0,0 @@
-% ============================================================================
-% _skill-creator v4 - Creates, tests, and deploys DML skills.
-%
-% Four-phase pipeline matching the DML Compiler Prompt role definition:
-%   Phase 1 - Understand & Research
-%             Clarify requirements, research dependencies, understand APIs.
-%   Phase 2 - Environment Setup
-%             Install packages, create/test helper scripts via bash.
-%   Phase 3 - DML Implementation
-%             Write DML, validate syntax, run tests - iterate until passing.
-%   Phase 4 - Deploy
-%             Ask user for permission, then deploy.
-%
-% System tools: validate_dml, test_dml, deploy_skill, write_file, bash
-% Proxied tools: web_search, news_search, url_fetch
-% Auto-augmented: ask_user
-%
-%   agent_main(SpecMarkdown)            - create new skill
-%   agent_main(SpecMarkdown, EditSlug)  - edit existing skill
-% ============================================================================
-
-% -- Tools available to the LLM during task() calls --------------------------
-
-tool(search(Query, Results),
-     "Search the web for information. Returns titles, URLs, and snippets.") :-
-    exec(web_search(query: Query), Results).
-
-tool(search_news(Query, Results),
-     "Search for recent news articles.") :-
-    exec(news_search(query: Query), Results).
-
-tool(fetch(Url, Content),
-     "Fetch a URL and return its body. Use for documentation pages, README files, API references.") :-
-    exec(url_fetch(url: Url), Result),
-    get_dict(body, Result, Content).
-
-tool(list_skills(Skills),
-    "List reusable local skills in the current workspace catalog. Use this before re-implementing a capability that might already exist.") :-
-    exec(list_skills, Skills).
-
-tool(shell(Command, Result),
-     "Run a shell command on the VM. Returns dict with: success (boolean), stdout (string), stderr (string), exitCode (integer), summary (string). Use for package installation, environment checks, and helper script creation/testing. Always check the 'success' field.") :-
-    exec(bash(command: Command), Result).
-
-tool(write(Path, Content, Result),
-     "Write (or overwrite) a file in the workspace. Content is passed as a JSON string so there are NO shell escaping issues - ALWAYS use this instead of bash heredocs for writing DML and other code files. Returns dict with: success (boolean), path (string), bytes (number).") :-
-    exec(write_file(path: Path, content: Content), Result).
-
-tool(validate(DmlFile, Result),
-     "Validate DML code from a .dml file using the Prolog parser. You MUST write the DML to a file first with write(), then pass the file path. Returns dict with: valid (boolean), errors (list), warnings (list).") :-
-    exec(validate_dml(dml_file: DmlFile), Result).
-
-tool(test_run(DmlFile, Input, Result),
-     "Run a DML program from a .dml file with test input(s) to verify it works. You MUST write the DML to a file first with write(), then pass the file path. Input can be a single string (for agent_main/1) or a JSON array string like '[\"arg1\", \"arg2\"]' for multi-arg agent_main. Returns dict with: success (boolean), status (string: ok/error/completed_no_answer/failed_silently), answer (string), outputs (list), errors (list), trace (list).") :-
-    exec(test_dml(dml_file: DmlFile, test_args: Input), Result).
-
-tool(deploy(DmlFile, Spec, MetaJSON, Result),
-    "Publish a new skill to the local runtime catalog. IMPORTANT ARG ORDER: deploy(<dml file path>, <original spec markdown>, <metadata json>). The SECOND argument is the original specification text. The THIRD argument is the metadata JSON string with keys: slug, name, description, trigger_phrases (array of 3-5 phrases). Never pass a version number or boolean flag here. Returns dict with: ok (boolean), slug (string), version (number), or error (string).") :-
-    exec(deploy_skill(dml_file: DmlFile, spec_markdown: Spec, metadata_json: MetaJSON), Result).
-
-tool(deploy_update(DmlFile, Spec, MetaJSON, Slug, Result),
-    "Update an existing skill. IMPORTANT ARG ORDER: deploy_update(<dml file path>, <updated spec markdown>, <metadata json>, <existing slug>). The THIRD argument is metadata JSON; the FOURTH argument is the slug override. Never pass a version number or boolean flag. Returns dict with: ok (boolean), slug (string), version (number), or error (string).") :-
-    exec(deploy_skill(dml_file: DmlFile, spec_markdown: Spec, metadata_json: MetaJSON, slug_override: Slug), Result).
-
-tool(ask_user(Prompt, Response), "Ask the user a clarifying question or for confirmation and get their response.") :-
-    exec(ask_user(prompt: Prompt), Result),
-    get_dict(user_response, Result, Response).
-
-
-% -- Create new skill --------------------------------------------------------
-
-agent_main(SpecMarkdown) :-
-    param(system_prompt, "System prompt with DML reference", SysPrompt),
-    system(SysPrompt),
-    output("📋 Starting skill creation..."),
-
-    % -- Phase 1: Understand & Research --------------------------------------
-    output("Phase 1/4: Understanding requirements and researching dependencies..."),
-    format(string(ResearchTask),
-        "You are starting to build a DML skill from the specification below.\n\nYour job in this phase:\n1. Read the specification carefully. If anything is ambiguous or missing, use ask_user to clarify before proceeding.\n2. Call list_skills if an existing local skill might already cover part of the requested functionality.\n3. Identify all external dependencies (Python packages, Node modules, system tools, APIs, CLI tools).\n4. For each dependency, use search or fetch to look up installation instructions, API docs, or usage examples if you are not already familiar with them.\n5. Summarise: what the skill does, whether any existing skills should be reused, its inputs/outputs, all dependencies found, and any tricky parts.\n\nSpecification:\n---\n~w\n---\n\nStore your findings in ResearchSummary.",
-        [SpecMarkdown]),
-    task(ResearchTask, string(ResearchSummary)),
-    output(ResearchSummary),
-
-    % -- Phase 2: Environment Setup -------------------------------------------
-    output("Phase 2/4: Setting up the environment..."),
-    format(string(EnvTask),
-        "Set up the execution environment for the skill you are about to build.\n\nBased on your research:\n~w\n\nYour job in this phase:\n1. Use shell() to check what is already installed (python --version, node --version, which <tool>, pip show <pkg>, etc.).\n2. Install ALL missing packages and tools: pip install, apt-get install (always use sudo and -y), npm install -g.\n3. If the skill needs helper scripts (Python, Shell, etc.), create and smoke-test them now with shell().\n4. When you encounter errors during setup, diagnose the root cause (version mismatch, missing system lib, permissions, ...) and resolve it.\n5. Prefer the simplest approach with the fewest new dependencies when the spec does not specify.\n6. Do NOT install anything inside the DML skill itself - the skill must assume everything is pre-installed.\n\nStore a short environment summary (what was installed, what exists) in EnvSummary.",
-        [ResearchSummary]),
-
-    task(EnvTask, string(EnvSummary)),
-    output(EnvSummary),
-
-    % -- Phase 3: Implement, Validate, Test ----------------------------------
-    output("Phase 3/4: Writing DML, validating, and testing..."),
-    format(string(ImplTask),
-        "Write, validate, and test the DML skill.\n\nBackground:\n- Research: ~w\n- Environment: ~w\n- Original specification: ~w\n\nYour job in this phase:\n1. Write a complete DML implementation plan (tool definitions, agent_main structure, fallback clause).\n2. If you reuse an existing local skill, prefer a narrow wrapper tool predicate that internally calls exec(run_skill(...)) for that specific child skill. Do NOT expose a generic tool(run_skill(...)) predicate unless the user explicitly asked for an orchestration skill.\n3. Write the full DML code to a .dml file using write(). NEVER use bash heredocs for DML - they mangle backslashes and special Prolog characters. NEVER pass DML as an inline string to validate or test_run.\n4. Call validate('my-skill.dml') - if there are syntax errors, fix the code using write() and re-validate until valid.\n5. Call test_run('my-skill.dml', ...) with a realistic test input - if it fails, analyse the error/trace, fix the code with write(), and re-test until passing.\n6. Keep iterating on validate -> test until the skill works correctly.\n\nStore the final .dml file path in FinalDML.",
-        [ResearchSummary, EnvSummary, SpecMarkdown]),
-    task(ImplTask, string(FinalDML)),
-    output("✅ DML implementation ready."),
-
-    % -- Phase 4: Deploy ------------------------------------------------------
-    (   param(auto_deploy, "Automatic publish mode", true)
-    ->  output("Phase 4/4: Publishing skill..."),
-        param(deployment_metadata_json, "Exact metadata JSON for automatic publishing", DeploymentMetaJSON),
-        format(string(DeployTask),
-            "You are ready to publish the skill automatically. Here is the final DML file path:\n\n~w\n\nOriginal specification:\n~w\n\nUse EXACTLY this metadata JSON string and do not modify it:\n\n~w\n\nYour job:\n1. Do NOT call ask_user. Automatic publish mode already serves as deployment approval.\n2. Call deploy() exactly once with the DML file path, the original specification, and the exact metadata JSON string shown above.\n3. Do not add, remove, or rename metadata keys.\n4. After a successful publish, end your response with a structured summary in EXACTLY this format:\n\nDEPLOY_RESULT:\n- name: <skill name>\n- slug: <skill slug>\n- trigger_phrases: <comma-separated list>\n- test_status: passed\n- deploy_status: success",
-            [FinalDML, SpecMarkdown, DeploymentMetaJSON]),
-        system("Automatic publish mode is enabled. Do not ask the user for permission. Use deployment_metadata_json exactly as provided."),
-        system("When you publish, use EXACTLY this argument order: deploy(FinalDMLPath, OriginalSpecMarkdown, MetadataJSONString). MetadataJSONString must be deployment_metadata_json without edits."),
-        task(DeployTask, string(DeployResult))
-    ;   output("Phase 4/4: Requesting deployment permission..."),
-        format(string(DeployTask),
-            "You are ready to deploy the skill. Here is the final DML file path:\n\n~w\n\nOriginal specification:\n~w\n\nYour job:\n1. Use ask_user to present a short summary of the skill (name, slug, what it does, trigger phrases you intend to use) and ask the user for permission to deploy.\n2. If the user approves (yes / ok / go ahead / etc.), call deploy() with the DML file path, the original specification, and a metadata JSON string containing: slug, name, description, trigger_phrases (3-5 phrases).\n3. If the user declines, answer with a message that the skill is ready but was not deployed, and that they can ask to deploy it later.\n4. After a successful deploy, end your response with a structured summary in EXACTLY this format:\n\nDEPLOY_RESULT:\n- name: <skill name>\n- slug: <skill slug>\n- trigger_phrases: <comma-separated list>\n- test_status: passed\n- deploy_status: success",
-            [FinalDML, SpecMarkdown]),
-        system("When you deploy, use EXACTLY this argument order: deploy(FinalDMLPath, OriginalSpecMarkdown, MetadataJSONString). Do not pass a version number, edit flag, or boolean in place of MetadataJSONString."),
-        task(DeployTask, string(DeployResult))
-    ),
-
-    format(string(Summary), "✅ Skill creation complete!\n\n~w\n\nYou can trigger this skill using one of the trigger phrases shown above.", [DeployResult]),
-    answer(Summary).
-
-% -- Fallback for create -----------------------------------------------------
-
-agent_main(SpecMarkdown) :-
-    format(string(Msg), "❌ Skill creation failed.\n\nThe skill could not be compiled, tested, or deployed from the specification provided. This can happen when:\n- The specification is ambiguous or incomplete\n- Required APIs or tools are not available\n- The DML code could not pass validation or testing after multiple attempts\n\nPlease try:\n1. Simplifying the specification\n2. Being more explicit about inputs, outputs, and logic\n3. Breaking into smaller, focused skills\n\nOriginal spec (first 200 chars): ~w", [SpecMarkdown]),
-    answer(Msg).
-
-% -- Edit existing skill -----------------------------------------------------
-
-agent_main(SpecMarkdown, EditSlug) :-
-    param(system_prompt, "System prompt with DML reference", SysPrompt),
-    system(SysPrompt),
-    format(string(Ctx), "You are editing the existing skill '~w'.", [EditSlug]),
-    system(Ctx),
-    output("📋 Starting skill update..."),
-
-    % -- Phase 1: Understand changes ------------------------------------------
-    output("Phase 1/4: Understanding required changes and dependencies..."),
-    format(string(ResearchTask),
-        "You are updating the existing DML skill '~w' from the specification below.\n\nYour job in this phase:\n1. Read the updated specification. If anything is ambiguous, use ask_user to clarify.\n2. Identify what is changing and any new dependencies introduced by the changes.\n3. Research new dependencies if needed (search, fetch).\n4. Summarise: what is changing, new dependencies if any, and any tricky parts.\n\nUpdated specification:\n---\n~w\n---\n\nStore your findings in ResearchSummary.",
-        [EditSlug, SpecMarkdown]),
-    task(ResearchTask, string(ResearchSummary)),
-    output(ResearchSummary),
-
-    % -- Phase 2: Environment Setup -------------------------------------------
-    output("Phase 2/4: Updating the environment if needed..."),
-    format(string(EnvTask),
-        "Review and update the execution environment for the skill changes.\n\nBased on your analysis:\n~w\n\nYour job:\n1. Check whether any new packages or tools need to be installed for the changes.\n2. Install anything missing via shell().\n3. Create or update any helper scripts if needed.\n4. If no environment changes are needed, confirm that with a brief note.\n\nStore an environment summary in EnvSummary.",
-        [ResearchSummary]),
-    task(EnvTask, string(EnvSummary)),
-    output(EnvSummary),
-
-    % -- Phase 3: Implement, Validate, Test ----------------------------------
-    output("Phase 3/4: Writing updated DML, validating, and testing..."),
-    format(string(ImplTask),
-        "Write, validate, and test the updated DML skill.\n\nBackground:\n- Changes summary: ~w\n- Environment: ~w\n- Updated specification: ~w\n\nYour job:\n1. Write the complete updated DML code to a .dml file using write(). NEVER use bash heredocs for DML - they mangle backslashes and special Prolog characters.\n2. Call validate('my-skill.dml') - fix any syntax errors by rewriting the file with write().\n3. Call test_run('my-skill.dml', ...) - fix any runtime failures by rewriting with write().\n4. Iterate until both validation and testing pass.\n\nStore the final .dml file path in FinalDML.",
-        [ResearchSummary, EnvSummary, SpecMarkdown]),
-    task(ImplTask, string(FinalDML)),
-    output("✅ Updated DML implementation ready."),
-
-    % -- Phase 4: Deploy -------------------------------------------------------
-    (   param(auto_deploy, "Automatic publish mode", true)
-    ->  output("Phase 4/4: Publishing update..."),
-        param(deployment_metadata_json, "Exact metadata JSON for automatic publishing", DeploymentMetaJSON),
-        format(string(DeployTask),
-            "You are ready to publish the updated skill '~w' automatically. Here is the final DML file path:\n\n~w\n\nUpdated specification:\n~w\n\nUse EXACTLY this metadata JSON string and do not modify it:\n\n~w\n\nYour job:\n1. Do NOT call ask_user. Automatic publish mode already serves as deployment approval.\n2. Call deploy_update() exactly once with the DML file path, updated specification, the exact metadata JSON shown above, and slug override '~w'.\n3. Do not add, remove, or rename metadata keys.\n4. After a successful publish, end your response with a structured summary in EXACTLY this format:\n\nDEPLOY_RESULT:\n- name: <skill name>\n- slug: ~w\n- changes: <brief summary of what changed>\n- test_status: passed\n- deploy_status: success",
-            [EditSlug, FinalDML, SpecMarkdown, DeploymentMetaJSON, EditSlug, EditSlug]),
-        system("Automatic publish mode is enabled. Do not ask the user for permission. Use deployment_metadata_json exactly as provided."),
-        system("When you publish an update, use EXACTLY this argument order: deploy_update(FinalDMLPath, UpdatedSpecMarkdown, MetadataJSONString, ExistingSlug). MetadataJSONString must be deployment_metadata_json without edits."),
-        task(DeployTask, string(DeployResult))
-    ;   output("Phase 4/4: Requesting deployment permission..."),
-        format(string(DeployTask),
-            "You are ready to deploy the updated skill '~w'. Here is the final DML file path:\n\n~w\n\nUpdated specification:\n~w\n\nYour job:\n1. Use ask_user to summarise what changed and ask the user for permission to deploy.\n2. If approved, call deploy_update() with the DML file path, spec, a metadata JSON (name, description, trigger_phrases), and slug override '~w'.\n3. If declined, answer that the update is ready but not deployed, and they can ask to deploy later.\n4. After a successful deploy, end your response with a structured summary in EXACTLY this format:\n\nDEPLOY_RESULT:\n- name: <skill name>\n- slug: ~w\n- changes: <brief summary of what changed>\n- test_status: passed\n- deploy_status: success",
-            [EditSlug, FinalDML, SpecMarkdown, EditSlug, EditSlug]),
-        system("When you deploy an update, use EXACTLY this argument order: deploy_update(FinalDMLPath, UpdatedSpecMarkdown, MetadataJSONString, ExistingSlug). Do not pass a version number or boolean flag."),
-        task(DeployTask, string(DeployResult))
-    ),
-
-    format(string(Summary), "✅ Skill '~w' updated and deployed!\n\n~w", [EditSlug, DeployResult]),
-    answer(Summary).
-
-% -- Fallback for edit --------------------------------------------------------
-
-agent_main(SpecMarkdown, EditSlug) :-
-    format(string(Msg), "❌ Skill update failed for '~w'.\n\nThe skill could not be updated from the specification provided. Please try:\n1. Simplifying the changes\n2. Providing the full updated specification\n3. Checking if the skill slug '~w' exists\n\nSpec (first 200 chars): ~w", [EditSlug, EditSlug, SpecMarkdown]),
-    answer(Msg).

package/dist/system/runtime/catalog-recipes.d.ts

@@ -1,24 +0,0 @@
-type RecipePriority = 'low' | 'normal' | 'high';
-export interface RecipeCatalogEntry {
-    slug: string;
-    name: string;
-    description: string;
-    tags: string[];
-    whenToUse: string[];
-    whenNotToUse: string[];
-    globs: string[];
-    priority: RecipePriority;
-    content: string;
-    sourcePath: string;
-    source: 'packaged' | 'workspace';
-}
-export interface RecipeCatalogMatch extends RecipeCatalogEntry {
-    score: number;
-    matchedOn: string[];
-}
-export declare function listRecipeCatalog(workspaceRoot: string): Promise<RecipeCatalogEntry[]>;
-export declare function searchRecipeCatalog(workspaceRoot: string, query: string, options?: {
-    maxResults?: number;
-}): Promise<RecipeCatalogMatch[]>;
-export {};
-//# sourceMappingURL=catalog-recipes.d.ts.map

package/dist/system/runtime/catalog-recipes.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"catalog-recipes.d.ts","sourceRoot":"","sources":["../../../src/system/runtime/catalog-recipes.ts"],"names":[],"mappings":"AAQA,KAAK,cAAc,GAAG,KAAK,GAAG,QAAQ,GAAG,MAAM,CAAC;AAYhD,MAAM,WAAW,kBAAkB;IACjC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,IAAI,EAAE,MAAM,EAAE,CAAC;IACf,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,KAAK,EAAE,MAAM,EAAE,CAAC;IAChB,QAAQ,EAAE,cAAc,CAAC;IACzB,OAAO,EAAE,MAAM,CAAC;IAChB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE,UAAU,GAAG,WAAW,CAAC;CAClC;AAED,MAAM,WAAW,kBAAmB,SAAQ,kBAAkB;IAC5D,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,EAAE,MAAM,EAAE,CAAC;CACrB;AAED,wBAAsB,iBAAiB,CAAC,aAAa,EAAE,MAAM,GAAG,OAAO,CAAC,kBAAkB,EAAE,CAAC,CAa5F;AAED,wBAAsB,mBAAmB,CACvC,aAAa,EAAE,MAAM,EACrB,KAAK,EAAE,MAAM,EACb,OAAO,GAAE;IAAE,UAAU,CAAC,EAAE,MAAM,CAAA;CAAO,GACpC,OAAO,CAAC,kBAAkB,EAAE,CAAC,CAmB/B"}