dsh-d365-kit 0.34.1 → 0.34.4

package/lib/write-store.js

@@ -1,167 +1,167 @@
-/**
- * Pending write plans and the change ledger.
- *
- * A plan is inert data. It becomes a change only when a person presses the
- * confirm button in the settings page, which then calls the Host's audited
- * execute route. The agent can create plans and read them; it cannot run one.
- */
-import { mkdir, readdir, readFile, rm, writeFile } from 'node:fs/promises'
-import { join } from 'node:path'
-import { dataRoot } from './snapshot.js'
-
-const PLAN_ID = /^[0-9A-Za-z-]{6,64}$/
-
-export function plansDir(config) {
-  return join(dataRoot(config), 'pending-writes')
-}
-
-export function changesDir(config) {
-  return join(dataRoot(config), 'changes')
-}
-
-function planPath(config, id) {
-  if (!PLAN_ID.test(String(id ?? ''))) return undefined
-  return join(plansDir(config), `${id}.json`)
-}
-
-/** Persist a plan and return it with its id. */
-export async function createPlan(config, plan) {
-  const id = plan.id ?? `${Date.now().toString(36)}-${Math.random().toString(36).slice(2, 8)}`
-  const record = { ...plan, id, createdAt: new Date().toISOString(), status: 'pending' }
-  const dir = plansDir(config)
-  await mkdir(dir, { recursive: true })
-  await writeFile(join(dir, `${id}.json`), `${JSON.stringify(record, null, 2)}\n`, 'utf8')
-  return record
-}
-
-export async function readPlan(config, id) {
-  const path = planPath(config, id)
-  if (!path) return undefined
-  try {
-    return JSON.parse(await readFile(path, 'utf8'))
-  } catch {
-    return undefined
-  }
-}
-
-export async function deletePlan(config, id) {
-  const path = planPath(config, id)
-  if (!path) return false
-  try {
-    await rm(path)
-    return true
-  } catch {
-    return false
-  }
-}
-
-/**
- * Move a plan through its lifecycle: pending → running → done | failed.
- *
- * The file is the only guard against executing a plan twice. Marking it
- * "running" before the first write means a crash mid-plan leaves a record that
- * refuses a silent second run, instead of replaying the operations that already
- * landed.
- */
-export async function setPlanStatus(config, id, status, extra = {}) {
-  const plan = await readPlan(config, id)
-  if (!plan) return undefined
-  const path = planPath(config, id)
-  if (!path) return undefined
-  const next = { ...plan, ...extra, status, updatedAt: new Date().toISOString() }
-  await writeFile(path, `${JSON.stringify(next, null, 2)}\n`, 'utf8')
-  return next
-}
-
-/** Every still-readable plan, newest first. */
-export async function listPlans(config) {
-  const dir = plansDir(config)
-  let names = []
-  try {
-    names = await readdir(dir)
-  } catch {
-    return []
-  }
-  const plans = []
-  for (const name of names.filter((name) => name.endsWith('.json'))) {
-    const plan = await readPlan(config, name.replace(/\.json$/, ''))
-    if (plan) plans.push(plan)
-  }
-  return plans.sort((a, b) => String(b.createdAt).localeCompare(String(a.createdAt)))
-}
-
-/**
- * Append one executed change to the ledger. This file is the only record of
- * "what did the agent change and when", so it is written before the HTTP calls
- * settle and never rewritten.
- */
-export async function recordChange(config, record) {
-  const dir = changesDir(config)
-  await mkdir(dir, { recursive: true })
-  const stamp = new Date().toISOString().replace(/[:.]/g, '-')
-  const name = `${stamp}-${record.planId ?? 'plan'}.json`
-  const path = join(dir, name)
-  await writeFile(path, `${JSON.stringify({ ...record, recordedAt: new Date().toISOString() }, null, 2)}\n`, 'utf8')
-  return path
-}
-
-/** Recent ledger entries, newest first. */
-export async function listChanges(config, limit = 20) {
-  const dir = changesDir(config)
-  let names = []
-  try {
-    names = await readdir(dir)
-  } catch {
-    return []
-  }
-  const files = names.filter((name) => name.endsWith('.json')).sort().reverse().slice(0, limit)
-  const entries = []
-  for (const name of files) {
-    try {
-      entries.push(JSON.parse(await readFile(join(dir, name), 'utf8')))
-    } catch {
-      // A half-written ledger entry is skipped rather than failing the page.
-    }
-  }
-  return entries
-}
-
-/**
- * Record how one publish attempt ended. One file per plan: a re-publish
- * overwrites the previous outcome, which is what "current state" means here.
- */
-export async function writePublishReport(config, planId, record) {
-  const dir = changesDir(config)
-  await mkdir(dir, { recursive: true })
-  const path = join(dir, `publish-${planId}.json`)
-  await writeFile(path, `${JSON.stringify(record, null, 2)}\n`, 'utf8')
-  return path
-}
-
-/**
- * How the publish for each executed plan ended.
- *
- * The publish runs detached, so the ledger can only say "running"; the sidecar
- * written when the request settles is the only place that knows the outcome.
- * Keyed by planId so the plans panel can show it next to the change.
- */
-export async function listPublishReports(config) {
-  const dir = changesDir(config)
-  let names = []
-  try {
-    names = await readdir(dir)
-  } catch {
-    return {}
-  }
-  const reports = {}
-  for (const name of names.filter((name) => name.startsWith('publish-') && name.endsWith('.json'))) {
-    try {
-      const record = JSON.parse(await readFile(join(dir, name), 'utf8'))
-      if (record?.planId) reports[record.planId] = record
-    } catch {
-      // Skip an unreadable sidecar; the UI falls back to the ledger state.
-    }
-  }
-  return reports
-}
-
+/**
+ * Pending write plans and the change ledger.
+ *
+ * A plan is inert data. It becomes a change only when a person presses the
+ * confirm button in the settings page, which then calls the Host's audited
+ * execute route. The agent can create plans and read them; it cannot run one.
+ */
+import { mkdir, readdir, readFile, rm, writeFile } from 'node:fs/promises'
+import { join } from 'node:path'
+import { dataRoot } from './snapshot.js'
+
+const PLAN_ID = /^[0-9A-Za-z-]{6,64}$/
+
+export function plansDir(config) {
+  return join(dataRoot(config), 'pending-writes')
+}
+
+export function changesDir(config) {
+  return join(dataRoot(config), 'changes')
+}
+
+function planPath(config, id) {
+  if (!PLAN_ID.test(String(id ?? ''))) return undefined
+  return join(plansDir(config), `${id}.json`)
+}
+
+/** Persist a plan and return it with its id. */
+export async function createPlan(config, plan) {
+  const id = plan.id ?? `${Date.now().toString(36)}-${Math.random().toString(36).slice(2, 8)}`
+  const record = { ...plan, id, createdAt: new Date().toISOString(), status: 'pending' }
+  const dir = plansDir(config)
+  await mkdir(dir, { recursive: true })
+  await writeFile(join(dir, `${id}.json`), `${JSON.stringify(record, null, 2)}\n`, 'utf8')
+  return record
+}
+
+export async function readPlan(config, id) {
+  const path = planPath(config, id)
+  if (!path) return undefined
+  try {
+    return JSON.parse(await readFile(path, 'utf8'))
+  } catch {
+    return undefined
+  }
+}
+
+export async function deletePlan(config, id) {
+  const path = planPath(config, id)
+  if (!path) return false
+  try {
+    await rm(path)
+    return true
+  } catch {
+    return false
+  }
+}
+
+/**
+ * Move a plan through its lifecycle: pending → running → done | failed.
+ *
+ * The file is the only guard against executing a plan twice. Marking it
+ * "running" before the first write means a crash mid-plan leaves a record that
+ * refuses a silent second run, instead of replaying the operations that already
+ * landed.
+ */
+export async function setPlanStatus(config, id, status, extra = {}) {
+  const plan = await readPlan(config, id)
+  if (!plan) return undefined
+  const path = planPath(config, id)
+  if (!path) return undefined
+  const next = { ...plan, ...extra, status, updatedAt: new Date().toISOString() }
+  await writeFile(path, `${JSON.stringify(next, null, 2)}\n`, 'utf8')
+  return next
+}
+
+/** Every still-readable plan, newest first. */
+export async function listPlans(config) {
+  const dir = plansDir(config)
+  let names = []
+  try {
+    names = await readdir(dir)
+  } catch {
+    return []
+  }
+  const plans = []
+  for (const name of names.filter((name) => name.endsWith('.json'))) {
+    const plan = await readPlan(config, name.replace(/\.json$/, ''))
+    if (plan) plans.push(plan)
+  }
+  return plans.sort((a, b) => String(b.createdAt).localeCompare(String(a.createdAt)))
+}
+
+/**
+ * Append one executed change to the ledger. This file is the only record of
+ * "what did the agent change and when", so it is written before the HTTP calls
+ * settle and never rewritten.
+ */
+export async function recordChange(config, record) {
+  const dir = changesDir(config)
+  await mkdir(dir, { recursive: true })
+  const stamp = new Date().toISOString().replace(/[:.]/g, '-')
+  const name = `${stamp}-${record.planId ?? 'plan'}.json`
+  const path = join(dir, name)
+  await writeFile(path, `${JSON.stringify({ ...record, recordedAt: new Date().toISOString() }, null, 2)}\n`, 'utf8')
+  return path
+}
+
+/** Recent ledger entries, newest first. */
+export async function listChanges(config, limit = 20) {
+  const dir = changesDir(config)
+  let names = []
+  try {
+    names = await readdir(dir)
+  } catch {
+    return []
+  }
+  const files = names.filter((name) => name.endsWith('.json')).sort().reverse().slice(0, limit)
+  const entries = []
+  for (const name of files) {
+    try {
+      entries.push(JSON.parse(await readFile(join(dir, name), 'utf8')))
+    } catch {
+      // A half-written ledger entry is skipped rather than failing the page.
+    }
+  }
+  return entries
+}
+
+/**
+ * Record how one publish attempt ended. One file per plan: a re-publish
+ * overwrites the previous outcome, which is what "current state" means here.
+ */
+export async function writePublishReport(config, planId, record) {
+  const dir = changesDir(config)
+  await mkdir(dir, { recursive: true })
+  const path = join(dir, `publish-${planId}.json`)
+  await writeFile(path, `${JSON.stringify(record, null, 2)}\n`, 'utf8')
+  return path
+}
+
+/**
+ * How the publish for each executed plan ended.
+ *
+ * The publish runs detached, so the ledger can only say "running"; the sidecar
+ * written when the request settles is the only place that knows the outcome.
+ * Keyed by planId so the plans panel can show it next to the change.
+ */
+export async function listPublishReports(config) {
+  const dir = changesDir(config)
+  let names = []
+  try {
+    names = await readdir(dir)
+  } catch {
+    return {}
+  }
+  const reports = {}
+  for (const name of names.filter((name) => name.startsWith('publish-') && name.endsWith('.json'))) {
+    try {
+      const record = JSON.parse(await readFile(join(dir, name), 'utf8'))
+      if (record?.planId) reports[record.planId] = record
+    } catch {
+      // Skip an unreadable sidecar; the UI falls back to the ledger state.
+    }
+  }
+  return reports
+}
+

