universal-dev-standards 6.13.0 → 6.14.0-beta.1

package/src/reconciler/desired-state-calculator.js

@@ -12,6 +12,7 @@ import { getAllStandards, getStandardSource, findOption, getOptionSource } from
 import {
   resolveToolKey,
   SUPPORTED_AI_TOOLS,
+  LEGACY_TOOL_MAPPINGS,
   MANIFEST_OPTION_BINDINGS,
   OPTIONS_INSTALL_DIR
 } from '../core/constants.js';
@@ -19,7 +20,9 @@ import {
   resolveIntegrationTargetFile,
   buildToolIntegrationConfig,
   generateIntegrationContent,
-  extractMarkedContent
+  extractMarkedContent,
+  generateAgentsMdSummary,
+  buildAgentsMdSummaryConfig
 } from '../utils/integration-generator.js';
 import { PathResolver } from '../core/paths.js';
 import { computeFileHash } from '../utils/hasher.js';
@@ -299,6 +302,61 @@ function computeExpectedIntegrationBlockHash(manifest, toolName, format) {
   }
 }
 
+/**
+ * The same block-hash computation as computeExpectedIntegrationBlockHash,
+ * for the OTHER AGENTS.md producer (the universal summary — see
+ * isAgentsMdGenuinelyToolOwned's docblock for why there are two).
+ *
+ * @param {Object} manifest
+ * @returns {string|null}
+ */
+function computeExpectedAgentsMdSummaryHash(manifest) {
+  try {
+    const generated = generateAgentsMdSummary(buildAgentsMdSummaryConfig(manifest));
+    const { content: blockContent } = extractMarkedContent(generated, 'markdown');
+    if (!blockContent) return null;
+    return `sha256:${createHash('sha256').update(blockContent).digest('hex')}`;
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * Whether `toolName` is a tool the project actually selected, as opposed to
+ * one `resolveToolKey` happened to resolve an entry to because a filename
+ * collided.
+ *
+ * AGENTS.md is the one case in `SUPPORTED_AI_TOOLS` where this distinction
+ * matters: it is opencode's per-tool file, but it is ALSO the generic
+ * "universal AGENTS.md summary" target that `generateAgentsMd` writes for
+ * ANY project regardless of which AI tools are selected (`uds init` always
+ * pushes 'AGENTS.md' into `manifest.integrations` once that summary is
+ * written — see init.js's `generateUniversalAgentsMd` call site — purely as
+ * a "this file is UDS-managed" marker, not as a record of a tool choice).
+ * `resolveToolKey('AGENTS.md')` resolves to 'opencode' regardless, because
+ * that is simply the first (only) tool whose default file matches.
+ *
+ * Every other file in `SUPPORTED_AI_TOOLS` maps 1:1 to exactly one tool, so
+ * this check is only ever consulted for opencode/AGENTS.md; it is written
+ * generically in case that ever changes.
+ *
+ * Confirmed as a real bug, not a hypothetical: `uds init` (aiTools:
+ * ['claude-code'] only) followed immediately by `uds update --apply` — zero
+ * manifest edits, zero version change, nothing to reconcile — silently
+ * replaced AGENTS.md's content, because `calculateIntegrations` treated the
+ * bare tracking marker as evidence opencode was selected. Confirmed in
+ * production on two real adopters (asiaostrich-telemetry-server,
+ * EngramGraph) and dev-platform's own `.standards/` install, all three with
+ * `aiTools` containing no codex/opencode entry.
+ *
+ * @param {string} toolName - Tool key to check (e.g. 'opencode')
+ * @param {Object} manifest - Project manifest
+ * @returns {boolean}
+ */
+function isToolGenuinelySelected(toolName, manifest) {
+  return (manifest.aiTools || []).some((t) => (LEGACY_TOOL_MAPPINGS[t] || t) === toolName);
+}
+
 /**
  * Calculate expected integration files.
  * For integrations we track the UDS marker block, not the entire file.
@@ -325,6 +383,31 @@ function calculateIntegrations(state, manifest) {
     // detection) would treat that file as unmanaged and CLAUDE.md as desired.
     const relativePath = resolveIntegrationTargetFile(toolName, manifest) || toolConfig.file;
 
+    // See isToolGenuinelySelected's docblock. `relativePath === 'AGENTS.md'`
+    // rather than `toolName === 'opencode'`: correct either way today (only
+    // opencode's file is 'AGENTS.md'), but this is the actual thing that
+    // matters — which FILE is ambiguous — should another tool ever share it.
+    if (relativePath === 'AGENTS.md' && !isToolGenuinelySelected(toolName, manifest)) {
+      if (!manifest.generateAgentsMd) continue; // Not wanted at all; nothing to track.
+      state.integrations.set(relativePath, {
+        relativePath,
+        hash: computeExpectedAgentsMdSummaryHash(manifest),
+        size: null,
+        category: 'integration',
+        sourcePath: null,
+        metadata: {
+          toolName: null,
+          // Read by plan-executor.js's executeMigrateBlock to pick the
+          // matching writer (writeAgentsMdSummary, not writeIntegrationFile).
+          generator: 'summary',
+          format: 'markdown',
+          toolCategory: null,
+          supports: []
+        }
+      });
+      continue;
+    }
+
     state.integrations.set(relativePath, {
       relativePath,
       // XSPEC adopter-report Q6: this used to be a hardcoded `null` ("hashes

package/src/reconciler/plan-executor.js

@@ -14,7 +14,12 @@
 import { existsSync, unlinkSync, mkdirSync, rmSync, copyFileSync, statSync } from 'fs';
 import { join, dirname } from 'path';
 import { copyStandard } from '../utils/copier.js';
-import { writeIntegrationFile, buildToolIntegrationConfig } from '../utils/integration-generator.js';
+import {
+  writeIntegrationFile,
+  buildToolIntegrationConfig,
+  writeAgentsMdSummary,
+  buildAgentsMdSummaryConfig
+} from '../utils/integration-generator.js';
 import {
   installSkillsToMultipleAgents,
   installCommandsToMultipleAgents
@@ -342,6 +347,34 @@ function executeDelete(projectPath, action, manifest) {
  * Uses writeIntegrationFile which handles marker-based section replacement.
  */
 function executeMigrateBlock(projectPath, action, manifest) {
+  // AGENTS.md tracked as the universal summary rather than a genuine
+  // per-tool integration — see desired-state-calculator.js's
+  // isToolGenuinelySelected docblock. Written through writeAgentsMdSummary,
+  // not writeIntegrationFile, so `--apply` produces the SAME content a plain
+  // `uds update` would for this case, instead of the opencode-shaped block a
+  // project with no codex/opencode selected never asked for.
+  // `diffIntegrations` (diff-engine.js) nests the desired-state metadata
+  // under `details.metadata`, not at the top level of `details` — only
+  // `toolName`/`format`/the hash fields are copied out. Checking
+  // `action.details?.generator` (rather than `action.details?.metadata?.generator`)
+  // is silently always false, and this branch would never fire; the
+  // fallback below then reads `action.details?.toolName` as `null` (correctly
+  // propagated from calculateIntegrations) and fails with "No tool name in
+  // action details" — reproduced live via `uds update --apply` E2E
+  // (tests/e2e/update-version-advances.test.js) before this fix.
+  if (action.details?.metadata?.generator === 'summary') {
+    const config = buildAgentsMdSummaryConfig(manifest);
+    const result = writeAgentsMdSummary(config, projectPath);
+    if (result.success) {
+      if (result.blockHashInfo) {
+        manifest.integrationBlockHashes[result.path] = result.blockHashInfo;
+      }
+      if (manifest.fileHashes) delete manifest.fileHashes[result.path];
+      return { action, success: true };
+    }
+    return { action, success: false, error: result.error };
+  }
+
   const toolName = action.details?.toolName;
   if (!toolName) {
     return { action, success: false, error: 'No tool name in action details' };

package/src/uninstallers/hook-uninstaller.js

@@ -2,7 +2,7 @@ import { existsSync, readFileSync, writeFileSync, unlinkSync } from 'fs';
 import { join, basename } from 'path';
 import {
   collectHookConfigs, standardsSourceDir, hooksSourceDir,
-  CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT,
+  CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT, AGY_HOOK_SCRIPT,
 } from '../installers/hooks-installer.js';
 
 /**
@@ -17,7 +17,7 @@ import {
  * test placing a user hook at `scripts/hooks/my-own-hook.mjs` lost it).
  * The safe signature is path *and* a script basename UDS is actually known to
  * ship right now — the same set collectHookConfigs() derives for install,
- * plus the two fixed Codex/Gemini script names.
+ * plus the three fixed Codex/Gemini/agy script names.
  *
  * 🔴 Until this file added the three functions below, uninstall only ever
  * touched .husky/pre-commit and .git/hooks/pre-commit — the settings.json /
@@ -37,7 +37,7 @@ function commandOf(entry) {
 /** Script basenames UDS currently ships and would install a hook entry for. */
 function knownUdsHookScripts() {
   const { scripts } = collectHookConfigs(standardsSourceDir(), hooksSourceDir());
-  return new Set([...scripts.map((s) => basename(s)), CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT]);
+  return new Set([...scripts.map((s) => basename(s)), CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT, AGY_HOOK_SCRIPT]);
 }
 
 function isUdsHookEntry(entry, knownScripts) {
@@ -159,10 +159,112 @@ export function uninstallGeminiHooks(projectPath, options = {}) {
   });
 }
 
+/**
+ * A bare `{ type, command }` handler (agy's shape — no `hooks[]` wrapper) that
+ * runs one of the scripts UDS ships.
+ */
+function isUdsAgyHandler(handler, knownScripts) {
+  const cmd = handler && typeof handler.command === 'string' ? handler.command : undefined;
+  // agy's hook cwd is `.agents/`, so the installed command climbs out first
+  // (`node ../scripts/hooks/...`); the earlier `node scripts/hooks/...` form
+  // is still recognised so an install made before that fix can be removed.
+  return typeof cmd === 'string' && /^node (?:\.\.\/)?scripts\/hooks\//.test(cmd) && knownScripts.has(basename(cmd));
+}
+
+/**
+ * Remove UDS's Stop handler from .agents/hooks.json (installAgyHooks()'s output).
+ *
+ * agy's file is `{ "<hook name>": { "<Event>": handler[] } }`, not the
+ * `{ hooks: { <Event>: entry[] } }` the other three share, so the generic
+ * stripper cannot be used. Only handlers that run a UDS-shipped script are
+ * removed, and from ANY hook name (an adopter may have renamed our key); a
+ * user's own handler, even inside the same name or the same event array, stays.
+ * A name left with no event after removal is dropped, and a file left empty is
+ * deleted.
+ */
+export function uninstallAgyHooks(projectPath, options = {}) {
+  const configPath = join(projectPath, '.agents', 'hooks.json');
+  const label = '.agents/hooks.json';
+  const dryRun = options.dryRun || false;
+  const result = { removed: [], skipped: [], errors: [] };
+  if (!existsSync(configPath)) return result;
+
+  let config;
+  try {
+    config = JSON.parse(readFileSync(configPath, 'utf-8'));
+  } catch (error) {
+    result.errors.push(`${label} — could not parse (${error.message}); left untouched`);
+    return result;
+  }
+  if (!config || typeof config !== 'object' || Array.isArray(config)) {
+    result.skipped.push(`${label} (no UDS hook entries found)`);
+    return result;
+  }
+
+  const knownScripts = knownUdsHookScripts();
+  let removedCount = 0;
+  const next = {};
+  for (const [name, def] of Object.entries(config)) {
+    if (!def || typeof def !== 'object' || Array.isArray(def)) {
+      next[name] = def;
+      continue;
+    }
+    const nextDef = {};
+    let touched = false;
+    let eventsLeft = 0;
+    for (const [key, value] of Object.entries(def)) {
+      if (!Array.isArray(value)) {
+        nextDef[key] = value; // e.g. `enabled`
+        continue;
+      }
+      const kept = value.filter((h) => {
+        if (isUdsAgyHandler(h, knownScripts)) {
+          removedCount += 1;
+          touched = true;
+          return false;
+        }
+        return true;
+      });
+      if (kept.length > 0) {
+        nextDef[key] = kept;
+        eventsLeft += 1;
+      }
+    }
+    // A name we emptied is dropped (nothing but `enabled` would remain);
+    // a name we did not touch is kept exactly as found.
+    if (touched && eventsLeft === 0) continue;
+    next[name] = touched ? nextDef : def;
+  }
+
+  if (removedCount === 0) {
+    result.skipped.push(`${label} (no UDS hook entries found)`);
+    return result;
+  }
+
+  const entryLabel = `${label} (${removedCount} UDS hook ${removedCount === 1 ? 'entry' : 'entries'})`;
+  if (dryRun) {
+    result.removed.push(entryLabel);
+    return result;
+  }
+  try {
+    if (Object.keys(next).length === 0) {
+      unlinkSync(configPath);
+      result.removed.push(`${entryLabel}, file removed — created by UDS, now empty`);
+    } else {
+      writeFileSync(configPath, JSON.stringify(next, null, 2) + '\n');
+      result.removed.push(entryLabel);
+    }
+  } catch (error) {
+    result.errors.push(`${label} — ${error.message}`);
+  }
+  return result;
+}
+
 /**
  * Remove UDS-related lines from .husky/pre-commit, the native
  * .git/hooks/pre-commit fallback, and the enforcement-hook entries UDS wrote
- * into .claude/settings.json, .codex/hooks.json and .gemini/settings.json.
+ * into .claude/settings.json, .codex/hooks.json, .gemini/settings.json and
+ * .agents/hooks.json.
  * @param {string} projectPath - Project root path
  * @param {Object} options - { dryRun: boolean }
  * @returns {Object} { removed: string[], skipped: string[], errors: string[] }
@@ -231,6 +333,7 @@ export function uninstallHook(projectPath, options = {}) {
     uninstallClaudeCodeHooks(projectPath, { dryRun }),
     uninstallCodexHooks(projectPath, { dryRun }),
     uninstallGeminiHooks(projectPath, { dryRun }),
+    uninstallAgyHooks(projectPath, { dryRun }),
   ]) {
     result.removed.push(...sub.removed);
     result.skipped.push(...sub.skipped);

package/src/utils/integration-generator.js

@@ -3462,21 +3462,41 @@ function withSelectedOptions(manifest) {
   return [...standards, ...extra];
 }
 
-export function buildToolIntegrationConfig(manifest, tool) {
+/**
+ * Resolve the content (display) language an integration block should be
+ * written in, from a project's manifest.
+ *
+ * Content language comes from `display_language` — the setting whose entire
+ * job is "what language do you want to read" — and only falls back to
+ * `output_language`, which is the commit-message language, when the project
+ * has no display setting to go on. They are different questions: `uds init`
+ * has always used the first, and this was the single place that used the
+ * second correctly (XSPEC-343 R2 / a Windows-adopter fix on 2026-09-16).
+ *
+ * `update.js`'s two other, older per-tool config builders (the plain
+ * `uds update` main flow and its `--plan` dry-run) each derived `language`
+ * independently and never picked up that fix — they read only
+ * `output_language`/`commit_language`, so a project installed with
+ * `display_language: zh-tw` and `output_language: bilingual` got the correct
+ * Chinese heading from `init`/the reconciler and an English one the next
+ * plain `uds update`, silently overwriting the block that was already there.
+ * Both call sites now use this function instead of re-deriving the value.
+ *
+ * @param {Object} manifest - Project manifest
+ * @returns {'en'|'zh-tw'|'bilingual'} Resolved content language
+ */
+export function resolveIntegrationLanguage(manifest) {
   const selected = manifest.options?.output_language || manifest.options?.commit_language || 'english';
-
-  // Content language comes from `display_language` — the setting whose entire
-  // job is "what language do you want to read" — and only falls back to
-  // `output_language`, which is the commit-message language, when the project
-  // has no display setting to go on. They are different questions: `uds init`
-  // has always used the first, every regeneration path used the second, and a
-  // project installed with `--locale zh-tw` therefore got Chinese instructions
-  // from `init` and English ones from the next `uds update`, silently.
   const display = manifest.options?.display_language;
   const fromOutput = selected === 'bilingual'
     ? 'bilingual'
     : selected === 'traditional-chinese' ? 'zh-tw' : 'en';
-  const language = ['en', 'zh-tw', 'bilingual'].includes(display) ? display : fromOutput;
+  return ['en', 'zh-tw', 'bilingual'].includes(display) ? display : fromOutput;
+}
+
+export function buildToolIntegrationConfig(manifest, tool) {
+  const language = resolveIntegrationLanguage(manifest);
+  const selected = manifest.options?.output_language || manifest.options?.commit_language || 'english';
   const resolved = resolveContentModeForTool(tool, manifest.contentMode || 'auto');
 
   return {
@@ -3502,6 +3522,33 @@ export function buildToolIntegrationConfig(manifest, tool) {
   };
 }
 
+/**
+ * Build the generation config for the universal AGENTS.md summary
+ * (`generateAgentsMdSummary`/`writeAgentsMdSummary`) from the manifest.
+ *
+ * This is the OTHER AGENTS.md producer — used when no genuinely-selected AI
+ * tool (codex/opencode) claims AGENTS.md as its own file, i.e. the file is
+ * present in `manifest.integrations` only because `uds init` tracks it there
+ * once `generateAgentsMd` writes one, not because a tool was chosen. Mirrors
+ * `commands/update.js`'s own construction of this same config exactly, so
+ * the reconciler (`--apply`) and a plain `uds update` compute and write
+ * IDENTICAL content for this case — see resolveIntegrationLanguage's and
+ * this whole area's history for what happens when "the same config" is
+ * derived independently in two places instead of shared.
+ *
+ * @param {Object} manifest - Project manifest
+ * @returns {Object} Config for generateAgentsMdSummary/writeAgentsMdSummary
+ */
+export function buildAgentsMdSummaryConfig(manifest) {
+  return {
+    installedStandards: manifest.standards || [],
+    standardsFormat: manifest.format || 'ai',
+    language: manifest.options?.display_language || 'en',
+    outputLanguage: manifest.options?.output_language || manifest.options?.commit_language || 'english',
+    standardOptions: manifest.options || {}
+  };
+}
+
 /**
  * Heading of the index-mode standards block. Not localised — both the English and
  * the Chinese body sit under this exact string, so it is a stable marker.
@@ -3835,13 +3882,45 @@ export function generateAgentsMdSummary(config = {}) {
   lines.push('');
 
   // Installed Standards Index
-  lines.push('<!-- UDS:STANDARDS:START -->');
-  lines.push('## Installed Standards');
-  lines.push('');
+  //
+  // Built as a separate block body and wrapped with wrapWithMarkers (the
+  // same helper generateIntegrationContent's own block uses), rather than
+  // hand-rolling the `<!-- UDS:STANDARDS:START/END -->` lines directly.
+  // Hand-rolled, this block never carried the
+  // `<!-- WARNING: This block is managed by UDS ... -->` line that
+  // wrapWithMarkers adds — so a hash computed straight from this function's
+  // output (desired-state-calculator.js's computeExpectedAgentsMdSummaryHash)
+  // never matched a real on-disk file's hash (computeIntegrationBlockHash,
+  // hasher.js — which always includes that line, since a written file only
+  // ever gets it added by the merge path's own wrapWithMarkers call), and
+  // `uds update --apply` reported "content differs" and re-wrote AGENTS.md
+  // on EVERY run forever, settled state or not — a non-convergent
+  // reconciliation loop, reproduced with a second `--apply` immediately
+  // after a first that had already "fixed" everything.
+  const blockLines = [];
+  // XSPEC-357 R7's disclosure was added to this function's HEADER above
+  // (2026-08-18) but never to the marker block itself. `writeAgentsMdSummary`'s
+  // marker-based update for an EXISTING file only ever replaces the content
+  // BETWEEN the markers — the header (including that reminder) is copied
+  // verbatim from whatever the file already had. Every adopter whose
+  // AGENTS.md predates 2026-08-18 therefore never received the reminder via
+  // the header (nothing ever regenerates it) and never received it in the
+  // block either, since it was never written there. Measured 2026-09-28
+  // against two real adopters (asiaostrich-telemetry-server, EngramGraph):
+  // reminder present at neither the file level nor the block level, 0 of 2.
+  // Placed here, inside the block, it reaches every project on every
+  // `uds update`/`--apply`, new or existing, regardless of the header's age.
+  // Uses the SAME wording as the per-tool generator's index/minimal
+  // templates (generateIndexDisclosure) rather than inventing a third
+  // phrasing for a third producer of the same idea.
+  blockLines.push(generateIndexDisclosure('markdown', language));
+  blockLines.push('');
+  blockLines.push('## Installed Standards');
+  blockLines.push('');
 
   if (installedStandards.length > 0) {
-    lines.push('All standards are in `.standards/`. Installed standards:');
-    lines.push('');
+    blockLines.push('All standards are in `.standards/`. Installed standards:');
+    blockLines.push('');
 
     // Resolved before filtering, not after. The filter asks for an `.ai.yaml`
     // suffix and a manifest's core entries are registry IDs, which carry no
@@ -3867,14 +3946,13 @@ export function generateAgentsMdSummary(config = {}) {
       if (!filename?.endsWith(suffix)) continue;
       const isOption = entry.includes('/options/') || entry.includes('\\options\\');
       const dir = isOption ? '.standards/options' : '.standards';
-      lines.push(`- \`${dir}/${filename}\` — ${filename.replace(suffix, '')}`);
+      blockLines.push(`- \`${dir}/${filename}\` — ${filename.replace(suffix, '')}`);
     }
   } else {
-    lines.push('No standards installed yet. Run `npx uds init` to install.');
+    blockLines.push('No standards installed yet. Run `npx uds init` to install.');
   }
 
-  lines.push('');
-  lines.push('<!-- UDS:STANDARDS:END -->');
+  lines.push(wrapWithMarkers(blockLines.join('\n'), 'markdown'));
   lines.push('');
 
   // Boundaries

package/standards-registry.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "version": "6.13.0",
+  "version": "6.14.0-beta.1",
   "lastUpdated": "2026-05-13",
   "description": "Standards registry for universal-dev-standards with integrated skills and AI-optimized formats",
   "formats": {
@@ -58,14 +58,14 @@
     "standards": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
-      "version": "6.13.0"
+      "version": "6.14.0-beta.1"
     },
     "skills": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
       "localPath": "skills",
       "rawUrl": "https://raw.githubusercontent.com/AsiaOstrich/universal-dev-standards/main/skills",
-      "version": "6.13.0",
+      "version": "6.14.0-beta.1",
       "note": "Skills are now included in the main repository under skills/"
     }
   },
@@ -1799,7 +1799,7 @@
       },
       "category": "reference",
       "skillName": null,
-      "description": "Downstream of deferred-item-exit: once an item has an exit, its carrier must stay trustworthy. Capture costs no more than two fields; a waiting item records its release condition; derivable fields are generated, not hand-written; a coverage figure states what it could not see; a checkpoint at turn end reports open work but never blocks"
+      "description": "Downstream of deferred-item-exit: once an item has an exit, its carrier must stay trustworthy. Capture costs no more than two fields; a waiting item records its release condition; derivable fields are generated, not hand-written; a coverage figure states what it could not see; a checkpoint at turn end reports open work but never blocks; goal and progress live in different carriers, an edit to the goal leaves a record, and a next action names a file, test, command or requirement"
     },
     {
       "id": "verification-evidence",
@@ -2295,7 +2295,7 @@
       "id": "license-compliance",
       "name": "License Compliance Standards",
       "nameZh": "授權合規標準",
-      "version": "6.13.0",
+      "version": "6.14.0-beta.1",
       "source": {
         "human": "core/license-compliance.md",
         "ai": "ai/standards/license-compliance.ai.yaml"
@@ -2307,7 +2307,7 @@
       "id": "verification-oracle",
       "name": "Verification Oracle Standards",
       "nameZh": "驗證 Oracle 標準",
-      "version": "6.13.0",
+      "version": "6.14.0-beta.1",
       "source": {
         "human": "core/verification-oracle.md",
         "ai": "ai/standards/verification-oracle.ai.yaml"
@@ -2319,7 +2319,7 @@
       "id": "model-provenance",
       "name": "Model Provenance Policy Standards",
       "nameZh": "模型來源政策標準",
-      "version": "6.13.0",
+      "version": "6.14.0-beta.1",
       "source": {
         "human": "core/model-provenance.md",
         "ai": "ai/standards/model-provenance.ai.yaml"
@@ -2331,7 +2331,7 @@
       "id": "resource-cost-boundary",
       "name": "Resource / Cost Boundary Declaration Standards",
       "nameZh": "資源／成本邊界宣告標準",
-      "version": "6.13.0",
+      "version": "6.14.0-beta.1",
       "source": {
         "human": "core/resource-cost-boundary.md",
         "ai": "ai/standards/resource-cost-boundary.ai.yaml"