@foggy-projects/deepseek-harness-plugin 0.4.0-beta.5 → 0.4.0-beta.7

package/README.md

@@ -8,7 +8,7 @@ only when the user selects **Initialize Foggy**.
 ## Local beta installation
 
 ```powershell
-dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.0-beta.5.tgz
+dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.0-beta.7.tgz
 ```
 
 Restart `dsh web`, open Settings → Plugins → Foggy Data Analysis, and initialize
@@ -23,8 +23,9 @@ dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-p
 For development, `FOGGY_ASSET_CACHE_DIRS` can contain platform-delimited verified
 asset-cache directories. It is not required for a normal install.
 
-Database credentials are deliberately outside the ordinary DSH settings
-document. The database and semantic-layer wizard is the next Bundle milestone.
+Database credentials remain outside the ordinary DSH settings document. The
+bundled onboarding Skill drives datasource discovery, semantic drafting,
+checkpointed publication, and bounded read-only query verification.
 
 ## Native Skill and workspace contract
 
@@ -34,6 +35,15 @@ are available in every DSH workspace without copying or symlinking `.agents`.
 The current session `cwd` remains the workspace boundary for semantic drafts and
 evidence.
 
+Opaque CLI profiles default to the private persistent
+`<dataRoot>/cli-profiles` directory. Composite onboarding commands are
+idempotent: unchanged completed phases are resumed rather than re-adding a
+datasource or re-registering a published bundle. Settings detects legacy
+temporary profiles and offers an explicit, validated migration into the
+persistent store. A completed profile can also be bound non-destructively to an
+additional DSH workspace when its reviewed connection contract and published
+semantic digest are unchanged.
+
 CLI, Launcher, the analysis Skill, install state, and Runtime state live in the
 user-level Foggy component directories. The managed CLI is intentionally isolated
 and does not need to be on `PATH`. **Re-download / Repair** verifies the global
@@ -41,6 +51,19 @@ analysis Skill, backs up modified or outdated managed content, restores it, and
 invalidates DSH's Skill catalog. The onboarding Skill is bundled with the plugin
 and is restored by reinstalling or upgrading the plugin package.
 
+The Foggy settings tab shows the persisted database/semantic onboarding stages,
+offers pinned checks and repair for CLI, Launcher, and the managed analysis
+Skill, and exports a private redacted diagnostics report. Runtime start is
+idempotent: an already-recorded process is verified with `wait-ready` and
+`capabilities` instead of being treated as a failed second start.
+
+This beta remains a local dev/test integration. The bundled Runtime reports
+`securityMode=none-dev-test-only` and must not be exposed to a network or used as
+a production service.
+
+See [`docs/PUBLIC-BETA-READINESS.md`](./docs/PUBLIC-BETA-READINESS.md) for the
+tested public Beta scope, release gates, and stable-release blockers.
+
 ## Linux and WSL2 experience
 
 Ubuntu and WSL2 users can use the checked-in preflighted installer under

package/lib/client.js

