@foggy-projects/deepseek-harness-plugin 0.4.0-beta.9 → 0.4.0-rc.2

package/skills/foggy-deepseek-onboarding/SKILL.md

@@ -1,137 +1,136 @@
 ---
 name: foggy-deepseek-onboarding
-description: Install and operate a pinned Foggy CLI-first dev/test environment from DeepSeek Harness, including opaque datasource profiles, resumable verification, and schema discovery before semantic authoring. Use for initial Foggy setup or local Runtime onboarding; do not use for production deployment or MCP configuration.
+description: Set up and use Foggy Runtime for data-source exploration and semantic-model development inside DeepSeek Harness. Use for local experience, datasource onboarding, TM/QM authoring, validation, and development publication; route production deployment or updates to a separate release workflow.
 ---
 
 # Foggy DeepSeek onboarding
 
-Set up Foggy through shell and `foggy-runtime` CLI. Do not configure Foggy MCP for this local workflow.
-
-## Native registry and installed-state gate
-
-This Skill is registered by the Foggy plugin through DeepSeek Harness's native Skill registry. Its
-resource base is the authoritative location for these scripts and references; do not search for or
-copy this Skill into the current workspace.
-
-- Resolve the global install state from the platform default component directory: on Linux use
-  `${XDG_DATA_HOME:-$HOME/.local/share}/foggy/deepseek-harness/install-state.json`; on Windows use
-  `%LOCALAPPDATA%\Foggy\DeepSeekHarness\install-state.json`.
-- Confirm the installation with this Skill's `doctor` wrapper and pass the current DSH session
-  workspace as `--project-root`. The absence of `foggy-runtime` from `PATH` is not evidence that the
-  managed CLI is missing; the plugin intentionally installs it in an isolated environment and records
-  its absolute command in the global install state.
-- The plugin downloads and verifies a pinned private Python runtime before running this Skill. Do not
-  search for, install, or repair a system Python. Wrappers resolve the interpreter recorded in the
-  global install state. If private Python is missing, use the plugin's Python repair action. Only use
-  `FOGGY_PYTHON` or `FOGGY_ONBOARDING_PYTHON` when the user explicitly supplied an advanced override.
-- Do not independently download or reinstall the CLI. If the global install state, managed marker, or
-  analysis Skill is missing or invalid, ask the user to open the Foggy plugin settings and use
-  the matching component repair action. Repair restores managed components and invalidates the
-  native DSH Skill catalog. Reinstall or upgrade the plugin itself to restore this bundled Skill.
-- Treat the current DSH session workspace as the authoritative `projectRoot` for the whole onboarding
-  run. Do not redirect semantic drafts or contracts to a different repository merely because another
-  Skill or example was found there. Place non-secret contracts below
-  `<projectRoot>/.foggy/onboarding-contracts/<profile>/`, drafts below
-  `<projectRoot>/.foggy/onboarding-drafts/<profile>/`, and published files below the approved
-  project-relative `modelsDir`.
-
-## Mandatory orchestration boundary
-
-For every new-database onboarding session, this Skill is the orchestration authority until
-`onboard-status` reports `next.status=completed`:
-
-- Invoke datasource, schema, semantic, bundle, and query operations only through this Skill's
-  `scripts/onboard.ps1` or `scripts/onboard.sh`. Do not call `foggy-runtime` directly for those
-  operations, even if another loaded Skill documents equivalent CLI commands.
-- Use `foggy-ai-analysis` only to author TM/QM draft content. Its general direct-CLI workflow does not
-  supersede this Skill's state machine, approval gates, names, paths, query limit, or evidence rules.
-- Use the exact profile, datasource, namespace, bundle, model names, paths, fields, and query limit
-  supplied or confirmed by the user. Do not replace them with examples or inferred alternatives.
-- Do not use raw SQL to sample business rows during onboarding. `schema-discover` is the metadata gate;
-  any later SQL probe requires separate explicit approval and must be bounded and read-only.
-- Never use `--replace`, `--replace-bundle`, `--prune`, `--watch`, or `--execute` unless that exact
-  mutation was explicitly approved. Approval for adding a new resource is not approval to replace one.
-- Save each wrapper result as the single JSON object returned on stdout when the user requests evidence.
-  Do not claim completion when required evidence is missing or the persisted status is incomplete.
-- Never read query-execution evidence back into the conversation. Report only validation state,
-  execution state, row count, and evidence path; do not report row values or generated SQL containing
-  business literals.
-- Prefer one composite command per approval boundary. Do not inspect this Skill's Python implementation
-  or the CLI package source during a normal run; use the documented command contract and inspect code
-  only after a structured wrapper error requires troubleshooting.
-
-## Boundaries
-
-- Treat the bundled Launcher as local dev/test only. Its expected security mode is
-  `none-dev-test-only`; never expose it to a network.
-- Do not print, persist, or request secrets in chat. Use named environment variables or a private env
-  file outside the Skill and evidence directories.
-- Do not modify Foggy engine or CLI source. If setup cannot continue without such a change, stop and
-  ask the user for explicit authorization.
-- Before downloads, installs, replacement, Runtime start/stop, or removal, state the concrete action
-  and obtain any authorization required by the host.
-
-## Workflow
-
-1. Run `scripts/doctor.ps1 --project-root <current-session-workspace>` on Windows or
-   `bash scripts/doctor.sh --project-root <current-session-workspace>` on Linux.
-2. If private Python, the pinned CLI, Launcher, or global managed analysis Skill is missing, use the
-   Foggy plugin's matching Repair action. First-time Python bootstrap requires the plugin UI unless
-   the user explicitly supplies `FOGGY_ONBOARDING_PYTHON`. Use a matching install script only after
-   private Python exists and the plugin UI is unavailable; use `--dry-run` first when paths or
-   permissions are uncertain.
-3. Run `runtime-start` and require successful `wait-ready` plus `capabilities`. Record engine,
-   Runtime API version, schema version, security mode, URL, namespace, PID, and evidence path. If the
-   recorded Runtime is already running, `runtime-start` verifies and reuses it instead of starting a
-   second process.
-4. Load `foggy-ai-analysis` from the native DSH Skill registry. Do not require a workspace copy.
-5. For a new business database, read [references/onboarding-workflow.md](references/onboarding-workflow.md)
-   and prefer its two composite `onboard-datasource-run` / `onboard-semantic-run` commands. Require the
-   trusted operator to create the private CLI profile outside Harness. Unless the operator explicitly
-   overrides it, use the persistent profile store reported by the wrapper under the Foggy data root
-   (`<dataRoot>/cli-profiles`), never `/tmp`. Accept only the opaque profile
-   ID, exact revision, datasource name/type, and namespace; never request JDBC URL, username,
-   password, or password environment-variable name in Harness.
-   If plugin settings report a legacy temporary profile, use the explicit migration action before
-   onboarding. It moves only validated connection metadata and environment-variable references; it
-   never copies a password value and leaves a recoverable private backup below the Foggy data root.
-6. After schema discovery, use `foggy-ai-analysis` only to author TM/QM files in the standard project-local
-   draft directory. Register, validate, publish, and verify them through this Skill's wrapper using the deterministic commands in
-   [references/onboarding-workflow.md](references/onboarding-workflow.md). Do not publish, prune, replace
-   a bundle, or execute a business-data query without the matching explicit flag and user approval.
-7. Stop only the Runtime PID recorded by this package. Preserve Runtime data unless the user explicitly
-   requests purge.
-
-## Command contract
-
-All package scripts return one JSON object on stdout. Treat `success=false` or a nonzero exit code as a
-failure. Do not infer readiness from a fixed sleep; require CLI `wait-ready` and `capabilities`.
-
-Use this analysis order after setup:
+Use this Skill for the normal DeepSeek Harness experience: connect a development datasource, inspect
+it, create TM/QM files in the current workspace, and iterate until queries pass. Use the managed
+`foggy-runtime` CLI and this Skill's wrappers; do not configure Foggy MCP for this local workflow.
+
+## Product boundary
+
+- Treat the plugin and bundled Launcher as local experience and development tooling.
+- Datasources, namespace bindings, model Bundles, refreshes, and query checks are online Runtime
+  operations. They do not require a Runtime restart.
+- Start Runtime only when it is absent. Reuse a healthy running Runtime. Restart only when the user
+  asks, a Launcher/JAR upgrade requires it, Runtime is unhealthy, or an actual startup setting such as
+  port, JVM options, Runtime authentication, or an opt-in module changes.
+- Do not turn production publication into a continuation of local onboarding. When the user wants to
+  deploy or update a formal environment, recommend a manual release or a dedicated production
+  deployment workflow with separately supplied target access, credentials, version, verification, and
+  rollback information.
+- Do not modify Foggy engine or CLI source. If progress genuinely requires either change, stop and ask
+  for explicit authorization.
+
+## Managed installation
+
+This Skill is registered through DeepSeek Harness's native Skill registry. Its scripts and references
+are authoritative; do not copy the Skill into the current workspace.
+
+- Linux install state: `${XDG_DATA_HOME:-$HOME/.local/share}/foggy/deepseek-harness/install-state.json`.
+- Windows install state: `%LOCALAPPDATA%\Foggy\DeepSeekHarness\install-state.json`.
+- Run this Skill's `doctor` wrapper with the current DSH workspace as `--project-root`. The managed CLI
+  is intentionally isolated, so absence from `PATH` does not mean it is missing.
+- Use plugin settings to initialize or repair private Python, CLI, Launcher, or the managed analysis
+  Skill. Do not independently reinstall them during a normal analysis session.
+- Treat the current DSH workspace as `projectRoot`. Keep model drafts and final model files there rather
+  than redirecting them to an example repository.
+
+## Development workflow
+
+1. Run `doctor`. Start Runtime only if it is not already healthy; require `wait-ready` and
+   `capabilities` after a new start.
+2. Accept datasource connection details from the user's message, a user-supplied local JSON file, an
+   environment variable, or Runtime Console. Direct `password` is supported for local development.
+   The wrapper submits it to the public Runtime API without copying it into onboarding state or
+   evidence. Do not echo it in the response.
+3. Create or select the namespace, add/test the datasource online, and bind it to the namespace. Do
+   not stop or restart Runtime to make a password available. A running Runtime can accept a direct
+   development password through its datasource API.
+4. Inspect tables, columns, keys, and relationships. Small, bounded, read-only SQL samples are allowed
+   when they help infer captions, enums, units, or date semantics. Do not run mutations unless the user
+   explicitly requests them.
+5. Load `foggy-ai-analysis` from the native registry only for TM/QM authoring and query tuning; its
+   generic installation, datasource-secret, and production-deployment guidance does not override this
+   development workflow. Default to a project-local `models/` directory unless the user specifies
+   another directory.
+6. Iterate through model validation, Bundle registration/update, model refresh/describe, query
+   validation, and bounded query execution. Development publication means making the local model
+   directory effective in this local Runtime; it is not a production release.
+   A successful response may still contain Runtime `warnings`. Preserve and report their stable facts
+   (`code`, `path`, `message`, `suggestedNextAction`, `safeToAutoRepair`, `normalizedFragment`,
+   `docsRef`, and `details.allowedProperties`)
+   instead of treating success as proof that every requested option took effect. Free-text advice is
+   optional. When a warning indicates possible semantic drift, use `models describe` to prepare a
+   corrected payload if the user's intent can be preserved; otherwise disclose the limitation.
+   Runtime 0.1.21 defaults unknown ordinary Query DSL properties to `WARN`; `IGNORE` continues without
+   `queryInputWarnings`, while `STRICT` rejects the request with the complete structured violations.
+   Never reinterpret a protected or governance-field failure as an ignorable warning.
+7. When the model works, recommend committing the model directory to the user's own Git repository.
+   Do not initialize a repository, commit, push, or create a remote unless the user requests it.
+
+For a normal end-to-end request, take the documented composite-command path first. Do not inspect
+`onboarding.py`, enumerate CLI help, search installation directories, load the sales-drop example, or
+fetch online syntax documentation before trying that path. Use those troubleshooting or reference
+sources only when a concrete error or unsupported modeling requirement makes them relevant.
+
+Use the user's business terms to narrow schema discovery with `--pattern` or repeated `--table` when
+there are clear candidates. Otherwise keep the bounded default, then inspect only the few tables and
+columns needed for the requested model. Full results belong in the evidence files; retain concise
+summaries and paths in the conversation instead of repeatedly reading complete JSON artifacts.
+
+Read [references/onboarding-workflow.md](references/onboarding-workflow.md) for the wrapper commands and
+credential shapes. Use `foggy-ai-analysis` references for detailed TM/QM modeling and query tuning.
+
+## Credential choices for local development
+
+Choose the simplest source the user provides:
+
+- `password` in a connection file: simplest for an experience session; the source file remains under
+  the user's control and should normally stay outside Git.
+- `passwordEnv`: the wrapper reads the variable from the Agent process and submits the value online;
+  Runtime does not need to inherit it at startup.
+- Opaque profile: optional for users who already have one; never require it for ordinary onboarding.
+- Runtime Console: when a Launcher exposing Runtime Console is installed, the user may enter the
+  connection there using the management token shown by the host/plugin.
+
+Keep only a minimal development safety baseline: do not echo passwords, put them in TM/QM files,
+include them in evidence/diagnostics, or commit them to Git. Do not impose production IAM, audit,
+approval, secret-store, or network-governance requirements on this local flow.
+
+## Command behavior
+
+All scripts emit one JSON object. Treat `success=false` or a nonzero exit code as failure. Prefer the
+two resumable composite commands for a complete requested experience:
 
 ```text
-datasource test -> bind -> diagnostics
-tables list -> inspect -> optional bounded read-only SQL
-models validate -> bundles add/update -> models refresh -> models describe
-query validate -> query execute -> interpretation
+onboard-datasource-run --project-root <workspace> --connection-file <json> \
+  --approve-configure --approve-bind --include-indexes
+
+onboard-semantic-run --project-root <workspace> --semantic-plan <json> \
+  --query-payload <json> --approve-validate --approve-publish --approve-execute
+```
+
+When the user has already asked to connect, build, and test a new local model, those flags implement
+that request and do not require separate question-by-question confirmation. Replacement, pruning, broad
+queries, destructive SQL, Git push, and production deployment still require their own clear scope.
+
+The normal analysis order is:
+
+```text
+datasource add/test -> namespace bind -> table/schema inspection
+TM/QM authoring -> models validate -> bundle add/update -> refresh/describe
+query validate -> bounded query execute -> tune -> optional Git handoff
 ```
 