package/locale/en.json

@@ -1,68 +1,68 @@
-{
-  "meta": {
-    "title": "D365 Toolkit",
-    "description": "Developer and deployment toolkit for Dynamics 365 CE: metadata, layers, migration risk, code checks, contract drift and environment health."
-  },
-  "tools": {
-    "d365_envs": {
-      "title": "Environments",
-      "description": "List configured environments, credential status and connectivity"
-    },
-    "d365_metadata": {
-      "title": "Metadata",
-      "description": "Query entities, attributes, forms, views, plugins and solutions by resource"
-    },
-    "d365_layers": {
-      "title": "Solution layers",
-      "description": "See which solutions cover a component and which layer is active"
-    },
-    "d365_sync": {
-      "title": "Sync snapshot",
-      "description": "Pull environment metadata into a local snapshot and record completeness"
-    },
-    "d365_diff": {
-      "title": "Diff snapshots",
-      "description": "Compare two snapshots: additions, deletions and field-level edits"
-    },
-    "d365_configure": {
-      "title": "Configure environments",
-      "description": "List, save, remove or test environment definitions"
-    },
-    "d365_write": {
-      "title": "Metadata changes",
-      "description": "Plan option values, attributes, table names and view columns, then apply after approval"
-    },
-    "d365_migrate": {
-      "title": "Migration risk",
-      "description": "Assess importing a solution elsewhere: shadowing, missing components, lost option values"
-    },
-    "d365_code_check": {
-      "title": "Code change check",
-      "description": "Read a GitLab MR and check whether script and plugin changes will run in the target environment"
-    },
-    "d365_refs": {
-      "title": "References",
-      "description": "Which forms, views and flows use a field, which forms load a script, which steps a plugin has"
-    },
-    "d365_data": {
-      "title": "Query data",
-      "description": "Count, group or sample business records (requires environment permission)"
-    },
-    "d365_data_write": {
-      "title": "Write data",
-      "description": "Create or update one business record after approval (requires environment permission)"
-    },
-    "d365_contract": {
-      "title": "Contract drift",
-      "description": "Check plugin registrations, form scripts and sitemaps across environments, with waivers"
-    },
-    "d365_health": {
-      "title": "Environment health",
-      "description": "Suspended and failed jobs, running imports and publishes, recently installed solutions"
-    },
-    "d365_reports": {
-      "title": "Local data",
-      "description": "Inspect local artifact usage, clean up by retention policy or compact snapshots"
-    }
-  }
-}
+{
+  "meta": {
+    "title": "D365 Toolkit",
+    "description": "Developer and deployment toolkit for Dynamics 365 CE: metadata, layers, migration risk, code checks, contract drift and environment health."
+  },
+  "tools": {
+    "d365_envs": {
+      "title": "Environments",
+      "description": "List configured environments, credential status and connectivity"
+    },
+    "d365_metadata": {
+      "title": "Metadata",
+      "description": "Query entities, attributes, forms, views, plugins and solutions by resource"
+    },
+    "d365_layers": {
+      "title": "Solution layers",
+      "description": "See which solutions cover a component and which layer is active"
+    },
+    "d365_sync": {
+      "title": "Sync snapshot",
+      "description": "Pull environment metadata into a local snapshot and record completeness"
+    },
+    "d365_diff": {
+      "title": "Diff snapshots",
+      "description": "Compare two snapshots: additions, deletions and field-level edits"
+    },
+    "d365_configure": {
+      "title": "Configure environments",
+      "description": "List, save, remove or test environment definitions"
+    },
+    "d365_write": {
+      "title": "Metadata changes",
+      "description": "Plan option values, attributes, table names and view columns, then apply after approval"
+    },
+    "d365_migrate": {
+      "title": "Migration risk",
+      "description": "Assess importing a solution elsewhere: shadowing, missing components, lost option values"
+    },
+    "d365_code_check": {
+      "title": "Code change check",
+      "description": "Read a GitLab MR and check whether script and plugin changes will run in the target environment"
+    },
+    "d365_refs": {
+      "title": "References",
+      "description": "Which forms, views and flows use a field, which forms load a script, which steps a plugin has"
+    },
+    "d365_data": {
+      "title": "Query data",
+      "description": "Count, group or sample business records (requires environment permission)"
+    },
+    "d365_data_write": {
+      "title": "Write data",
+      "description": "Create or update one business record after approval (requires environment permission)"
+    },
+    "d365_contract": {
+      "title": "Contract drift",
+      "description": "Check plugin registrations, form scripts and sitemaps across environments, with waivers"
+    },
+    "d365_health": {
+      "title": "Environment health",
+      "description": "Suspended and failed jobs, running imports and publishes, recently installed solutions"
+    },
+    "d365_reports": {
+      "title": "Local data",
+      "description": "Inspect local artifact usage, clean up by retention policy or compact snapshots"
+    }
+  }
+}