@@ -10,7 +10,10 @@ window.__ModuleLoader__.load({
     const passthroughSchema = { parse: (value) => value }
     const TYPERT_REMOTE = {
       package: '@foggy-projects/deepseek-harness-plugin',
-      descriptors: ['status', 'plan', 'initialize', 'repair', 'runtimeStart', 'runtimeStop'].map((method) => ({
+      descriptors: [
+        'status', 'plan', 'initialize', 'repair', 'repairCli', 'repairLauncher', 'repairAnalysisSkill',
+        'migrateProfiles', 'diagnostics', 'runtimeStart', 'runtimeStop',
+      ].map((method) => ({
         id: `@foggy-projects/deepseek-harness-plugin#foggyIntegration/${method}`,
         service: 'foggyIntegration',
         namespace: 'foggyIntegration',
@@ -51,6 +54,12 @@ window.__ModuleLoader__.load({
       unavailable: '不可用',
       initialize: '初始化 Foggy',
       repair: '重新下载 / 修复',
+      repairTitle: '分组件检查与修复',
+      repairCli: '检查 / 修复 CLI',
+      repairLauncher: '检查 / 修复 Launcher',
+      repairAnalysisSkill: '检查 / 修复分析 Skill',
+      diagnostics: '导出诊断报告',
+      diagnosticsSaved: '诊断报告已保存',
       start: '启动 Runtime',
       stop: '停止 Runtime',
       working: '操作进行中…',
@@ -68,6 +77,23 @@ window.__ModuleLoader__.load({
       roots: '本地目录',
       installRoot: '组件目录',
       dataRoot: '数据目录',
+      profileStore: 'CLI Profile',
+      profileMigrationTitle: '旧 Profile 迁移',
+      profileMigrationPending: '检测到旧版临时 Profile。迁移只转移连接元数据和密码环境变量引用，不复制密码值。',
+      profileMigrationConflict: '旧 Profile 存在冲突或格式问题，请先导出诊断报告。',
+      migrateProfiles: '迁移到持久目录',
+      onboardingProgress: '数据库与语义层进度',
+      noOnboarding: '尚无数据库引导记录；请在对话中调用 Foggy onboarding Skill。',
+      projectRoot: '工作区',
+      resumeInChat: '未完成步骤应回到对应工作区，在对话中继续。',
+      stepPlanned: '规划',
+      stepDatasourceConfigured: '数据库连接',
+      stepDatasourceVerified: '连接验证',
+      stepSchemaDiscovered: 'Schema 发现',
+      stepSemanticDrafted: '语义层草拟',
+      stepSemanticValidated: '模型校验',
+      stepSemanticPublished: '发布',
+      stepSemanticVerified: '首次查询',
       runtimeUrl: 'Runtime 地址',
       nextTitle: '后续配置',
       nextCopy: 'Skills 已通过 DeepSeek Harness 原生注册表提供给所有工作区；每个会话直接使用自己的工作目录。Runtime 启动成功后，将继续进入数据库连接与语义层向导。',
@@ -99,6 +125,12 @@ window.__ModuleLoader__.load({
       unavailable: 'Unavailable',
       initialize: 'Initialize Foggy',
       repair: 'Re-download / Repair',
+      repairTitle: 'Component checks and repair',
+      repairCli: 'Check / repair CLI',
+      repairLauncher: 'Check / repair Launcher',
+      repairAnalysisSkill: 'Check / repair analysis Skill',
+      diagnostics: 'Export diagnostics',
+      diagnosticsSaved: 'Diagnostics saved',
       start: 'Start Runtime',
       stop: 'Stop Runtime',
       working: 'Operation in progress…',
@@ -116,6 +148,23 @@ window.__ModuleLoader__.load({
       roots: 'Local directories',
       installRoot: 'Components',
       dataRoot: 'Data',
+      profileStore: 'CLI profiles',
+      profileMigrationTitle: 'Legacy profile migration',
+      profileMigrationPending: 'Legacy temporary profiles were found. Migration transfers connection metadata and password environment-variable references, never password values.',
+      profileMigrationConflict: 'A legacy profile has a conflict or invalid format. Export diagnostics before continuing.',
+      migrateProfiles: 'Move to persistent store',
+      onboardingProgress: 'Database and semantic-layer progress',
+      noOnboarding: 'No database onboarding record yet. Invoke the Foggy onboarding Skill in a conversation.',
+      projectRoot: 'Workspace',
+      resumeInChat: 'Resume incomplete steps from a conversation in the matching workspace.',
+      stepPlanned: 'Plan',
+      stepDatasourceConfigured: 'Database connection',
+      stepDatasourceVerified: 'Connection test',
+      stepSchemaDiscovered: 'Schema discovery',
+      stepSemanticDrafted: 'Semantic draft',
+      stepSemanticValidated: 'Model validation',
+      stepSemanticPublished: 'Publish',
+      stepSemanticVerified: 'First query',
       runtimeUrl: 'Runtime URL',
       nextTitle: 'Next configuration',
       nextCopy: 'Skills are provided to every workspace through the native DeepSeek Harness registry, and each session uses its own working directory. After Runtime starts, the database connection and semantic-layer wizard comes next.',
@@ -131,7 +180,7 @@ window.__ModuleLoader__.load({
       .foggy-actions{display:flex;gap:8px;flex-wrap:wrap}.foggy-button{border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-1);color:var(--dsw-alias-label-primary);font:inherit;border-radius:8px;padding:7px 12px;cursor:pointer}.foggy-button:hover{background:var(--dsw-alias-interactive-bg-hover)}.foggy-button:disabled{opacity:.55;cursor:not-allowed}.foggy-button-primary{border-color:var(--dsw-alias-state-business-primary);background:var(--dsw-alias-state-business-primary);color:white}
       .foggy-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:10px}.foggy-card{border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-3);border-radius:10px;padding:13px 14px}.foggy-card-head{display:flex;justify-content:space-between;gap:8px}.foggy-card strong{font-size:13px}.foggy-badge{font-size:11px;color:var(--dsw-alias-label-secondary)}.foggy-card code{display:block;margin-top:8px;color:var(--dsw-alias-label-tertiary);font-size:11px;overflow-wrap:anywhere}
       .foggy-progress{border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-3);border-radius:10px;padding:13px 14px}.foggy-progress-head{display:flex;align-items:center;justify-content:space-between;gap:12px;font-size:13px}.foggy-progress-head strong{font-weight:600}.foggy-progress-percent{color:var(--dsw-alias-label-secondary);font-variant-numeric:tabular-nums}.foggy-progress-track{height:8px;margin-top:10px;border-radius:999px;background:var(--dsw-alias-bg-layer-1);overflow:hidden}.foggy-progress-fill{height:100%;border-radius:inherit;background:var(--dsw-alias-state-business-primary);transition:width .25s ease}.foggy-progress-meta{display:flex;justify-content:space-between;gap:12px;margin-top:8px;color:var(--dsw-alias-label-tertiary);font-size:11px;line-height:16px}.foggy-progress-file{min-width:0;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
-      .foggy-message{margin:0;font-size:13px;line-height:20px;color:var(--dsw-alias-label-secondary)}.foggy-message[data-error=true]{color:var(--dsw-alias-state-error-primary)}.foggy-paths,.foggy-next{border-top:1px solid var(--dsw-alias-border-l2);padding-top:14px}.foggy-paths h4,.foggy-next h4{margin:0 0 8px;font-size:13px}.foggy-paths dl{display:grid;grid-template-columns:100px minmax(0,1fr);gap:6px 10px;margin:0}.foggy-paths dt{color:var(--dsw-alias-label-tertiary);font-size:12px}.foggy-paths dd{margin:0;min-width:0;overflow-wrap:anywhere;font-family:var(--ds-font-family-code);font-size:11px}.foggy-next p{margin:0;color:var(--dsw-alias-label-secondary);font-size:13px;line-height:20px}
+      .foggy-message{margin:0;font-size:13px;line-height:20px;color:var(--dsw-alias-label-secondary)}.foggy-message[data-error=true]{color:var(--dsw-alias-state-error-primary)}.foggy-paths,.foggy-next,.foggy-section{border-top:1px solid var(--dsw-alias-border-l2);padding-top:14px}.foggy-paths h4,.foggy-next h4,.foggy-section h4{margin:0 0 8px;font-size:13px}.foggy-paths dl{display:grid;grid-template-columns:100px minmax(0,1fr);gap:6px 10px;margin:0}.foggy-paths dt{color:var(--dsw-alias-label-tertiary);font-size:12px}.foggy-paths dd{margin:0;min-width:0;overflow-wrap:anywhere;font-family:var(--ds-font-family-code);font-size:11px}.foggy-next p,.foggy-section p{margin:0;color:var(--dsw-alias-label-secondary);font-size:13px;line-height:20px}.foggy-section-actions{display:flex;gap:8px;flex-wrap:wrap;margin-top:10px}.foggy-onboarding-head{display:flex;justify-content:space-between;gap:12px;align-items:start}.foggy-onboarding-head code{font-size:11px;color:var(--dsw-alias-label-tertiary);overflow-wrap:anywhere}.foggy-step-list{display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:7px;margin-top:10px}.foggy-step{border:1px solid var(--dsw-alias-border-l2);border-radius:8px;padding:8px;font-size:11px;color:var(--dsw-alias-label-tertiary)}.foggy-step[data-state=completed]{border-color:color-mix(in srgb,var(--dsw-alias-state-success-primary) 45%,var(--dsw-alias-border-l2));color:var(--dsw-alias-state-success-primary)}.foggy-step[data-state=failed],.foggy-step[data-state=invalid]{border-color:var(--dsw-alias-state-error-primary);color:var(--dsw-alias-state-error-primary)}.foggy-warning{border:1px solid color-mix(in srgb,var(--dsw-alias-state-warning-primary) 55%,var(--dsw-alias-border-l2));background:color-mix(in srgb,var(--dsw-alias-state-warning-primary) 8%,transparent);border-radius:10px;padding:12px}
       @media (width<=680px){.foggy-grid{grid-template-columns:minmax(0,1fr)}}
     `
 
@@ -213,6 +262,41 @@ window.__ModuleLoader__.load({
       })
     }
 
+    function onboardingPanel(onboarding, t) {
+      const profile = onboarding?.profiles?.[0]
+      if (!profile) return jsxs('div', { className: 'foggy-section', children: [
+        jsx('h4', { children: t('onboardingProgress') }),
+        jsx('p', { children: t('noOnboarding') }),
+      ] })
+      const steps = [
+        ['planned', 'stepPlanned'],
+        ['datasourceConfigured', 'stepDatasourceConfigured'],
+        ['datasourceVerified', 'stepDatasourceVerified'],
+        ['schemaDiscovered', 'stepSchemaDiscovered'],
+        ['semanticDrafted', 'stepSemanticDrafted'],
+        ['semanticValidated', 'stepSemanticValidated'],
+        ['semanticPublished', 'stepSemanticPublished'],
+        ['semanticVerified', 'stepSemanticVerified'],
+      ]
+      const percent = Math.round(((profile.completedSteps || 0) / Math.max(profile.totalSteps || 8, 1)) * 100)
+      return jsxs('div', { className: 'foggy-section', children: [
+        jsxs('div', { className: 'foggy-onboarding-head', children: [
+          jsxs('div', { children: [
+            jsx('h4', { children: `${t('onboardingProgress')} · ${profile.profile}` }),
+            jsx('code', { children: `${t('projectRoot')}: ${profile.projectRoot || '—'}` }),
+          ] }),
+          jsx('span', { className: 'foggy-progress-percent', children: `${percent}%` }),
+        ] }),
+        jsx('div', { className: 'foggy-step-list', children: steps.map(([name, label]) => jsx('div', {
+          className: 'foggy-step',
+          'data-state': profile.steps?.[name]?.status || 'pending',
+          title: profile.steps?.[name]?.status || 'pending',
+          children: t(label),
+        }, name)) }),
+        profile.next?.status !== 'completed' ? jsx('p', { style: { marginTop: '9px' }, children: t('resumeInChat') }) : null,
+      ] })
+    }
+
     function FoggySettingsTab({ api, t }) {
       const [view, setView] = useState({ phase: 'loading', status: null, message: '', error: false })
 
@@ -237,7 +321,12 @@ window.__ModuleLoader__.load({
         setView((current) => ({ ...current, message: t('working'), error: false }))
         try {
           const result = unwrap(await api[method](), method)
-          setView((current) => ({ ...current, message: result.accepted ? t('accepted') : '', error: result.success === false }))
+          const message = result.accepted
+            ? t('accepted')
+            : result.path
+              ? `${t('diagnosticsSaved')}: ${result.path}`
+              : ''
+          setView((current) => ({ ...current, message, error: result.success === false }))
           await refresh()
         } catch (error) {
           setView((current) => ({ ...current, message: `${t('actionFailed')}: ${String(error.message || error)}`, error: true }))
@@ -266,6 +355,7 @@ window.__ModuleLoader__.load({
           jsxs('div', { className: 'foggy-state', children: [jsx('span', { className: 'foggy-dot', 'data-state': status.state }), jsx('span', { children: t(stateLabels[status.state] || 'notInstalled') })] }),
           jsxs('div', { className: 'foggy-actions', children: [
             jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: refresh, children: t('refresh') }),
+            jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: () => run('diagnostics'), children: t('diagnostics') }),
             status.state === 'not-installed' ? jsx('button', { className: 'foggy-button foggy-button-primary', type: 'button', disabled: busy, onClick: () => run('initialize'), children: t('initialize') }) : null,
             status.state !== 'not-installed' ? jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: () => run('repair'), children: t('repair') }) : null,
             status.installed && !status.running && status.components.java.available ? jsx('button', { className: 'foggy-button foggy-button-primary', type: 'button', disabled: busy, onClick: () => run('runtimeStart'), children: t('start') }) : null,
@@ -283,11 +373,29 @@ window.__ModuleLoader__.load({
           componentCard(t('onboardingSkill'), status.components.onboardingSkill, 'runtime', t),
           componentCard(t('skillRegistry'), { installed: status.components.onboardingSkill?.provider === 'foggy-managed-skills', version: 'native' }, 'runtime', t),
         ] }),
+        jsxs('div', { className: 'foggy-section', children: [
+          jsx('h4', { children: t('repairTitle') }),
+          jsx('div', { className: 'foggy-section-actions', children: [
+            jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: () => run('repairCli'), children: t('repairCli') }),
+            jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: () => run('repairLauncher'), children: t('repairLauncher') }),
+            jsx('button', { className: 'foggy-button', type: 'button', disabled: busy, onClick: () => run('repairAnalysisSkill'), children: t('repairAnalysisSkill') }),
+          ] }),
+        ] }),
+        status.profileMigration?.pendingCount || status.profileMigration?.conflictCount ? jsxs('div', { className: 'foggy-warning', children: [
+          jsx('h4', { children: t('profileMigrationTitle') }),
+          jsx('p', { children: status.profileMigration.conflictCount ? t('profileMigrationConflict') : t('profileMigrationPending') }),
+          !status.profileMigration.conflictCount ? jsx('div', { className: 'foggy-section-actions', children: jsx('button', {
+            className: 'foggy-button foggy-button-primary', type: 'button', disabled: busy,
+            onClick: () => run('migrateProfiles'), children: t('migrateProfiles'),
+          }) }) : null,
+        ] }) : null,
+        onboardingPanel(status.onboarding, t),
         jsxs('div', { className: 'foggy-paths', children: [
           jsx('h4', { children: t('roots') }),
           jsxs('dl', { children: [
             jsx('dt', { children: t('installRoot') }), jsx('dd', { children: status.roots.installRoot }),
             jsx('dt', { children: t('dataRoot') }), jsx('dd', { children: status.roots.dataRoot }),
+            jsx('dt', { children: t('profileStore') }), jsx('dd', { children: status.roots.profileStore }),
             status.runtimeUrl ? jsx('dt', { children: t('runtimeUrl') }) : null,
             status.runtimeUrl ? jsx('dd', { children: status.runtimeUrl }) : null,
           ] }),

package/lib/index.js

@@ -1,5 +1,5 @@
 import { execFile } from 'node:child_process'
-import { access, readFile } from 'node:fs/promises'
+import { access, mkdir, readFile, writeFile } from 'node:fs/promises'
 import { constants as fsConstants } from 'node:fs'
 import { dirname, join, delimiter } from 'node:path'
 import { fileURLToPath } from 'node:url'
@@ -20,17 +20,20 @@ function defaultRoots() {
     return {
       installRoot: join(base, 'Foggy', 'DeepSeekHarness'),
       dataRoot: join(base, 'Foggy', 'DeepSeekHarnessData'),
+      profileStore: process.env.FOGGY_RUNTIME_PROFILE_STORE || join(base, 'Foggy', 'DeepSeekHarnessData', 'cli-profiles'),
     }
   }
   const home = process.env.HOME
   if (!home) throw new Error('HOME is not set')
+  const dataRoot = process.env.XDG_STATE_HOME
+    ? join(process.env.XDG_STATE_HOME, 'foggy', 'deepseek-harness')
+    : join(home, '.local', 'state', 'foggy', 'deepseek-harness')
   return {
     installRoot: process.env.XDG_DATA_HOME
       ? join(process.env.XDG_DATA_HOME, 'foggy', 'deepseek-harness')
       : join(home, '.local', 'share', 'foggy', 'deepseek-harness'),
-    dataRoot: process.env.XDG_STATE_HOME
-      ? join(process.env.XDG_STATE_HOME, 'foggy', 'deepseek-harness')
-      : join(home, '.local', 'state', 'foggy', 'deepseek-harness'),
+    dataRoot,
+    profileStore: process.env.FOGGY_RUNTIME_PROFILE_STORE || join(dataRoot, 'cli-profiles'),
   }
 }
 
@@ -154,6 +157,16 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
     let runtime = null
     try { state = await readJson(statePath) } catch {}
     try { runtime = await readJson(runtimeStatePath) } catch {}
+    let onboarding = { success: true, profiles: [], profileCount: 0 }
+    let profileMigration = { success: true, entries: [], pendingCount: 0, conflictCount: 0, profileStore: roots.profileStore }
+    if (state) {
+      try { onboarding = await runOnboarding(['onboard-list']) } catch (error) {
+        onboarding = { success: false, profiles: [], profileCount: 0, error: String(error.message ?? error) }
+      }
+      try { profileMigration = await runOnboarding(['profile-migration-status']) } catch (error) {
+        profileMigration = { success: false, entries: [], pendingCount: 0, conflictCount: 0, profileStore: roots.profileStore, error: String(error.message ?? error) }
+      }
+    }
     const cliPath = state?.cli?.command
     const launcherPath = state?.launcher?.path
     const analysisSkillPath = state?.skills?.analysis?.path || join(roots.installRoot, 'skills', 'foggy-ai-analysis')
@@ -215,6 +228,8 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
       roots,
       components,
       operation,
+      onboarding,
+      profileMigration,
       next: installed ? (running ? 'configure-database' : 'start-runtime') : 'initialize',
     }
   }
@@ -246,6 +261,49 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
     return this.startOperation('repair', true)
   }
 
+  async repairCli() {
+    return this.startOperation('repair-cli', false, ['install', '--repair-component', 'cli'])
+  }
+
+  async repairLauncher() {
+    return this.startOperation('repair-launcher', false, ['install', '--repair-component', 'launcher'])
+  }
+
+  async repairAnalysisSkill() {
+    return this.startOperation('repair-analysis-skill', true, ['install', '--repair-component', 'analysis-skill'])
+  }
+
+  async migrateProfiles() {
+    return this.startOperation('profile-migration', false, ['profile-migrate', '--approve'])
+  }
+
+  async diagnostics() {
+    const roots = defaultRoots()
+    const [status, doctor] = await Promise.all([
+      this.status(),
+      runOnboarding(['doctor', '--no-fail']),
+    ])
+    const report = {
+      schemaVersion: 'foggy-deepseek-diagnostics/v1',
+      generatedAt: new Date().toISOString(),
+      packageVersion: status.packageVersion,
+      state: status.state,
+      installed: status.installed,
+      running: status.running,
+      runtimeUrl: status.runtimeUrl,
+      roots: status.roots,
+      components: status.components,
+      onboarding: status.onboarding,
+      profileMigration: status.profileMigration,
+      doctor,
+    }
+    const directory = join(roots.dataRoot, 'diagnostics')
+    await mkdir(directory, { recursive: true })
+    const path = join(directory, `diagnostics-${Date.now()}.json`)
+    await writeFile(path, `${JSON.stringify(report, null, 2)}\n`, { encoding: 'utf8', mode: 0o600 })
+    return { success: true, path, report }
+  }
+
   async runtimeStart() {
     return this.startOperation('runtime-start', false, ['runtime-start'])
   }
@@ -260,7 +318,8 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
     }
     const id = `${Date.now()}-${Math.random().toString(16).slice(2, 10)}`
     const args = explicitArgs ?? ['install']
-    if (!explicitArgs) {
+    const reportsProgress = args[0] === 'install'
+    if (reportsProgress) {
       const roots = defaultRoots()
       args.push('--progress-file', join(roots.dataRoot, 'operation-progress.json'), '--operation-id', id, '--operation-kind', kind)
     }
@@ -276,7 +335,7 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
       finishedAt: null,
       result: null,
       error: null,
-      progress: !explicitArgs ? {
+      progress: reportsProgress ? {
         schemaVersion: 'foggy-deepseek-onboarding-progress/v1',
         operationId: id,
         kind,
@@ -324,7 +383,10 @@ export class FoggyIntegrationGateway extends TypertRemoteService {
 }
 
 const markerInitializers = []
-for (const method of ['status', 'plan', 'initialize', 'repair', 'runtimeStart', 'runtimeStop']) {
+for (const method of [
+  'status', 'plan', 'initialize', 'repair', 'repairCli', 'repairLauncher', 'repairAnalysisSkill',
+  'migrateProfiles', 'diagnostics', 'runtimeStart', 'runtimeStop',
+]) {
   Remote(method)(FoggyIntegrationGateway.prototype[method], {
     kind: 'method',
     name: method,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@foggy-projects/deepseek-harness-plugin",
-  "version": "0.4.0-beta.5",
+  "version": "0.4.0-beta.7",
   "description": "Foggy Java data analysis engine integration for DeepSeek Harness",
   "type": "module",
   "main": "./lib/index.js",
@@ -55,6 +55,6 @@
   },
   "scripts": {
     "check": "node --check lib/index.js && node --check lib/skill-provider.js && node --check lib/client.js && node --check lib/typert.js && node --check lib/remote.js",
-    "test": "node --test test/package.test.js"
+    "test": "node --test test/package.test.js && python test/onboarding_unit.py"
   }
 }

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

@@ -22,8 +22,14 @@ copy this Skill into the current workspace.
   its absolute command in the global install state.
 - 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
-  **Re-download / Repair**. Repair restores the global managed analysis Skill and invalidates the
+  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
 
@@ -46,6 +52,9 @@ For every new-database onboarding session, this Skill is the orchestration autho
 - 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
 
@@ -66,14 +75,21 @@ For every new-database onboarding session, this Skill is the orchestration autho
    plugin's Repair action. Use the matching install script only when 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.
+   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. Accept only the opaque profile
+   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.
-6. After schema discovery, use `foggy-ai-analysis` only to author TM/QM files in a separate project-local
+   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.
@@ -98,5 +114,18 @@ In DeepSeek Harness, do not expand the composite onboarding commands back into t
 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.

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

@@ -13,6 +13,26 @@
     "installRoot": {"type": "string"},
     "dataRoot": {"type": "string"},
     "projectRoot": {"type": "string"},
+    "workspaceBindings": {
+      "type": "array",
+      "items": {"type": "string"},
+      "uniqueItems": true
+    },
+    "workspaceVerifications": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["projectRoot", "queryModel", "queryPayloadDigest", "verifiedAt"],
+        "properties": {
+          "projectRoot": {"type": "string"},
+          "queryModel": {"type": "string"},
+          "queryPayloadDigest": {"type": "string", "pattern": "^[a-f0-9]{64}$"},
+          "rowCount": {"type": ["integer", "null"], "minimum": 0},
+          "verifiedAt": {"type": "string", "format": "date-time"}
+        },
+        "additionalProperties": false
+      }
+    },
     "runtime": {"type": "object"},
     "connection": {"$ref": "connection.schema.json"},
     "semantic": {"type": "object"},

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

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "foggy-deepseek-onboarding-versions/v1",
-  "packageVersion": "0.4.0-beta.5",
+  "packageVersion": "0.4.0-beta.7",
   "validatedAt": "2026-09-01",
   "components": {
     "deepseekHarness": {

package/skills/foggy-deepseek-onboarding/references/onboarding-workflow.md

@@ -23,6 +23,22 @@ to paste a password and do not put a JDBC URL, username, password environment-va
 line, logs, or evidence. For non-SQLite databases, ask the user to set the named environment variable
 before Runtime starts so the Java process inherits it. Recommend a read-only database account.
 
+Use the current DSH session workspace as `projectRoot`. Store approved non-secret contracts at
+`.foggy/onboarding-contracts/<profile>/`, semantic drafts at `.foggy/onboarding-drafts/<profile>/`, and
+command evidence at `.foggy/onboarding-command-evidence/<profile>/`. Do not split these files across the
+session workspace and a separate example repository. The wrapper rejects a query payload outside the
+recorded project root before any semantic validation or publication mutation occurs.
+
+The wrapper defaults `FOGGY_RUNTIME_PROFILE_STORE` to the private persistent directory
+`<dataRoot>/cli-profiles`. An explicit operator-provided value still wins. Do not use `/tmp` for a profile
+that must survive a WSL or Harness restart.
+
+If plugin settings detect profiles in the legacy temporary store, use **Move to persistent store**.
+Migration validates the opaque profile schema, rejects embedded passwords and conflicts, writes the
+destination with private permissions, verifies it, and moves the legacy JSON to a recoverable private
+backup below the Foggy data root.
+Do not manually copy or edit opaque profile JSON.
+
 Treat every user-supplied identifier and bound as immutable input: profile, datasource, namespace,
 models directory, bundle name, TM/QM name, query fields, and limit. Do not swap in demo names, add
 fields, raise the limit, or introduce replacement flags. If one of these inputs is missing, pause for
@@ -42,17 +58,32 @@ For Harness-driven onboarding, use the two composite commands below. Each writes
 evidence internally and refuses to cross an unapproved mutation gate:
 
 ```text
-onboard-datasource-run --connection-file <approved-json> \
+onboard-datasource-run --project-root <current-session-workspace> \
+  --connection-file <approved-json> \
   --approve-configure --approve-bind --include-indexes
 
 # After authoring the registered TM/QM draft from schema metadata:
-onboard-semantic-run --semantic-plan <approved-json> --query-payload <approved-json> \
+onboard-semantic-run --project-root <current-session-workspace> \
+  --semantic-plan <approved-json> --query-payload <approved-json> \
   --approve-validate --approve-publish --approve-execute
 ```
 
 Include an approval flag only after the user approves that exact action. Without it, the composite
 command stops after the corresponding dry-run and returns `phaseStatus=awaiting-...-approval`.
 
+Both composite commands are resumable. When the approved contract is unchanged, they skip completed
+checkpoints instead of re-adding an existing datasource, revalidating an already published draft, or
+registering the same bundle twice. If query validation fails after publication, correct the project-local
+payload and rerun `onboard-semantic-run`; it resumes at query verification and leaves the active bundle in
+place. A same-name datasource is accepted idempotently only when its public name and database type match
+the approved plan; otherwise replacement still requires explicit approval.
+
+When a completed profile already belongs to another workspace, the datasource composite may add the
+current workspace as a binding only if the approved connection contract is identical and the datasource,
+schema, and semantic publication checkpoints are complete. The semantic composite then accepts the same
+published draft digest from the bound workspace and performs a workspace-specific bounded verification
+query. It refuses semantic replacement from the secondary workspace.
+
 The granular commands below remain available for manual troubleshooting and resumption. Do not expand
 the composite commands into this list during a normal Harness turn.
 
@@ -68,8 +99,8 @@ semantic-validate --profile <profile>
 semantic-validate --profile <profile> --apply
 semantic-publish --profile <profile>
 semantic-publish --profile <profile> --apply
-semantic-verify --profile <profile> --query-payload <json>
-semantic-verify --profile <profile> --query-payload <json> --execute
+semantic-verify --profile <profile> --project-root <current-session-workspace> --query-payload <json>
+semantic-verify --profile <profile> --project-root <current-session-workspace> --query-payload <json> --execute
 onboard-status --profile <profile>
 ```
 
@@ -111,6 +142,11 @@ requires an integer `limit` from 1 through 100. The first `semantic-verify` call
 validates the query; only `--execute` reads business data. Full results stay in evidence and the command
 returns only counts and paths.
 
+Before the first semantic mutation, the composite command checks that the query payload is inside
+`projectRoot`, has a bounded limit, and targets a query model declared in the approved semantic plan.
+After publication, `semantic-verify` always describes the live model before validation. If a field is
+rejected, update the payload from those described names and rerun the same composite command.
+
 Do not open, summarize, or quote `query-execute.json` or the Runtime's generated SQL after execution.
 The conversational result may contain only `queryValidated`, `queryExecuted`, `rowCount`, the model
 name, and the evidence path. A successful direct CLI command is not proof that onboarding completed;