-In DeepSeek Harness, do not expand the composite onboarding commands back into these individual CLI
-operations. This order documents what the wrapper enforces internally and becomes a direct CLI workflow
-only after onboarding is complete.
-
-Composite commands are checkpointed and idempotent: a retry skips completed datasource, validation,
-publication, and verification phases when the approved contract and draft digest are unchanged. Fix a
-query payload in place and rerun the same semantic composite command; do not remove a successfully
-published bundle merely to recover from a later query-validation failure.
-
-An already-completed profile may be reused from another DSH workspace when the approved connection
-contract is byte-for-byte equivalent. Run the datasource composite in the new workspace first; it adds
-that workspace as a non-destructive binding and reuses datasource/schema checkpoints. Then pass the
-current workspace explicitly as `--project-root` to the semantic composite. A secondary workspace may
-reuse an identical published semantic digest and run its own bounded verification query, but it cannot
-replace the published semantic layer; changes must be published from the original workspace or a new
-profile.
-
-Keep user business data separate from the sales-drop SQLite demo. Prefer a read-only database account,
-opaque CLI profile references, and bounded query limits.
+Stop only the PID recorded by this package and preserve the Runtime work directory unless the user
+explicitly requests removal.
+
+## Result
+
+Report the Runtime URL, namespace, datasource name, model directory, Bundle and QueryModel names,
+validation/query status, and useful evidence paths. Never include the password or business row values
+unless the user specifically asks for those values. Include Runtime warning count/codes and the
+warning evidence path when validation or execution completed with warnings.