package/locale/zh.json

@@ -1,68 +1,68 @@
-{
-  "meta": {
-    "title": "D365 工具箱",
-    "description": "Dynamics 365 CE 的开发与部署助手：元数据、解决方案层、迁移风险、代码改动检查、契约漂移、环境健康。"
-  },
-  "tools": {
-    "d365_envs": {
-      "title": "环境清单",
-      "description": "列出已配置环境、凭据状态与连通性"
-    },
-    "d365_metadata": {
-      "title": "元数据查询",
-      "description": "按类别查询实体、字段、表单、视图、插件、解决方案等"
-    },
-    "d365_layers": {
-      "title": "解决方案层",
-      "description": "查看组件被哪些解决方案覆盖、当前生效的是哪一层"
-    },
-    "d365_sync": {
-      "title": "同步快照",
-      "description": "把环境元数据拉成本地快照并记录采集完整度"
-    },
-    "d365_diff": {
-      "title": "快照对比",
-      "description": "比较两份快照的新增、删除与字段级修改"
-    },
-    "d365_configure": {
-      "title": "环境配置",
-      "description": "读写环境清单：列出、保存、删除或测试连接"
-    },
-    "d365_write": {
-      "title": "元数据变更",
-      "description": "准备选项值、字段、表名与视图列的修改计划，确认后执行"
-    },
-    "d365_migrate": {
-      "title": "迁移评估",
-      "description": "评估解决方案导入其它环境的风险：遮蔽、缺失、选项值丢失"
-    },
-    "d365_code_check": {
-      "title": "代码改动检查",
-      "description": "读 GitLab MR，检查脚本与插件改动发到目标环境能否运行"
-    },
-    "d365_refs": {
-      "title": "引用反查",
-      "description": "字段被哪些表单/视图/流程引用，Web 资源被谁加载，程序集有哪些步骤"
-    },
-    "d365_data": {
-      "title": "业务数据查询",
-      "description": "统计、分组或抽样读取业务记录（需环境授权）"
-    },
-    "d365_data_write": {
-      "title": "业务数据写入",
-      "description": "新建或修改一条业务记录，确认后执行（需环境授权）"
-    },
-    "d365_contract": {
-      "title": "契约漂移",
-      "description": "核对插件注册、表单脚本与站点地图在上游下游是否一致，支持豁免"
-    },
-    "d365_health": {
-      "title": "环境健康",
-      "description": "挂起与失败的后台作业、正在运行的导入发布、最近安装的解决方案"
-    },
-    "d365_reports": {
-      "title": "本机数据",
-      "description": "查看本机产物占用，按保留策略清理或压缩快照"
-    }
-  }
-}
+{
+  "meta": {
+    "title": "D365 工具箱",
+    "description": "Dynamics 365 CE 的开发与部署助手：元数据、解决方案层、迁移风险、代码改动检查、契约漂移、环境健康。"
+  },
+  "tools": {
+    "d365_envs": {
+      "title": "环境清单",
+      "description": "列出已配置环境、凭据状态与连通性"
+    },
+    "d365_metadata": {
+      "title": "元数据查询",
+      "description": "按类别查询实体、字段、表单、视图、插件、解决方案等"
+    },
+    "d365_layers": {
+      "title": "解决方案层",
+      "description": "查看组件被哪些解决方案覆盖、当前生效的是哪一层"
+    },
+    "d365_sync": {
+      "title": "同步快照",
+      "description": "把环境元数据拉成本地快照并记录采集完整度"
+    },
+    "d365_diff": {
+      "title": "快照对比",
+      "description": "比较两份快照的新增、删除与字段级修改"
+    },
+    "d365_configure": {
+      "title": "环境配置",
+      "description": "读写环境清单：列出、保存、删除或测试连接"
+    },
+    "d365_write": {
+      "title": "元数据变更",
+      "description": "准备选项值、字段、表名与视图列的修改计划，确认后执行"
+    },
+    "d365_migrate": {
+      "title": "迁移评估",
+      "description": "评估解决方案导入其它环境的风险：遮蔽、缺失、选项值丢失"
+    },
+    "d365_code_check": {
+      "title": "代码改动检查",
+      "description": "读 GitLab MR，检查脚本与插件改动发到目标环境能否运行"
+    },
+    "d365_refs": {
+      "title": "引用反查",
+      "description": "字段被哪些表单/视图/流程引用，Web 资源被谁加载，程序集有哪些步骤"
+    },
+    "d365_data": {
+      "title": "业务数据查询",
+      "description": "统计、分组或抽样读取业务记录（需环境授权）"
+    },
+    "d365_data_write": {
+      "title": "业务数据写入",
+      "description": "新建或修改一条业务记录，确认后执行（需环境授权）"
+    },
+    "d365_contract": {
+      "title": "契约漂移",
+      "description": "核对插件注册、表单脚本与站点地图在上游下游是否一致，支持豁免"
+    },
+    "d365_health": {
+      "title": "环境健康",
+      "description": "挂起与失败的后台作业、正在运行的导入发布、最近安装的解决方案"
+    },
+    "d365_reports": {
+      "title": "本机数据",
+      "description": "查看本机产物占用，按保留策略清理或压缩快照"
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-d365-kit",
-  "version": "0.34.1",
+  "version": "0.34.4",
   "type": "module",
   "description": "Dynamics 365 CE developer and deployment toolkit for DSH: metadata, layers, snapshots, migration risk, code checks, contract drift, environment health, plug-in traces, message invocation and business-record sync.",
   "license": "MIT",
@@ -58,4 +58,4 @@
       "inject": []
     }
   }
-}
+}