@unbrained/pm-cli 2026.7.6 → 2026.7.8

package/dist/cli-bundle/chunks/chunk-JINYH2DB.js

@@ -1,371 +0,0 @@
-// dist/core/diagnostics/remediation.js
-!(function() {
-  try {
-    var e = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof globalThis ? globalThis : "undefined" != typeof self ? self : {}, n = new e.Error().stack;
-    n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "6700669e-bb33-5b85-a194-73e559d13abd");
-  } catch (e2) {
-  }
-})();
-var REMEDIATION_REGISTRY = Object.freeze([
-  // --- pm health: directories ---
-  {
-    code: "missing_directory",
-    command: "pm init",
-    summary: "Recreate missing tracker directories (pm init is idempotent and restores the scaffold)."
-  },
-  // --- pm health: settings (read/parse) ---
-  {
-    code: "settings_read_invalid_json",
-    command: "pm config list --json",
-    summary: "settings.json is not valid JSON and pm fell back to defaults; fix the syntax error in the reported path, then re-run."
-  },
-  {
-    code: "settings_read_invalid_schema",
-    command: "pm config list --json",
-    summary: "settings.json failed schema validation and pm fell back to defaults; correct the reported key in the file, then re-run."
-  },
-  {
-    code: "settings_read_merge_failed",
-    command: "pm config list --json",
-    summary: "Global/project settings could not be merged; reconcile the conflicting keys in the reported settings files."
-  },
-  // --- pm health: settings_values ---
-  {
-    code: "settings:id_prefix_empty",
-    command: "pm config list --json",
-    summary: 'id_prefix is empty; set a non-empty "id_prefix" in settings.json so generated item ids are well-formed.'
-  },
-  {
-    code: "settings:locks_ttl_non_positive",
-    command: "pm config list --json",
-    summary: 'locks.ttl_seconds must be positive; set a positive "locks.ttl_seconds" in settings.json.'
-  },
-  // --- pm health: telemetry (advisory) ---
-  {
-    code: "telemetry_state_invalid_json",
-    command: "pm health --check-telemetry",
-    summary: "Local telemetry state file is corrupt; pm recreates it on the next flush. Advisory only."
-  },
-  {
-    code: "telemetry_queue_invalid_rows",
-    command: "pm health --check-telemetry",
-    summary: "The telemetry queue has unparseable rows; they are skipped on the next flush. Advisory only."
-  },
-  {
-    code: "telemetry_queue_pending",
-    command: "pm health --check-telemetry",
-    summary: "Telemetry events are queued; they flush automatically on the next reachable command. Advisory only."
-  },
-  {
-    code: "telemetry_queue_high_retries",
-    command: "pm telemetry flush",
-    summary: "Some queued telemetry events are near retry exhaustion; flush now and verify endpoint reachability before entries are dropped."
-  },
-  {
-    code: "telemetry_endpoint_probe_failed",
-    command: "pm health --check-telemetry",
-    summary: "The telemetry endpoint is unreachable; events stay queued until it recovers. Advisory only."
-  },
-  {
-    code: "telemetry_endpoint_probe_http_status",
-    command: "pm health --check-telemetry",
-    summary: "The telemetry endpoint returned a non-success status; events stay queued until it recovers. Advisory only."
-  },
-  {
-    code: "telemetry_schema_version_behind",
-    command: "pm health --check-telemetry",
-    summary: "Client schema is behind server; upgrade pm-cli to emit the latest event shape."
-  },
-  {
-    code: "telemetry_otel_export_failing",
-    command: "pm health --check-telemetry",
-    summary: "OTLP trace spans are queued but the traces endpoint export is failing; spans retry automatically on the next reachable command, or set PM_TELEMETRY_OTEL_DISABLED=1 to skip OTLP export. Advisory only."
-  },
-  // --- pm health: integrity ---
-  {
-    code: "integrity_item_unreadable",
-    command: "pm validate --check-files --verbose-diagnostics",
-    summary: "An item file could not be read; restore or repair the file at the reported path."
-  },
-  {
-    code: "integrity_item_parse_failed",
-    command: "pm validate --check-files --verbose-diagnostics",
-    summary: "An item file failed to parse; fix the malformed front matter at the reported path."
-  },
-  {
-    code: "integrity_item_conflict_marker",
-    command: "pm validate --check-files --verbose-diagnostics",
-    summary: "An item file contains Git conflict markers; resolve the <<<<<<< / >>>>>>> markers at the reported line."
-  },
-  {
-    code: "integrity_history_unreadable",
-    command: "pm history-repair <id>",
-    summary: "A history stream could not be read; re-anchor the affected item's history chain."
-  },
-  {
-    code: "integrity_history_invalid_json",
-    command: "pm history-repair <id>",
-    summary: "A history stream contains invalid JSON; re-anchor the affected item's history chain."
-  },
-  {
-    code: "integrity_history_conflict_marker",
-    command: "pm history-repair <id>",
-    summary: "A history stream contains Git conflict markers; resolve the markers, then re-anchor the chain."
-  },
-  // --- pm health (integrity) + pm validate (format_version): item format version ---
-  {
-    code: "integrity_item_outdated_format_version",
-    command: "pm validate --verbose-diagnostics",
-    summary: "An item predates the current storage format version; a pm storage migration rewrites it. Use --verbose-diagnostics to list the affected items."
-  },
-  {
-    code: "integrity_item_ahead_format_version",
-    command: "npm install -g @unbrained/pm-cli@latest",
-    summary: "An item was written by a newer pm format version than this runtime supports; upgrade pm to read and validate it safely."
-  },
-  // --- pm health: history_drift ---
-  // `pm health` rewrites these commands to `pm history-repair --all` in the
-  // per-check remediation_map when more than one stream is drifted.
-  {
-    code: "history_drift_missing_stream",
-    command: "pm history-repair <id>",
-    summary: "The item has no history stream; re-anchor the chain to rebuild it (pm history-repair --all repairs every drifted stream in one pass)."
-  },
-  {
-    code: "history_drift_unreadable_stream",
-    command: "pm history-repair <id>",
-    summary: "The item's history stream is unreadable; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass)."
-  },
-  {
-    code: "history_drift_hash_mismatch",
-    command: "pm history-repair <id>",
-    summary: "The item's content hash no longer matches its history; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass)."
-  },
-  {
-    code: "history_drift_chain_mismatch",
-    command: "pm history-repair <id>",
-    summary: "The item's history chain is broken; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass)."
-  },
-  // --- pm health: storage (history compaction policy) ---
-  {
-    code: "history_stream_over_compact_threshold",
-    command: "pm history-compact <id>",
-    summary: "The history stream exceeds the configured compaction threshold; compact it (pm history-compact --all-streams sweeps every over-threshold stream in one pass)."
-  },
-  // --- pm health: locks ---
-  {
-    code: "locks_stale_count",
-    command: "pm gc --scope locks",
-    summary: "Stale item-claim locks (embedded ttl elapsed) can block mutations; sweep them \u2014 gc retains active and unparseable locks."
-  },
-  {
-    code: "locks_unreadable",
-    command: "pm gc --scope locks --dry-run",
-    summary: "Some lock files could not be read; preview the sweep and inspect the unreadable files manually \u2014 gc never deletes what it cannot read."
-  },
-  // --- pm health: extensions ---
-  // Most extension findings keep their richer, contextual
-  // `details.triage.remediation` and are intentionally absent here. The
-  // partial-coverage code is the exception: it is not a per-extension triage
-  // result but a system-wide adoption gap (unmanaged installs the update-health
-  // scan had to skip), so it has a single deterministic fix and belongs in the
-  // shared registry like any other health finding (pm-bdvm).
-  {
-    code: "extension_update_health_partial_coverage",
-    command: "pm extension --adopt-all --project",
-    summary: "Update-health coverage is partial because unmanaged extensions were skipped; adopt the existing installs into managed metadata so the update scan covers them (use --global for global-scope extensions, or pm package --adopt-all when working with packages)."
-  },
-  // --- pm health: vectorization ---
-  {
-    code: "vectorization_stale_items_remaining",
-    command: "pm health --refresh-vectors",
-    summary: "Some items have stale embeddings; refresh vectors so semantic search results stay current."
-  },
-  {
-    code: "vectorization_embedding_identity_changed",
-    command: "pm reindex --mode semantic",
-    summary: "Embedding provider/model changed since the last index; run a semantic reindex to rebuild vectors."
-  },
-  // --- pm validate: metadata ---
-  // Note: validate_metadata_missing_author has no entry on purpose. `pm update
-  // --author` sets the mutation/audit author (history), not the item's
-  // `metadata.author` front-matter field, and there is no CLI flag that writes
-  // that field — so emitting a command here would record an audit entry without
-  // clearing the finding. A missing item author must be restored at the source.
-  {
-    code: "validate_metadata_missing_acceptance_criteria",
-    command: 'pm update <id> --acceptance-criteria "<criteria>"',
-    summary: "Backfill the missing acceptance criteria on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_estimate",
-    command: 'pm update <id> --estimate "<estimate>"',
-    summary: "Backfill the missing estimate on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_close_reason",
-    command: 'pm update <id> --close-reason "<reason>"',
-    summary: "Backfill the missing close reason on the reported closed item(s)."
-  },
-  {
-    code: "validate_metadata_missing_reviewer",
-    command: 'pm update <id> --reviewer "<name>"',
-    summary: "Backfill the missing reviewer on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_risk",
-    command: 'pm update <id> --risk "<level>"',
-    summary: "Backfill the missing risk on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_confidence",
-    command: 'pm update <id> --confidence "<level>"',
-    summary: "Backfill the missing confidence on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_sprint",
-    command: 'pm update <id> --sprint "<sprint>"',
-    summary: "Backfill the missing sprint on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_missing_release",
-    command: 'pm update <id> --release "<release>"',
-    summary: "Backfill the missing release on the reported item(s)."
-  },
-  {
-    code: "validate_metadata_custom_profile_missing_required_fields",
-    command: 'pm config set metadata-required-fields --criterion "<field>"',
-    summary: "Config-driven finding: the custom metadata profile has no required fields configured and falls back to core, so configure the fields rather than mutating items."
-  },
-  {
-    code: "validate_metadata_duplicate_issue_codes",
-    command: 'pm update <id> --title "<distinct title>"',
-    summary: "Two or more items share one logical issue code (GH-235); give each a distinct title so the derived code is unique, or close the redundant item with pm close <id> --duplicate-of <canonical-id> (closed-as-duplicate items are excluded from the check)."
-  },
-  // --- pm validate: resolution ---
-  {
-    code: "validate_resolution_missing_fields",
-    command: 'pm update <id> --resolution "<how resolved>"',
-    summary: "Backfill resolution / expected_result / actual_result on the reported closed item(s)."
-  },
-  // --- pm validate: lifecycle ---
-  {
-    code: "validate_lifecycle_active_closure_like_metadata",
-    command: "pm update <id> --unset <closure-like-field>",
-    summary: "Clear the closure-like field the validator flags on this active item \u2014 the detail row names it (resolution / actual-result / blocked-reason) \u2014 or close the item if it is actually done."
-  },
-  {
-    code: "validate_lifecycle_active_terminal_parent",
-    command: "pm update <id> --parent <active-parent-id>",
-    summary: "Reopen the terminal parent or move the active child under a non-terminal parent."
-  },
-  {
-    code: "validate_lifecycle_stale_blockers",
-    command: "pm update <id> --unset blocked-by --unset blocked-reason",
-    summary: "Resolve the stale blocker the validator flags: clear blocked-by/blocked-reason when they linger on a non-blocked item or report a resolved blocker; if instead a blocked item is missing blocker context, add the context or move it out of a blocked status."
-  },
-  {
-    code: "validate_lifecycle_dependency_cycles_error",
-    command: "pm update <id> --dep-remove <dep-id>",
-    summary: "Break the dependency cycle by removing one edge from the reported cycle."
-  },
-  {
-    code: "validate_lifecycle_dependency_cycles",
-    command: "pm update <id> --dep-remove <dep-id>",
-    summary: "Break the dependency cycle by removing one edge from the reported cycle."
-  },
-  {
-    code: "validate_hierarchy_parent_cycle_error",
-    command: "pm update <id> --parent <other-id>",
-    summary: "Break the parent-hierarchy cycle by reparenting one item in the reported cycle to a non-cyclic parent (or clear it with pm update <id> --unset parent)."
-  },
-  {
-    code: "validate_hierarchy_parent_cycle",
-    command: "pm update <id> --parent <other-id>",
-    summary: "Break the parent-hierarchy cycle by reparenting one item in the reported cycle to a non-cyclic parent (or clear it with pm update <id> --unset parent)."
-  },
-  // --- pm validate: files ---
-  {
-    code: "validate_files_missing_linked_paths",
-    command: "pm <files|docs> <id> --remove <path>",
-    summary: "The check spans both item.files and item.docs under one code: restore the missing linked artifact, or unlink it with pm files (linked file) or pm docs (linked doc)."
-  },
-  {
-    code: "validate_files_orphaned_paths",
-    command: "pm <files|docs> <id> --add <path>",
-    summary: "Link the orphaned artifact with pm files (file) or pm docs (doc), or remove it from the workspace."
-  },
-  {
-    code: "validate_files_tracked_all_strict_forces_pm_internals",
-    command: "pm validate --check-files --include-pm-internals",
-    summary: "tracked-all-strict scan flagged pm internals; re-run with --include-pm-internals or a softer --scan-mode."
-  },
-  // --- pm validate: history_drift ---
-  {
-    code: "validate_history_drift_missing_streams",
-    command: "pm history-repair <id>",
-    summary: "Re-anchor the history chains of the items missing a history stream."
-  },
-  {
-    code: "validate_history_drift_unreadable_streams",
-    command: "pm history-repair <id>",
-    summary: "Re-anchor the history chains of the items with an unreadable history stream."
-  },
-  {
-    code: "validate_history_drift_hash_mismatches",
-    command: "pm history-repair <id>",
-    summary: "Re-anchor the history chains of the items whose content hash drifted."
-  },
-  {
-    code: "validate_history_drift_chain_mismatches",
-    command: "pm history-repair <id>",
-    summary: "Re-anchor the history chains of the items with a broken history chain."
-  },
-  // --- pm validate: command_references ---
-  {
-    code: "validate_command_references_stale_pm_ids",
-    command: 'pm update <id> --replace-tests --test "command=<corrected-command>" [--test ...]',
-    summary: "Correct the stale pm-ID inside the item's linked test command (the check scans tests[].command, not the body). --replace-tests overwrites the entire tests list, so re-include the item's other linked tests in the same call."
-  },
-  {
-    code: "validate_format_version_outdated_items",
-    command: "pm validate --verbose-diagnostics",
-    summary: "One or more items predate the current storage format version; a pm storage migration rewrites them. Use --verbose-diagnostics to list the affected items."
-  },
-  {
-    code: "validate_format_version_ahead_items",
-    command: "npm install -g @unbrained/pm-cli@latest",
-    summary: "One or more items were written by a newer pm format version than this runtime supports; upgrade pm to read and validate them safely."
-  }
-]);
-function resolveRemediation(warning) {
-  if (typeof warning !== "string") {
-    return void 0;
-  }
-  const normalized = warning.trim();
-  for (const entry of REMEDIATION_REGISTRY) {
-    if (normalized === entry.code || normalized.startsWith(`${entry.code}:`)) {
-      return entry;
-    }
-  }
-  return void 0;
-}
-function buildRemediationMap(warnings) {
-  const map = {};
-  for (const warning of warnings) {
-    const entry = resolveRemediation(warning);
-    if (entry !== void 0 && !Object.prototype.hasOwnProperty.call(map, entry.code)) {
-      map[entry.code] = entry.command;
-    }
-  }
-  return map;
-}
-function buildRemediationCommands(warnings) {
-  return Object.values(buildRemediationMap(warnings));
-}
-
-export {
-  buildRemediationMap,
-  buildRemediationCommands
-};
-//# sourceMappingURL=chunk-JINYH2DB.js.map