package/skills/foggy-deepseek-onboarding/assets/connection.schema.json

@@ -12,6 +12,7 @@
     "type": {"enum": ["sqlite", "mysql", "postgres", "postgresql"]},
     "jdbcUrl": {"type": "string", "minLength": 1},
     "username": {"type": "string"},
+    "password": {"type": "string", "description": "Optional local development password. It is submitted once and is not copied into onboarding state or evidence."},
     "passwordEnv": {"type": "string", "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"},
     "opaqueProfileId": {"type": "string", "pattern": "^fop_[a-f0-9]{32}$"},
     "opaqueRevision": {"type": "string", "pattern": "^sha256:[a-f0-9]{64}$"},
@@ -27,6 +28,7 @@
       "not": {"anyOf": [
         {"required": ["jdbcUrl"]},
         {"required": ["username"]},
+        {"required": ["password"]},
         {"required": ["passwordEnv"]}
       ]}
     },
@@ -38,13 +40,9 @@
       ]}
     }
   ],
-  "allOf": [
-    {
-      "if": {
-        "required": ["jdbcUrl"],
-        "properties": {"type": {"not": {"const": "sqlite"}}}
-      },
-      "then": {"required": ["passwordEnv"]}
+  "allOf": [{
+    "not": {
+      "required": ["password", "passwordEnv"]
     }
-  ]
+  }]
 }

package/skills/foggy-deepseek-onboarding/assets/datasource.example.json

@@ -3,8 +3,9 @@
   "profile": "business",
   "name": "business-db",
   "type": "mysql",
-  "opaqueProfileId": "fop_0123456789abcdef0123456789abcdef",
-  "opaqueRevision": "sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
+  "jdbcUrl": "jdbc:mysql://127.0.0.1:3306/business",
+  "username": "business_dev",
+  "password": "replace-for-local-development",
   "namespace": "business",
   "schemas": ["public"],
   "modelsDir": "models",

package/skills/foggy-deepseek-onboarding/assets/env.example

@@ -1,7 +1,7 @@
-# Copy only the variables you need into a private, gitignored env file.
-# Never put provider keys or database passwords in DSH settings, Skill files, or evidence.
+# Optional development configuration. Direct passwords in a user-supplied connection file are also
+# supported; the onboarding wrapper does not copy them into state or evidence.
 
-FOGGY_RUNTIME_API_URL=http://127.0.0.1:18066
+FOGGY_RUNTIME_API_URL=http://127.0.0.1:18166
 FOGGY_NAMESPACE=default
 
 # Optional when Runtime reports securityMode=auth-code.
@@ -10,5 +10,5 @@ FOGGY_NAMESPACE=default
 # Optional data-plane authorization value.
 # FOGGY_RUNTIME_AUTHORIZATION=
 