package/dist/cli-bundle/chunks/chunk-JINYH2DB.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../../../../../../core/diagnostics/remediation.ts"],
-  "sourcesContent": ["/**\n * Shared machine-executable remediation registry.\n *\n * `pm health` and `pm validate` both emit stable, colon-delimited warning tokens\n * (for example `history_drift_missing_stream:pm-abcd` or\n * `validate_resolution_missing_fields:3`). Agents that gate on these commands\n * previously had to hardcode the mapping from a warning code to the `pm` command\n * that fixes it. This module is the single source of truth for that mapping so\n * `pm health --json` (per-check `remediation_map`) and `pm validate --fix-hints`\n * (per-check `fix_hints`) can both surface executable remediation without any\n * duplicated, drift-prone lookup tables.\n *\n * Semantics of {@link RemediationEntry.command}: the suggested next `pm` command\n * an operator/agent should run to resolve findings with that code. Per-item\n * findings use an `<id>` placeholder (callers that have the concrete id may\n * substitute it); findings whose only fix is a manual file edit point at the\n * most useful diagnostic/repair command and describe the manual step in\n * {@link RemediationEntry.summary}.\n */\n\n/** Maps a stable diagnostic warning code to the command and summary that resolve it. */\nexport interface RemediationEntry {\n  /**\n   * Stable warning-code prefix this entry resolves. A warning matches when it\n   * equals this code or begins with `<code>:`. Registry codes are mutually\n   * exclusive under that colon-boundary rule (no code is a `:`-delimited prefix\n   * of another — e.g. `settings:id_prefix_empty` is distinct from a bare\n   * `settings`, which is intentionally not registered), so `resolveRemediation`\n   * uses first-match with no ordering dependency.\n   */\n  readonly code: string;\n  /** Executable `pm` command (or imperative) that resolves the finding. May contain an `<id>` placeholder. */\n  readonly command: string;\n  /** One-line description of what the command does / which manual step it covers. */\n  readonly summary: string;\n}\n\n/**\n * Registry of every non-extension `pm health` / `pm validate` warning code and\n * its remediation. Extension findings keep their richer, contextual\n * `details.triage.remediation` produced by the extension health triage and are\n * intentionally excluded here (see pm-0hnu: \"all non-extension checks\").\n */\nexport const REMEDIATION_REGISTRY: readonly RemediationEntry[] = Object.freeze([\n  // --- pm health: directories ---\n  {\n    code: \"missing_directory\",\n    command: \"pm init\",\n    summary: \"Recreate missing tracker directories (pm init is idempotent and restores the scaffold).\",\n  },\n  // --- pm health: settings (read/parse) ---\n  {\n    code: \"settings_read_invalid_json\",\n    command: \"pm config list --json\",\n    summary:\n      \"settings.json is not valid JSON and pm fell back to defaults; fix the syntax error in the reported path, then re-run.\",\n  },\n  {\n    code: \"settings_read_invalid_schema\",\n    command: \"pm config list --json\",\n    summary:\n      \"settings.json failed schema validation and pm fell back to defaults; correct the reported key in the file, then re-run.\",\n  },\n  {\n    code: \"settings_read_merge_failed\",\n    command: \"pm config list --json\",\n    summary: \"Global/project settings could not be merged; reconcile the conflicting keys in the reported settings files.\",\n  },\n  // --- pm health: settings_values ---\n  {\n    code: \"settings:id_prefix_empty\",\n    command: \"pm config list --json\",\n    summary: 'id_prefix is empty; set a non-empty \"id_prefix\" in settings.json so generated item ids are well-formed.',\n  },\n  {\n    code: \"settings:locks_ttl_non_positive\",\n    command: \"pm config list --json\",\n    summary: 'locks.ttl_seconds must be positive; set a positive \"locks.ttl_seconds\" in settings.json.',\n  },\n  // --- pm health: telemetry (advisory) ---\n  {\n    code: \"telemetry_state_invalid_json\",\n    command: \"pm health --check-telemetry\",\n    summary: \"Local telemetry state file is corrupt; pm recreates it on the next flush. Advisory only.\",\n  },\n  {\n    code: \"telemetry_queue_invalid_rows\",\n    command: \"pm health --check-telemetry\",\n    summary: \"The telemetry queue has unparseable rows; they are skipped on the next flush. Advisory only.\",\n  },\n  {\n    code: \"telemetry_queue_pending\",\n    command: \"pm health --check-telemetry\",\n    summary: \"Telemetry events are queued; they flush automatically on the next reachable command. Advisory only.\",\n  },\n  {\n    code: \"telemetry_queue_high_retries\",\n    command: \"pm telemetry flush\",\n    summary:\n      \"Some queued telemetry events are near retry exhaustion; flush now and verify endpoint reachability before entries are dropped.\",\n  },\n  {\n    code: \"telemetry_endpoint_probe_failed\",\n    command: \"pm health --check-telemetry\",\n    summary: \"The telemetry endpoint is unreachable; events stay queued until it recovers. Advisory only.\",\n  },\n  {\n    code: \"telemetry_endpoint_probe_http_status\",\n    command: \"pm health --check-telemetry\",\n    summary: \"The telemetry endpoint returned a non-success status; events stay queued until it recovers. Advisory only.\",\n  },\n  {\n    code: \"telemetry_schema_version_behind\",\n    command: \"pm health --check-telemetry\",\n    summary: \"Client schema is behind server; upgrade pm-cli to emit the latest event shape.\",\n  },\n  {\n    code: \"telemetry_otel_export_failing\",\n    command: \"pm health --check-telemetry\",\n    summary:\n      \"OTLP trace spans are queued but the traces endpoint export is failing; spans retry automatically on the next reachable command, or set PM_TELEMETRY_OTEL_DISABLED=1 to skip OTLP export. Advisory only.\",\n  },\n  // --- pm health: integrity ---\n  {\n    code: \"integrity_item_unreadable\",\n    command: \"pm validate --check-files --verbose-diagnostics\",\n    summary: \"An item file could not be read; restore or repair the file at the reported path.\",\n  },\n  {\n    code: \"integrity_item_parse_failed\",\n    command: \"pm validate --check-files --verbose-diagnostics\",\n    summary: \"An item file failed to parse; fix the malformed front matter at the reported path.\",\n  },\n  {\n    code: \"integrity_item_conflict_marker\",\n    command: \"pm validate --check-files --verbose-diagnostics\",\n    summary: \"An item file contains Git conflict markers; resolve the <<<<<<< / >>>>>>> markers at the reported line.\",\n  },\n  {\n    code: \"integrity_history_unreadable\",\n    command: \"pm history-repair <id>\",\n    summary: \"A history stream could not be read; re-anchor the affected item's history chain.\",\n  },\n  {\n    code: \"integrity_history_invalid_json\",\n    command: \"pm history-repair <id>\",\n    summary: \"A history stream contains invalid JSON; re-anchor the affected item's history chain.\",\n  },\n  {\n    code: \"integrity_history_conflict_marker\",\n    command: \"pm history-repair <id>\",\n    summary: \"A history stream contains Git conflict markers; resolve the markers, then re-anchor the chain.\",\n  },\n  // --- pm health (integrity) + pm validate (format_version): item format version ---\n  {\n    code: \"integrity_item_outdated_format_version\",\n    command: \"pm validate --verbose-diagnostics\",\n    summary: \"An item predates the current storage format version; a pm storage migration rewrites it. Use --verbose-diagnostics to list the affected items.\",\n  },\n  {\n    code: \"integrity_item_ahead_format_version\",\n    command: \"npm install -g @unbrained/pm-cli@latest\",\n    summary: \"An item was written by a newer pm format version than this runtime supports; upgrade pm to read and validate it safely.\",\n  },\n  // --- pm health: history_drift ---\n  // `pm health` rewrites these commands to `pm history-repair --all` in the\n  // per-check remediation_map when more than one stream is drifted.\n  {\n    code: \"history_drift_missing_stream\",\n    command: \"pm history-repair <id>\",\n    summary: \"The item has no history stream; re-anchor the chain to rebuild it (pm history-repair --all repairs every drifted stream in one pass).\",\n  },\n  {\n    code: \"history_drift_unreadable_stream\",\n    command: \"pm history-repair <id>\",\n    summary: \"The item's history stream is unreadable; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass).\",\n  },\n  {\n    code: \"history_drift_hash_mismatch\",\n    command: \"pm history-repair <id>\",\n    summary: \"The item's content hash no longer matches its history; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass).\",\n  },\n  {\n    code: \"history_drift_chain_mismatch\",\n    command: \"pm history-repair <id>\",\n    summary: \"The item's history chain is broken; re-anchor the chain (pm history-repair --all repairs every drifted stream in one pass).\",\n  },\n  // --- pm health: storage (history compaction policy) ---\n  {\n    code: \"history_stream_over_compact_threshold\",\n    command: \"pm history-compact <id>\",\n    summary: \"The history stream exceeds the configured compaction threshold; compact it (pm history-compact --all-streams sweeps every over-threshold stream in one pass).\",\n  },\n  // --- pm health: locks ---\n  {\n    code: \"locks_stale_count\",\n    command: \"pm gc --scope locks\",\n    summary:\n      \"Stale item-claim locks (embedded ttl elapsed) can block mutations; sweep them — gc retains active and unparseable locks.\",\n  },\n  {\n    code: \"locks_unreadable\",\n    command: \"pm gc --scope locks --dry-run\",\n    summary:\n      \"Some lock files could not be read; preview the sweep and inspect the unreadable files manually — gc never deletes what it cannot read.\",\n  },\n  // --- pm health: extensions ---\n  // Most extension findings keep their richer, contextual\n  // `details.triage.remediation` and are intentionally absent here. The\n  // partial-coverage code is the exception: it is not a per-extension triage\n  // result but a system-wide adoption gap (unmanaged installs the update-health\n  // scan had to skip), so it has a single deterministic fix and belongs in the\n  // shared registry like any other health finding (pm-bdvm).\n  {\n    code: \"extension_update_health_partial_coverage\",\n    command: \"pm extension --adopt-all --project\",\n    summary:\n      \"Update-health coverage is partial because unmanaged extensions were skipped; adopt the existing installs into managed metadata so the update scan covers them (use --global for global-scope extensions, or pm package --adopt-all when working with packages).\",\n  },\n  // --- pm health: vectorization ---\n  {\n    code: \"vectorization_stale_items_remaining\",\n    command: \"pm health --refresh-vectors\",\n    summary: \"Some items have stale embeddings; refresh vectors so semantic search results stay current.\",\n  },\n  {\n    code: \"vectorization_embedding_identity_changed\",\n    command: \"pm reindex --mode semantic\",\n    summary: \"Embedding provider/model changed since the last index; run a semantic reindex to rebuild vectors.\",\n  },\n  // --- pm validate: metadata ---\n  // Note: validate_metadata_missing_author has no entry on purpose. `pm update\n  // --author` sets the mutation/audit author (history), not the item's\n  // `metadata.author` front-matter field, and there is no CLI flag that writes\n  // that field — so emitting a command here would record an audit entry without\n  // clearing the finding. A missing item author must be restored at the source.\n  {\n    code: \"validate_metadata_missing_acceptance_criteria\",\n    command: 'pm update <id> --acceptance-criteria \"<criteria>\"',\n    summary: \"Backfill the missing acceptance criteria on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_estimate\",\n    command: 'pm update <id> --estimate \"<estimate>\"',\n    summary: \"Backfill the missing estimate on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_close_reason\",\n    command: 'pm update <id> --close-reason \"<reason>\"',\n    summary: \"Backfill the missing close reason on the reported closed item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_reviewer\",\n    command: 'pm update <id> --reviewer \"<name>\"',\n    summary: \"Backfill the missing reviewer on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_risk\",\n    command: 'pm update <id> --risk \"<level>\"',\n    summary: \"Backfill the missing risk on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_confidence\",\n    command: 'pm update <id> --confidence \"<level>\"',\n    summary: \"Backfill the missing confidence on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_sprint\",\n    command: 'pm update <id> --sprint \"<sprint>\"',\n    summary: \"Backfill the missing sprint on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_missing_release\",\n    command: 'pm update <id> --release \"<release>\"',\n    summary: \"Backfill the missing release on the reported item(s).\",\n  },\n  {\n    code: \"validate_metadata_custom_profile_missing_required_fields\",\n    command: 'pm config set metadata-required-fields --criterion \"<field>\"',\n    summary:\n      \"Config-driven finding: the custom metadata profile has no required fields configured and falls back to core, so configure the fields rather than mutating items.\",\n  },\n  {\n    code: \"validate_metadata_duplicate_issue_codes\",\n    command: 'pm update <id> --title \"<distinct title>\"',\n    summary:\n      \"Two or more items share one logical issue code (GH-235); give each a distinct title so the derived code is unique, or close the redundant item with pm close <id> --duplicate-of <canonical-id> (closed-as-duplicate items are excluded from the check).\",\n  },\n  // --- pm validate: resolution ---\n  {\n    code: \"validate_resolution_missing_fields\",\n    command: 'pm update <id> --resolution \"<how resolved>\"',\n    summary: \"Backfill resolution / expected_result / actual_result on the reported closed item(s).\",\n  },\n  // --- pm validate: lifecycle ---\n  {\n    code: \"validate_lifecycle_active_closure_like_metadata\",\n    command: \"pm update <id> --unset <closure-like-field>\",\n    summary:\n      \"Clear the closure-like field the validator flags on this active item — the detail row names it (resolution / actual-result / blocked-reason) — or close the item if it is actually done.\",\n  },\n  {\n    code: \"validate_lifecycle_active_terminal_parent\",\n    command: \"pm update <id> --parent <active-parent-id>\",\n    summary: \"Reopen the terminal parent or move the active child under a non-terminal parent.\",\n  },\n  {\n    code: \"validate_lifecycle_stale_blockers\",\n    command: \"pm update <id> --unset blocked-by --unset blocked-reason\",\n    summary:\n      \"Resolve the stale blocker the validator flags: clear blocked-by/blocked-reason when they linger on a non-blocked item or report a resolved blocker; if instead a blocked item is missing blocker context, add the context or move it out of a blocked status.\",\n  },\n  {\n    code: \"validate_lifecycle_dependency_cycles_error\",\n    command: \"pm update <id> --dep-remove <dep-id>\",\n    summary: \"Break the dependency cycle by removing one edge from the reported cycle.\",\n  },\n  {\n    code: \"validate_lifecycle_dependency_cycles\",\n    command: \"pm update <id> --dep-remove <dep-id>\",\n    summary: \"Break the dependency cycle by removing one edge from the reported cycle.\",\n  },\n  {\n    code: \"validate_hierarchy_parent_cycle_error\",\n    command: \"pm update <id> --parent <other-id>\",\n    summary:\n      \"Break the parent-hierarchy cycle by reparenting one item in the reported cycle to a non-cyclic parent (or clear it with pm update <id> --unset parent).\",\n  },\n  {\n    code: \"validate_hierarchy_parent_cycle\",\n    command: \"pm update <id> --parent <other-id>\",\n    summary:\n      \"Break the parent-hierarchy cycle by reparenting one item in the reported cycle to a non-cyclic parent (or clear it with pm update <id> --unset parent).\",\n  },\n  // --- pm validate: files ---\n  {\n    code: \"validate_files_missing_linked_paths\",\n    command: \"pm <files|docs> <id> --remove <path>\",\n    summary:\n      \"The check spans both item.files and item.docs under one code: restore the missing linked artifact, or unlink it with pm files (linked file) or pm docs (linked doc).\",\n  },\n  {\n    code: \"validate_files_orphaned_paths\",\n    command: \"pm <files|docs> <id> --add <path>\",\n    summary:\n      \"Link the orphaned artifact with pm files (file) or pm docs (doc), or remove it from the workspace.\",\n  },\n  {\n    code: \"validate_files_tracked_all_strict_forces_pm_internals\",\n    command: \"pm validate --check-files --include-pm-internals\",\n    summary: \"tracked-all-strict scan flagged pm internals; re-run with --include-pm-internals or a softer --scan-mode.\",\n  },\n  // --- pm validate: history_drift ---\n  {\n    code: \"validate_history_drift_missing_streams\",\n    command: \"pm history-repair <id>\",\n    summary: \"Re-anchor the history chains of the items missing a history stream.\",\n  },\n  {\n    code: \"validate_history_drift_unreadable_streams\",\n    command: \"pm history-repair <id>\",\n    summary: \"Re-anchor the history chains of the items with an unreadable history stream.\",\n  },\n  {\n    code: \"validate_history_drift_hash_mismatches\",\n    command: \"pm history-repair <id>\",\n    summary: \"Re-anchor the history chains of the items whose content hash drifted.\",\n  },\n  {\n    code: \"validate_history_drift_chain_mismatches\",\n    command: \"pm history-repair <id>\",\n    summary: \"Re-anchor the history chains of the items with a broken history chain.\",\n  },\n  // --- pm validate: command_references ---\n  {\n    code: \"validate_command_references_stale_pm_ids\",\n    command: 'pm update <id> --replace-tests --test \"command=<corrected-command>\" [--test ...]',\n    summary:\n      \"Correct the stale pm-ID inside the item's linked test command (the check scans tests[].command, not the body). --replace-tests overwrites the entire tests list, so re-include the item's other linked tests in the same call.\",\n  },\n  {\n    code: \"validate_format_version_outdated_items\",\n    command: \"pm validate --verbose-diagnostics\",\n    summary: \"One or more items predate the current storage format version; a pm storage migration rewrites them. Use --verbose-diagnostics to list the affected items.\",\n  },\n  {\n    code: \"validate_format_version_ahead_items\",\n    command: \"npm install -g @unbrained/pm-cli@latest\",\n    summary: \"One or more items were written by a newer pm format version than this runtime supports; upgrade pm to read and validate them safely.\",\n  },\n]);\n\n/**\n * Resolve the remediation entry for a warning token, or `undefined` when no\n * entry is registered. A warning matches an entry when it equals the entry code\n * or begins with `<code>:` (the colon boundary keeps sibling codes such as\n * `validate_lifecycle_dependency_cycles` and\n * `validate_lifecycle_dependency_cycles_error` disjoint).\n *\n * First match is intentional and correct: registry codes are mutually exclusive\n * under the colon-boundary rule, so at most one entry can ever match a warning\n * and order is irrelevant. That invariant is enforced by a test (see\n * remediation-registry.spec.ts \"keeps every registry code mutually exclusive\"),\n * which is why this stays a simple linear scan rather than a longest-prefix\n * search — a longest-prefix tie-break is unreachable with disjoint codes.\n *\n * Accepts unknown input defensively (this is an exported helper SDK consumers\n * may call from untyped JS): a non-string `warning` resolves to `undefined`.\n */\nexport function resolveRemediation(warning: string): RemediationEntry | undefined {\n  if (typeof warning !== \"string\") {\n    return undefined;\n  }\n  const normalized = warning.trim();\n  for (const entry of REMEDIATION_REGISTRY) {\n    if (normalized === entry.code || normalized.startsWith(`${entry.code}:`)) {\n      return entry;\n    }\n  }\n  return undefined;\n}\n\n/**\n * Build a compact `remediation_map` (code -> command) for a set of warning\n * tokens. First match wins per code; unknown codes are skipped. Used by\n * `pm health --json` per-check details and as the source of deduped executable\n * commands for `pm validate --fix-hints`.\n */\nexport function buildRemediationMap(warnings: Iterable<string>): Record<string, string> {\n  const map: Record<string, string> = {};\n  for (const warning of warnings) {\n    const entry = resolveRemediation(warning);\n    if (entry !== undefined && !Object.prototype.hasOwnProperty.call(map, entry.code)) {\n      map[entry.code] = entry.command;\n    }\n  }\n  return map;\n}\n\n/**\n * Build a deduped, ordered list of executable remediation commands for a set of\n * warning tokens (one command per distinct matched code). Used by\n * `pm validate --fix-hints` for checks that do not already emit per-row\n * remediation commands.\n */\nexport function buildRemediationCommands(warnings: Iterable<string>): string[] {\n  return Object.values(buildRemediationMap(warnings));\n}\n"],
-  "mappings": ";;;;;;;;AA2CO,IAAM,uBAAoD,OAAO,OAAO;;EAE7E;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SACE;;;EAGJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;;;EAKX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;;;;;;;;EASJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;;EAGJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;;;;;;EAQX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;;EAGJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;;EAGJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;;EAGX;IACE,MAAM;IACN,SAAS;IACT,SACE;;EAEJ;IACE,MAAM;IACN,SAAS;IACT,SAAS;;EAEX;IACE,MAAM;IACN,SAAS;IACT,SAAS;;CAEZ;AAmBK,SAAU,mBAAmB,SAAe;AAChD,MAAI,OAAO,YAAY,UAAU;AAC/B,WAAO;EACT;AACA,QAAM,aAAa,QAAQ,KAAI;AAC/B,aAAW,SAAS,sBAAsB;AACxC,QAAI,eAAe,MAAM,QAAQ,WAAW,WAAW,GAAG,MAAM,IAAI,GAAG,GAAG;AACxE,aAAO;IACT;EACF;AACA,SAAO;AACT;AAQM,SAAU,oBAAoB,UAA0B;AAC5D,QAAM,MAA8B,CAAA;AACpC,aAAW,WAAW,UAAU;AAC9B,UAAM,QAAQ,mBAAmB,OAAO;AACxC,QAAI,UAAU,UAAa,CAAC,OAAO,UAAU,eAAe,KAAK,KAAK,MAAM,IAAI,GAAG;AACjF,UAAI,MAAM,IAAI,IAAI,MAAM;IAC1B;EACF;AACA,SAAO;AACT;AAQM,SAAU,yBAAyB,UAA0B;AACjE,SAAO,OAAO,OAAO,oBAAoB,QAAQ,CAAC;AACpD;",
-  "names": []
-}