-# Example datasource password reference. Use a datasource-specific variable name.
+# Optional alternative to a direct development password.
 # FOGGY_DATASOURCE_PASSWORD=

package/skills/foggy-deepseek-onboarding/assets/onboarding-state.schema.json

@@ -28,13 +28,42 @@
           "queryModel": {"type": "string"},
           "queryPayloadDigest": {"type": "string", "pattern": "^[a-f0-9]{64}$"},
           "rowCount": {"type": ["integer", "null"], "minimum": 0},
+          "warningCount": {"type": "integer", "minimum": 0},
+          "warningCodes": {
+            "type": "array",
+            "items": {"type": "string"},
+            "uniqueItems": true
+          },
+          "warningEvidence": {"type": ["string", "null"]},
           "verifiedAt": {"type": "string", "format": "date-time"}
         },
         "additionalProperties": false
       }
     },
     "runtime": {"type": "object"},
-    "connection": {"$ref": "connection.schema.json"},
+    "connection": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["schemaVersion", "connectionMode", "name", "type", "namespace"],
+      "properties": {
+        "schemaVersion": {"const": "foggy-deepseek-connection/v1"},
+        "connectionMode": {"enum": ["legacy-inline", "opaque-profile"]},
+        "credentialMode": {"enum": ["inline-development", "agent-environment", "opaque-profile", "none"]},
+        "name": {"type": "string"},
+        "type": {"type": "string"},
+        "jdbcUrl": {"type": ["string", "null"]},
+        "username": {"type": ["string", "null"]},
+        "passwordEnv": {"type": ["string", "null"]},
+        "opaqueProfileId": {"type": "string"},
+        "opaqueRevision": {"type": "string"},
+        "namespace": {"type": "string"},
+        "schemas": {"type": "array", "items": {"type": "string"}},
+        "modelsDir": {"type": "string"},
+        "readOnlyRecommended": {"type": "boolean"},
+        "profile": {"type": "string"},
+        "evidenceDir": {"type": "string"}
+      }
+    },
     "semantic": {"type": "object"},
     "steps": {"type": "object"},
     "artifacts": {"type": "object"}

package/skills/foggy-deepseek-onboarding/assets/versions.json

@@ -1,10 +1,10 @@
 {
   "schemaVersion": "foggy-deepseek-onboarding-versions/v1",
-  "packageVersion": "0.4.0-beta.9",
-  "validatedAt": "2026-09-03",
+  "packageVersion": "0.4.0-rc.2",
+  "validatedAt": "2026-09-06",
   "components": {
     "deepseekHarness": {
-      "version": "0.1.1-rc.2",
+      "version": "0.1.2-rc.1",
       "minimumNodeVersion": "22.19.0"
     },
     "python": {
@@ -66,70 +66,95 @@
       }
     },
     "launcher": {
-      "version": "0.1.18",
+      "version": "0.1.21",
       "minimumJavaVersion": "17.0.0",
       "runtimeApiContract": "foggy-runtime-api/v1",
       "assets": [
         {
-          "file": "foggy-runtime-launcher-0.1.18.jar",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/foggy-runtime-launcher-0.1.18.jar",
-          "sha256": "2953d2fab39208b3fffefed033b34ec6f59da851920b533047a1d0909a1de049"
+          "file": "foggy-runtime-launcher-0.1.21.jar",
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/foggy-runtime-launcher-0.1.21.jar",
+          "sha256": "0b5002e40633f4606b0f5d3adbcd734ad4a11d8204decab162bb53b6ab28b3b3"
         },
         {
           "file": "start-foggy-runtime.ps1",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/start-foggy-runtime.ps1",
-          "sha256": "b54f2f144cfdc38afcc3e9167d0700248f476c93adb3e9d95431490430f7b549"
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/start-foggy-runtime.ps1",
+          "sha256": "8609f8c60bad9e56460b132e1bd6c699d4ebf47cf591c3e6bc37bc8563d7de5a"
         },
         {
           "file": "start-foggy-runtime.sh",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/start-foggy-runtime.sh",
-          "sha256": "e801cc340bf0842e29045e5e24798921864114846b0e1aaff30640845c8f37d0"
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/start-foggy-runtime.sh",
+          "sha256": "fa844f422473ba00a31cf801092b0fe4ef93fe8697656a9063e0ec27dacef715"
         },
         {
           "file": "README-foggy-runtime-launcher.md",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/README-foggy-runtime-launcher.md",
-          "sha256": "0202546c5221cbb9343cf7367ceb20bff785fd85c2ba77cd0dac5395f6362674"
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/README-foggy-runtime-launcher.md",
+          "sha256": "6b63cafe798e19c255a043e15e64109f6fb3252aee3fb9c37ab6a66d9adbf3cf"
         },
         {
           "file": "runtime-launcher-manifest.json",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/runtime-launcher-manifest.json",
-          "sha256": "0065de9c516471b936927a0b13ed1b9380c484437352b2e589c5171932427326"
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/runtime-launcher-manifest.json",
+          "sha256": "1591804035bbf589912907195c74746bf97edff3b9e6ebd7d569ecc0e5aebed7"
         },
         {
           "file": "SHA256SUMS",
-          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.18/SHA256SUMS",
-          "sha256": "26f65a7112c115ccd19c6f80336b4335ab7773d54841376aa81504d1c3fcd21f"
+          "url": "https://github.com/foggy-projects/foggy-data-mcp-bridge/releases/download/foggy-runtime-launcher-v0.1.21/SHA256SUMS",
+          "sha256": "6e03f8861176d73be22c4c7c6f6345a68e49aacfb5375cd5cf2c54f1dc4cbe5d"
         }
       ]
     },
     "analysisSkill": {
       "name": "foggy-ai-analysis",
-      "version": "0.1.17",
-      "minimumCliVersion": "0.1.21",
+      "version": "0.1.18",
+      "minimumCliVersion": "0.1.23",
+      "assets": [
+        {
+          "role": "zip",
+          "file": "foggy-ai-analysis-skill-0.1.18.zip",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-ai-analysis-skill-0.1.18.zip",
+          "sha256": "93d7bb8812e91a7f85040fe14ce40a3e0657cb2fed07ddfeb9c6f28aca9e2925"
+        },
+        {
+          "role": "manifest",
+          "file": "foggy-ai-analysis-skill-0.1.18-manifest.json",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-ai-analysis-skill-0.1.18-manifest.json",
+          "sha256": "c6e3ae9d9ab17d8fd05fde9b94bba25577662f7edd862b099429e24244d22739"
+        },
+        {
+          "role": "checksums",
+          "file": "foggy-ai-analysis-skill-0.1.18-SHA256SUMS",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-ai-analysis-skill-0.1.18-SHA256SUMS",
+          "sha256": "10b4c97e30201d63fa1fb9773e9a540827b92b495369403deb12b9ab67c69846"
+        }
+      ]
+    },
+    "semanticQuerySkill": {
+      "name": "foggy-semantic-query",
+      "version": "0.1.18",
+      "minimumCliVersion": "0.1.23",
       "assets": [
         {
           "role": "zip",
-          "file": "foggy-ai-analysis-skill-0.1.17.zip",
-          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.17/foggy-ai-analysis-skill-0.1.17.zip",
-          "sha256": "2c5a10090befc38dd2cf8c3de5121d19c28682ca9c0fe72daf778d315c56c7ff"
+          "file": "foggy-semantic-query-skill-0.1.18.zip",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-semantic-query-skill-0.1.18.zip",
+          "sha256": "828aa8517385ea7c4956906834d3bea918f56de6e1d2df7ff0779dc31f7f7fb2"
         },
         {
           "role": "manifest",
-          "file": "foggy-ai-analysis-skill-0.1.17-manifest.json",
-          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.17/foggy-ai-analysis-skill-0.1.17-manifest.json",
-          "sha256": "094b1401ff384f011ef80446dd639d8afb2585aa01d7a7ba49d39cb2968ae8bf"
+          "file": "foggy-semantic-query-skill-0.1.18-manifest.json",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-semantic-query-skill-0.1.18-manifest.json",
+          "sha256": "0348c0786b72c3ea39a5e091ef494559f2fd48a625bd41796fc1b0f6eba82400"
         },
         {
           "role": "checksums",
-          "file": "foggy-ai-analysis-skill-0.1.17-SHA256SUMS",
-          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.17/foggy-ai-analysis-skill-0.1.17-SHA256SUMS",
-          "sha256": "18804088cd7da7af6bbf70d658cb0d6a5a31e765470ed673dfd274f1789db240"
+          "file": "foggy-semantic-query-skill-0.1.18-SHA256SUMS",
+          "url": "https://github.com/foggy-projects/foggy-ai-analysis/releases/download/v0.1.18/foggy-semantic-query-skill-0.1.18-SHA256SUMS",
+          "sha256": "9fdba41edcb39e07f199b3347191e025a4ade4b535827842f861ffa42f4da9cc"
         }
       ]
     }
   },
   "defaults": {
-    "port": 18066,
+    "port": 18166,
     "namespace": "default",
     "readinessTimeoutSeconds": 180,
     "securityMode": "none-dev-test-only"