@peernova/cuneiform-sf 1.0.2 → 1.0.4-beta.8

package/oclif.manifest.json

@@ -1,11 +1,18 @@
 {
   "commands": {
-    "cuneiform:about": {
+    "cuneiform:profile": {
       "aliases": [],
       "args": {},
-      "description": "More information about a command. Don't repeat the summary.",
+      "description": "Profiling is the moment where KYCD moves from planning to evidence. Before profiling, definitions are plans — field lists, filters, and scoping decisions. After profiling, they have results: field population rates, value distributions, null percentages, default detection, and usage patterns across every profiled object.\n\nThe command operates as a fire-and-forget execution engine — it creates profiling requests in the processing queue and returns immediately. Results appear in the org as summaries complete, typically within minutes depending on object size and field count. Definitions are managed with the `definition` commands; results are reviewed through summaries.\n\nTWO MODES:\n\n**Single mode** — Profile one definition:\n\n- `--keys PD-0001` — profile by definition key\n- `--id a0Bxx000000001AAAA` — profile by Salesforce record ID\n\nSingle mode displays definition key, object name, status, request ID, duration, and error details.\n\n**Bulk mode** — Profile multiple definitions with parallel execution:\n\n- `--method metadata` — profile all definitions of a method type (metadata, historical, or comparative)\n- Add filters: --status, --namespace, --category, --time-category, --segment-category, --limit\n- Control concurrency: --parallel (1-10 threads, default: 5)\n\nBulk mode displays a configuration summary, a results table, a profiling summary (Successful/Failed/Skipped/Total), and resolution guidance for failures.\n\nObjects with zero records are automatically skipped (--skip-empty defaults to true), preventing wasted API calls. Failed definitions are reported with resolution guidance that provides actionable next steps.\n\nPREREQUISITE: Definitions must exist before profiling. Create them with `sf cuneiform definition create`.\n\nWHEN TO USE:\n\n- After creating definitions — turn scoping work into analytical evidence\n- To refresh profiling results — re-run profiling on existing definitions for updated data\n- For bulk assessment — sweep all metadata definitions in a single parallel command\n- To re-profile after errors — fix the underlying issue, then re-run the failed definitions\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"profile the Account definition\" → --keys PD-0001\n\"profile all metadata definitions\" → --method metadata\n\"profile everything that hasn't been profiled\" → --method metadata --status \"NOT PROFILED\"\n\"profile only FSC objects\" → --method metadata --namespace FinServ\n\"profile with less concurrency\" → --method metadata --parallel 1\n\nCOMMAND SEQUENCE:\n`definition create` or `definition update` → **`profile`** → `profile request list` → `definition get` (view results)",
       "examples": [
-        "<%= config.bin %> <%= command.id %>"
+        "Profile a single definition by key:\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001",
+        "Profile a single definition by Salesforce record ID:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a0Bxx000000001AAAA",
+        "Sweep all metadata definitions with parallel execution:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method metadata",
+        "Profile only definitions that have never been profiled:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method historical --status \"NOT PROFILED\"",
+        "Profile only Financial Services Cloud objects:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method metadata --namespace FinServ",
+        "Maximize throughput with full parallelism:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method comparative --parallel 10",
+        "Profile a small batch for testing:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method metadata --limit 5",
+        "Minimize API impact with single-threaded execution:\n<%= config.bin %> <%= command.id %> --target-org myOrg --method metadata --parallel 1"
       ],
       "flags": {
         "json": {
@@ -23,46 +30,193 @@
           "multiple": false,
           "type": "option"
         },
-        "name": {
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Authenticate and execute profiling against this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "keys": {
+          "aliases": [
+            "key"
+          ],
+          "char": "k",
+          "deprecateAliases": true,
+          "exclusive": [
+            "id",
+            "method"
+          ],
+          "name": "keys",
+          "summary": "Profile one or more definitions by key (e.g., --keys PD-0001). Find keys with `definition list`. Mutually exclusive with --id and --method.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "id": {
+          "exclusive": [
+            "keys",
+            "method"
+          ],
+          "name": "id",
+          "summary": "Profile a single definition by its Salesforce record ID (e.g., --id a0Bxx000000001AAAA). Use when you have the record ID from the Salesforce UI or API. Mutually exclusive with --keys and --method.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "method": {
+          "aliases": [
+            "type"
+          ],
+          "char": "t",
+          "deprecateAliases": true,
+          "exclusive": [
+            "keys",
+            "id"
+          ],
+          "name": "method",
+          "summary": "Profile all definitions matching a method type: metadata (field-level analysis), historical (time-series trends), or comparative (segment comparison). Activates bulk mode with parallel execution. Mutually exclusive with --keys and --id.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "metadata",
+            "historical",
+            "comparative"
+          ],
+          "type": "option"
+        },
+        "status": {
+          "char": "s",
+          "name": "status",
+          "summary": "Filter definitions by profiling status before executing (e.g., --status \"NOT PROFILED\" for first-time profiling, --status \"ERROR\" to retry failures). Applies only in bulk mode with --method.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "NOT PROFILED",
+            "IN PROGRESS",
+            "SUCCESS",
+            "COMPLETE w/ FAILURES",
+            "ERROR"
+          ],
+          "type": "option"
+        },
+        "namespace": {
           "char": "n",
-          "description": "More information about a flag. Don't repeat the summary.",
-          "name": "name",
-          "required": false,
-          "summary": "Description of a flag.",
+          "name": "namespace",
+          "summary": "Filter definitions by the namespace prefix of their target object (e.g., \"FinServ\" for Financial Services Cloud, \"SBQQ\" for CPQ). Profiles only definitions targeting objects from a specific managed package.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "category": {
+          "char": "c",
+          "name": "category",
+          "summary": "Filter definitions by category label (e.g., \"Baseline\", \"Phase 1\"). Combine with --time-category and --segment-category to target definitions across all three category dimensions.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "time-category": {
+          "name": "time-category",
+          "summary": "Filter definitions by time category (e.g., \"Lifetime\", \"2026 vs 2025\", \"This Year\"). Combine with --category and --segment-category to target time-scoped definitions.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "segment-category": {
+          "name": "segment-category",
+          "summary": "Filter definitions by segment category (e.g., \"Historical\", \"Comparative\", \"Enterprise Sales\", \"Won vs Lost\"). Combine with --category and --time-category to target specific comparison segments.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Cap the number of definitions processed in bulk mode (e.g., --limit 10 to profile a small batch for testing). Controls the maximum definitions per run.",
+          "default": 50,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "skip-empty": {
+          "name": "skip-empty",
+          "summary": "Automatically skip definitions targeting objects with zero records (default: true). Optimizes API usage by focusing execution on populated objects. Use --no-skip-empty to include all definitions regardless of record count.",
+          "allowNo": true,
+          "type": "boolean"
+        },
+        "parallel": {
+          "name": "parallel",
+          "summary": "Set the number of parallel concurrent operations for bulk mode (1-10, default: 5). Lower values reduce API consumption; higher values increase throughput when the org has API capacity.",
+          "default": 5,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "format": {
+          "name": "format",
+          "summary": "Control the output format: table (default, human-readable with progress and summary boxes) or json (machine-readable for scripting and automation).",
+          "default": "table",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "table",
+            "json"
+          ],
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "cuneiform:about",
+      "id": "cuneiform:profile",
       "pluginAlias": "@peernova/cuneiform-sf",
       "pluginName": "@peernova/cuneiform-sf",
       "pluginType": "core",
       "strict": true,
-      "summary": "Summary of a command.",
+      "summary": "Execute profiling definitions against a Salesforce org to generate field-level, value-level, and KPI-level evidence about data population and usage patterns.",
       "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "PROFILE_NO_SELECTION": "errors.noSelection",
+        "PROFILE_INVALID_SELECTION": "errors.invalidSelection",
+        "PROFILE_INVALID_ID": "errors.invalidId",
+        "PROFILE_DEFINITION_NOT_FOUND": "errors.definitionNotFound",
+        "PROFILE_INVALID_PARALLEL": "errors.invalidParallel",
+        "PROFILE_QUERY_FAILED": "errors.queryFailed",
+        "PROFILE_NO_DEFINITIONS_FOUND": "errors.noDefinitionsFound",
+        "PROFILE_EXECUTION_FAILED": "errors.executionFailed"
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "cuneiform",
-        "about.js"
+        "profile.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "cuneiform:about",
-        "about:cuneiform"
+        "cuneiform:profile",
+        "profile:cuneiform"
       ]
     },
-    "hello:world": {
+    "cuneiform:compatibility:check": {
       "aliases": [],
       "args": {},
-      "description": "Say hello either to the world or someone you know.",
+      "description": "Reports the Cuneiform For Salesforce managed-package version this CLI release was tested against. Without `--target-org`, the command is a local-only readout — no Salesforce API calls, no authentication required.\n\nWhen `--target-org` is supplied, the command queries the org for the installed Cuneiform For Salesforce package via the Tooling API and reports one of five states:\n\n- `installed-match` — installed version satisfies the requirement (exit 0)\n- `installed-newer` — installed version is newer than required (exit 0, advisory)\n- `installed-version-unknown` — Cuneiform is detected via namespace but the version is not exposed (typical for source-pushed scratch orgs — CLI-1569). Compatibility cannot be verified, but the package is present (exit 0, advisory)\n- `installed-older` — installed version is older than required (exit 1)\n- `not-installed` — Cuneiform For Salesforce is not installed in this org (exit 1)\n\nUse this command to:\n\n- Confirm a scratch org or sandbox is ready for CLI operations after a fresh package install\n- Diagnose CLI errors that look like data-shape mismatches but are version-compatibility issues\n- Pin CLI/app version pairs in CI before running profiling jobs",
       "examples": [
-        "Say hello to the world:\n<%= config.bin %> <%= command.id %>",
-        "Say hello to someone you know:\n<%= config.bin %> <%= command.id %> --name Astro"
+        "Print the required app version (no auth, no API calls):\n<%= config.bin %> <%= command.id %>",
+        "Verify the installed version in a target org:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Machine-readable output for CI:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
       ],
       "flags": {
         "json": {
@@ -80,39 +234,2667 @@
           "multiple": false,
           "type": "option"
         },
-        "name": {
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "summary": "Target org username or alias. When supplied, the command queries the org's installed Cuneiform For Salesforce version and reports compatibility.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "char": "a",
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "summary": "API version to use when querying the target org. Defaults to the org's maximum supported version.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:compatibility:check",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Verify the Cuneiform For Salesforce app version required by this CLI build, and (optionally) the version installed in a target org.",
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "compatibility",
+        "check.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:compatibility:check",
+        "compatibility:cuneiform:check",
+        "compatibility:check:cuneiform",
+        "cuneiform:check:compatibility",
+        "check:cuneiform:compatibility",
+        "check:compatibility:cuneiform"
+      ]
+    },
+    "cuneiform:definition:create": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling definitions are the blueprint that tells Cuneiform what to analyze. Each definition specifies an object, a profiling method, and a time scope. This command translates your intent — expressed through flags for method selection, object filtering, and time windowing — into structured definition records in the target org.\n\nThe command executes in two phases. Phase 1 discovers and validates objects, builds a preview table showing each object with its record count, profiling type, category, time category, and segment category, then prompts for confirmation. Phase 2 creates definitions sequentially, reporting progress via spinner updates. Output includes separate Created and Skipped tables, a summary box (Objects/Created/Skipped/Failed), and optional post-creation actions: trigger immediate profiling, open the first definition in Salesforce Lightning, or write session data to a local log directory.\n\nPREREQUISITES: Run `sf cuneiform user details --configure` to verify permissions. Objects must exist in the target org.\n\nCHOOSING A PROFILING METHOD (--method):\n\n- metadata — Catalogs field structure and configuration. No record scanning. Fast. No time dimension.\n- historical — Full record-level data profiling with year-based time windows. Captures how field population changes over time.\n- comparative — Year-over-year comparison: compares current-period records (SetA) against prior-period records (SetB). Requires --year or --date-literal.\n- recordtype — Per-record-type analysis across 6 time windows. Segments data by business process stage (e.g., New Business vs Renewal).\n- outcome — Boolean outcome comparison: Won vs Lost for Opportunity, Closed vs Open for Case, Converted vs Unconverted for Lead. Surfaces data quality gaps between business outcomes.\n- full — All five methods combined. Comprehensive first-time profiling of a new org. Default.\n\nSCOPING OBJECTS:\n\n- --objects Account,Contact — Profile specific named objects (comma-separated or repeated)\n- --filter custom — All custom objects; --filter standard — All standard objects\n- --with-records — Only objects that have at least one record (recommended for historical/comparative)\n- --min-records 100 — Only objects with 100+ records\n- --namespace SBQQ — Only objects from a specific managed package (e.g., SBQQ for CPQ, FinServ for FSC)\n- --pattern Account\\* — Objects matching a wildcard pattern\n\nROLLING TIME WINDOWS (use with --method comparative, historical, recordtype, or full):\n\n- --date-literal THIS_YEAR — Profile the current year's records\n- --date-literal THIS_QUARTER — Profile the current quarter\n- --date-literal THIS_MONTH — Profile the current month\n- --depth 3 — With a date literal, creates 3 cascading periods: this period, last period, and two periods ago\n- --depth 2 --date-literal THIS_QUARTER — Creates definitions for this quarter AND last quarter\n- --year 2026 — Use a specific year instead of a date literal; --depth controls how many prior years to include\n- --date-field LastModifiedDate — Use LastModifiedDate instead of CreatedDate for time filtering\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\n- \"compare X from 2025 vs 2026\" → --method comparative --year 2026\n- \"rolling quarterly analysis\" → --method comparative --date-literal THIS_QUARTER --depth N\n- \"year-over-year trends\" → --method comparative\n- \"by business stage / record type\" → --method recordtype\n- \"won vs lost / closed vs open\" → --method outcome\n- \"field-level stats only\" → --method metadata\n- \"objects with data\" → --with-records\n- \"FSC objects\" → --namespace FinServ\n- \"CPQ objects\" → --namespace SBQQ\n- \"last N months\" → --date-literal LAST_MONTH --depth N\n- \"this fiscal year\" → --date-literal THIS_FISCAL_YEAR\n\nCOMMAND SEQUENCE: `user details --configure` (verify permissions) → `object describe` (understand structure) → `definition create` (build definitions) → `profile` (execute profiling)\n\nSAFETY: Objects that already have definitions are skipped automatically (no duplicates). A confirmation prompt appears before creation. Use --dry-run to preview without creating.",
+      "examples": [
+        "Create definitions for a single object using all profiling methods:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account",
+        "Preview what would be created before committing (recommended before batch runs):\n<%= config.bin %> <%= command.id %> --target-org myOrg --filter custom --with-records --dry-run",
+        "Profile all custom objects with at least 100 records, tagged by engagement phase:\n<%= config.bin %> <%= command.id %> --target-org myOrg --filter custom --with-records --min-records 100 --category \"Phase 1\"",
+        "Isolate Financial Services Cloud objects by namespace:\n<%= config.bin %> <%= command.id %> --target-org myOrg --namespace FinServ --method metadata",
+        "Rolling quarterly trend analysis across the last 4 quarters:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Opportunity --method comparative --date-literal THIS_QUARTER --depth 4",
+        "Lifetime vs last 2 years — show what fraction of all records were created in the recent window:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account,Contact,Opportunity --method comparative --lifetime-primary --date-literal LAST_N_YEARS:2",
+        "Lifetime vs a specific year — compare all records ever against records created in 2024:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Opportunity --method comparative --lifetime-primary --year 2024",
+        "Won vs Lost opportunity analysis to surface data quality gaps between business outcomes:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Opportunity --objects Case --objects Lead --method outcome",
+        "Bulk run with shared, human-readable category labels across every created definition:\n<%= config.bin %> <%= command.id %> --target-org myOrg --filter custom --with-records --time-category \"Q1 2026\" --segment-category \"Pilot Run\""
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Salesforce org where definitions will be created. The command validates Cuneiform installation and permission sets before any API calls.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "objects": {
+          "char": "b",
+          "name": "objects",
+          "summary": "Salesforce object API names to create definitions for (e.g., --objects Account --objects Contact). Repeat the flag for multiple objects. When you know exactly which objects to profile, this is the most direct selection mode. Cannot be combined with --filter when targeting specific objects.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "filter": {
+          "char": "f",
+          "name": "filter",
+          "summary": "Filter objects by Salesforce object type: custom (objects with \\_\\_c suffix), standard (built-in objects like Account, Contact, Opportunity), or all (both). Defaults to all.",
+          "default": "all",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "all",
+            "standard",
+            "custom"
+          ],
+          "type": "option"
+        },
+        "pattern": {
+          "char": "p",
+          "name": "pattern",
+          "summary": "Filter objects by API name pattern using wildcard matching (e.g., Account\\_ matches Account and AccountTeamMember). Use plain text for substring matching (e.g., Account matches any object containing \"Account\"). Targets families of related objects by naming convention.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "namespace": {
           "char": "n",
-          "description": "This person can be anyone in the world!",
-          "name": "name",
-          "summary": "The name of the person you'd like to say hello to.",
-          "default": "World",
+          "name": "namespace",
+          "summary": "Filter objects by managed package namespace prefix to scope profiling to a specific product installation (e.g., --namespace SBQQ for CPQ, --namespace FinServ for Financial Services Cloud, --namespace HealthCloudGA for Health Cloud). Pass an empty string (\"\") to target only unpackaged custom objects. Combines with --filter custom to isolate custom objects from a specific package.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "classification": {
+          "name": "classification",
+          "summary": "Filter by object classification: customer (business-facing objects), internal (system objects), or all. Defaults to all.",
+          "default": "customer",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "customer",
+            "internal",
+            "all"
+          ],
+          "type": "option"
+        },
+        "with-records": {
+          "name": "with-records",
+          "summary": "Include only objects that have at least one record. Avoids creating definitions for empty staging or archive objects. Recommended for historical and comparative profiling where empty objects produce no analytical value. Cannot be combined with --without-records.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "without-records": {
+          "name": "without-records",
+          "summary": "Include only objects that have zero records. Targets empty objects for data completeness analysis or unused schema identification. Cannot be combined with --with-records.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-record-types": {
+          "name": "with-record-types",
+          "summary": "Include only objects that have at least one active record type defined. Use with --method recordtype to ensure targeted objects have record types to segment by.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "category": {
+          "char": "c",
+          "name": "category",
+          "summary": "Label assigned to every definition created in this run (e.g., --category \"Phase 1\" or --category \"Sales Cloud\"). Groups definitions by engagement phase or functional area for later filtering and management. Freeform text.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "min-records": {
+          "name": "min-records",
+          "summary": "Minimum record count an object must have to be included (e.g., --min-records 100 skips objects with fewer than 100 records). Filters out low-volume objects that would produce statistically insignificant profiling results. Defaults to 0 (include all).",
+          "default": 0,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Maximum number of objects to create definitions for (e.g., --limit 20 for a quick demo setup). Constrains scope in large orgs or matches a statement-of-work object count. Objects are selected in the order returned by the Salesforce DescribeGlobal API. When omitted, processes all matching objects.",
+          "default": 100,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "method": {
+          "char": "t",
+          "name": "method",
+          "summary": "Profiling methodology that determines the analytical questions each definition can answer:\nmetadata — Catalogs field structure and configuration. Fast, no record scanning, no time dimension.\nhistorical — Full record-level analysis with year-based time windows. Captures field population changes over time.\ncomparative — Compares current-period records (SetA) vs prior-period records (SetB). Requires --year or --date-literal.\nrecordtype — Per-record-type analysis across 6 time windows. Segments by business process stage (e.g., New Business vs Renewal for Opportunity).\noutcome — Boolean outcome comparison: Won vs Lost (Opportunity), Closed vs Open (Case), Converted vs Unconverted (Lead). Surfaces data quality gaps between business outcomes.\nfull — All five methods combined. Comprehensive first-time profiling of a new org or client engagement. Default.\nDefaults to full.",
+          "default": "full",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "metadata",
+            "historical",
+            "comparative",
+            "recordtype",
+            "outcome",
+            "full"
+          ],
+          "type": "option"
+        },
+        "recordtype": {
+          "name": "recordtype",
+          "summary": "Filter to a specific record type name for record-type-specific profiling (e.g., --recordtype \"New Business\"). Used with --method recordtype or --method full. When omitted, all record types matching --record-type-status are included.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "record-type-status": {
+          "name": "record-type-status",
+          "summary": "Filter record types by activity status: active (default), all (active and inactive), or inactive (only inactive). Used with --method recordtype or --method full.",
+          "default": "active",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "active",
+            "all",
+            "inactive"
+          ],
+          "type": "option"
+        },
+        "year": {
+          "name": "year",
+          "summary": "Anchor year for time-based profiling definitions (e.g., --year 2026). Used with --method comparative, historical, recordtype, or full. Accepts comma-separated years (--year 2026,2025,2024). When combined with --depth, sets the starting year and counts backward (e.g., --year 2026 --depth 3 creates definitions for 2026, 2025, and 2024). Defaults to the current year. Cannot be combined with --date-literal.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "depth": {
+          "name": "depth",
+          "summary": "Number of cascading time periods to create, counting backward from the anchor year or date literal (e.g., --depth 3 with --year 2026 creates definitions for 2026, 2025, and 2024). Use with --date-literal to span periods (e.g., --date-literal THIS_QUARTER --depth 2 creates definitions for this quarter and last quarter). When no anchor year is specified, defaults to the current year. Defaults to 1 for comparative, 3 for full and recordtype. Maximum 10.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "from": {
+          "name": "from",
+          "summary": "Start year of an explicit range (inclusive). Use with --to for a custom year range (e.g., --from 2020 --to 2026). Produces one profiling definition per year in the inclusive range — `objects × (to − from + 1)` total. Cannot be combined with --depth.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "to": {
+          "name": "to",
+          "summary": "End year of an explicit range (inclusive). Use with --from for a custom year range (e.g., --from 2020 --to 2026). Produces one profiling definition per year in the inclusive range — `objects × (to − from + 1)` total. Defaults to the current year when --from is specified.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "no-value-frequency": {
+          "name": "no-value-frequency",
+          "summary": "Skip common value frequency analysis during profiling. Reduces profiling time for objects where frequency distribution data is not needed.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "use-prior": {
+          "name": "use-prior",
+          "summary": "Expand the comparison baseline (SetB) for comparative definitions to include all records created before the anchor year, rather than only the immediately prior year. Shows \"current year vs everything before\" instead of \"current year vs last year\" — useful for demonstrating data quality improvements across the full historical record. Cannot be combined with --date-literal.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "lifetime-primary": {
+          "name": "lifetime-primary",
+          "summary": "Lifetime-vs-X comparative variant: SetA is unfiltered (all records), SetB is the supplied secondary filter. Shows \"all records ever vs records matching the filter\" — useful for highlighting what fraction of the lifetime data falls within a recent window or specific year. Requires --method comparative AND one of (--date-literal, --year, --from/--to). Mutually exclusive with --use-prior, --depth, and non-comparative methods.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "date-literal": {
+          "name": "date-literal",
+          "summary": "Rolling time window for time-scoped profiling — use instead of --year for calendar-relative periods. Combine with --depth to create cascading definitions across multiple periods (e.g., --date-literal THIS_QUARTER --depth 4 creates definitions for the last 4 quarters). Cannot be combined with --year, --from, --to, or --use-prior.\n\nSupported values:\nTODAY, YESTERDAY — Single-day windows\nTHIS_WEEK, LAST_WEEK — Weekly windows\nTHIS_MONTH, LAST_MONTH — Monthly windows (use with --depth for \"last N months\")\nTHIS_QUARTER, LAST_QUARTER — Quarterly windows (use with --depth for \"rolling quarters\")\nTHIS_FISCAL_QUARTER, LAST_FISCAL_QUARTER — Fiscal quarter windows\nTHIS_YEAR, LAST_YEAR — Annual windows\nTHIS_FISCAL_YEAR, LAST_FISCAL_YEAR — Fiscal year windows\nN_YEARS_AGO:2, N_YEARS_AGO:3 — Specific years in the past\nLAST_N_YEARS:2, LAST_N_YEARS:3 — Last N complete years",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "date-field": {
+          "name": "date-field",
+          "summary": "Date field used to assign records to time windows when using --date-literal. Determines which records fall in \"this year\" vs \"last year.\" Defaults to CreatedDate. Use LastModifiedDate to analyze records by when they were last updated rather than when they were created (e.g., --date-field LastModifiedDate to profile recently refreshed data).",
+          "default": "CreatedDate",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "profiled": {
+          "name": "profiled",
+          "summary": "Only create definitions for objects that already have successful metadata profiling results. Builds on prior metadata analysis — run metadata profiling first, review the results, then create historical or comparative definitions for the objects worth deeper analysis. Cannot be combined with --method metadata.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview which definitions would be created without writing any records to the org. The preview table shows the same columns as the creation output: object name, record count, type, category, and time segment. Use before any scoped run to verify the object selection and methodology match your intent.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and create definitions immediately. Use for scripted execution and CI automation workflows.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "profile": {
+          "name": "profile",
+          "summary": "Trigger profiling immediately after definitions are created — equivalent to running `sf cuneiform profile` as a follow-up. Useful for quick single-object setup. For batch runs, create definitions first, review them, then profile separately.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "open": {
+          "name": "open",
+          "summary": "Open the created definition in Salesforce Lightning after creation completes. When multiple definitions are created, opens the first one. Useful for verifying the definition record in the Profiling Definition Wizard.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "logs": {
+          "name": "logs",
+          "summary": "Write session logs to the .cuneiform/logs/ directory for audit and troubleshooting.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "name-prefix": {
+          "name": "name-prefix",
+          "summary": "Prefix prepended to each definition name (e.g., --name-prefix TC-01). Joined with the bullet separator character.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "name-suffix": {
+          "name": "name-suffix",
+          "summary": "Suffix appended to each definition name (e.g., --name-suffix \"Run A\"). Joined with the bullet separator character.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "time-category": {
+          "name": "time-category",
+          "summary": "Verbatim time category applied to every definition created in this run (e.g., --time-category \"Q1 2026\" or --time-category \"Pilot Period\"). Overrides all computed time category values regardless of method, year, or outcome configuration. Useful for grouping definitions across a bulk run with a single shared, human-readable time label.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "segment-category": {
+          "name": "segment-category",
+          "summary": "Verbatim segment category applied to every definition created in this run (e.g., --segment-category \"Pilot Run\" or --segment-category \"Phase 1 Cohort\"). Overrides all computed segment category values regardless of method, record type, or outcome configuration. Useful for grouping definitions across a bulk run with a single shared, human-readable segment label.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "origin": {
+          "name": "origin",
+          "summary": "Origin message appended to auto-generated definition descriptions. Defaults to \"Created via the Cuneiform for Salesforce CLI.\" Pass an empty string to suppress the origin tag.",
+          "default": "Created via the Cuneiform for Salesforce CLI.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "hello:world",
+      "id": "cuneiform:definition:create",
       "pluginAlias": "@peernova/cuneiform-sf",
       "pluginName": "@peernova/cuneiform-sf",
       "pluginType": "core",
       "strict": true,
-      "summary": "Say hello.",
+      "summary": "Build profiling definitions that translate scoping decisions — object selection, filtering, and profiling methodology — into executable configuration records across one or dozens of objects in a single command.",
       "enableJsonFlag": true,
+      "skipAccessGate": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "hello",
-        "world.js"
+        "cuneiform",
+        "definition",
+        "create.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:create",
+        "definition:cuneiform:create",
+        "definition:create:cuneiform",
+        "cuneiform:create:definition",
+        "create:cuneiform:definition",
+        "create:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:export": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling definitions represent hours of scoping work — object selection, method assignment, category classification, field configuration. That configuration exists inside the Salesforce org and a sandbox refresh removes it. This command extracts all profiling definitions and writes them to a self-contained export directory for backup, migration, or version control.\n\nThe export creates a timestamped directory containing three files:\n\n- `export.json` — SFDMU configuration file for round-trip compatibility with `definition import`\n- `pnova__Profiling_Definition__c.csv` — all definition records (fields covering identity, aggregation status, version tracking, profiling configuration, and formula fields)\n- `export-metadata.json` — source org, timestamp, record count, and file manifest\n\nThis command exports OUT of the org. To bring definitions back IN, use `sf cuneiform definition import`.\n\nWHEN TO USE:\n\n- Before a sandbox refresh — preserve definitions so you can restore after the refresh wipes custom data\n- Before a package upgrade — capture the current configuration in case the upgrade affects profiling definitions\n- For cross-org migration — export from sandbox, review the CSV in a spreadsheet, import to production\n- For version control — commit definition exports to Git with `--exclude-ids` for clean diffs between versions\n\nThe `--exclude-ids` flag strips Salesforce-generated IDs (Id, CreatedById, LastModifiedById) from the CSV output. This produces clean diffs between exports — org-specific IDs create false diffs in version control.\n\nRead-only. Does not modify definitions in the org. Fails if the output directory already exists, preventing accidental overwrites of previous exports.",
+      "examples": [
+        "Back up all definitions before a sandbox refresh:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Save to a specific directory within your project structure:\n<%= config.bin %> <%= command.id %> --target-org myOrg --output ./backup/definitions",
+        "Export for Git — strip org-specific IDs so diffs reflect only meaningful configuration changes:\n<%= config.bin %> <%= command.id %> --target-org myOrg --exclude-ids --output ./config/definitions",
+        "Export for cross-org migration — keep IDs for exact restore fidelity in the target org:\n<%= config.bin %> <%= command.id %> --target-org myOrg --output ./migration/source-org",
+        "Output as JSON for scripting, automation pipelines, or downstream tooling:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Export definitions from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "output": {
+          "char": "d",
+          "name": "output",
+          "summary": "Override the default timestamped output directory. Defaults to `./data/exports/definitions/{timestamp}`, creating a unique directory per export. Specify a custom path to organize exports within a project structure (e.g., `--output ./config/definitions`).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "exclude-ids": {
+          "name": "exclude-ids",
+          "summary": "Strip Salesforce-generated IDs (Id, CreatedById, LastModifiedById) from the CSV output. Use this when committing exports to Git — org-specific IDs differ between environments and create false diffs. Keep IDs when exporting for same-org restore fidelity.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:export",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Preserve profiling definitions as portable CSV files before sandbox refreshes, package upgrades, or cross-org migrations — so hours of scoping work are recoverable in seconds.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "export.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:export",
+        "definition:cuneiform:export",
+        "definition:export:cuneiform",
+        "cuneiform:export:definition",
+        "export:cuneiform:definition",
+        "export:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:get": {
+      "aliases": [],
+      "args": {},
+      "description": "Definition keys like PD-0001 appear throughout the Cuneiform workflow — in profiling logs, summary reports, error messages, and colleague questions. When a key surfaces in any context, the next step is resolving what that definition targets, what method it uses, and what state it is in. This command retrieves profiling definitions by key and presents them in a nine-column table: key, name, target object, profiling type, category, time category, segment category, profiling status, and last profiled date.\n\nMultiple keys are fetched in parallel, so looking up 5 definitions is as fast as looking up 1. The output includes an Org Identity header, a definitions table with section header and count, JSON flag guidance with a copy-paste command, and contextual next steps. Keys that do not match any definition produce warnings (not errors), supporting partial success when retrieving batches.\n\n**When to use vs related commands:**\n\n- `definition list` — \"Show me all definitions\" (browse, filter, overview of many)\n- `definition get` — \"Show me PD-0001\" (targeted lookup of specific definitions by key)\n- `definition export` — \"Back up definitions for migration\" (portable CSV export, not inspection)\n\n**File export:** Use `--output-dir` to save each definition as a separate JSON file for audit artifacts, project documentation, or version control.\n\nRead-only. Does not create, modify, or execute definitions. The access gate validates Cuneiform installation and permissions before queries execute.\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\n\"get definition PD-0001\" → --keys PD-0001\n\"get details for Account Standard\" → --keys Account_Standard\n\"show me multiple definitions\" → --keys PD-0001 --keys PD-0002\n\"export definitions to files\" → --keys PD-0001 --output-dir ./definitions\n\"show definition as JSON\" → --keys PD-0001 --json\n\nCOMMAND SEQUENCE: `definition list` (find keys) → `definition get` (inspect by key) → `profile` (execute profiling) or `definition update` (refine configuration)",
+      "examples": [
+        "Resolve a definition key from a profiling log or error message:\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001",
+        "Verify multiple definitions before executing profiling (fetched in parallel):\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001 --keys PD-0002 --keys PD-0003",
+        "Export definitions as JSON files for audit artifacts or project documentation:\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001 --keys PD-0002 --output-dir ./definitions",
+        "Export with descriptive file names for engagement deliverables:\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001 --output-dir ./definitions --file-names account-standard.json",
+        "View the complete definition record in JSON format:\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001 --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Retrieve definitions from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "keys": {
+          "char": "k",
+          "name": "keys",
+          "required": true,
+          "summary": "One or more definition keys to retrieve (e.g., `--keys PD-0001`). Repeat the flag for multiple keys: `--keys PD-0001 --keys PD-0002`. Keys are fetched in parallel for efficient batch lookup.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "output-dir": {
+          "name": "output-dir",
+          "summary": "Save each definition as a separate JSON file in this directory (e.g., `PD-0001.json`). The directory is created if it does not exist. Use this for audit artifacts, project documentation, or version control snapshots.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "file-names": {
+          "name": "file-names",
+          "summary": "Override default key-based file names with custom names (must match `--keys` count). Use when you want descriptive names for exported files (e.g., `--file-names account-standard.json`).",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "format": {
+          "name": "format",
+          "summary": "Display format: `table` (nine-column summary, default) or `json` (complete definition record with all fields).",
+          "default": "table",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "table",
+            "json"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:get",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Resolve profiling definition keys to their full configuration — see what each definition targets, which method it uses, and what state it is in.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "get.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:get",
+        "definition:cuneiform:get",
+        "definition:get:cuneiform",
+        "cuneiform:get:definition",
+        "get:cuneiform:definition",
+        "get:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:import": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling definitions capture the scoping decisions that tell Cuneiform what to analyze. When those decisions need to move between environments — sandbox to production, old scratch org to new, or restored after a refresh — this command imports them from CSV files produced by `definition export`.\n\nThe command reads a source directory containing `pnova__Profiling_Definition__c.csv`, generates a temporary import configuration, and executes the import. Partial failures are surfaced explicitly — if some definitions fail validation while others import successfully, the output identifies which objects failed and why.\n\nOPERATION MODES:\n\n- **Insert** (default) — Creates new records only. Fails on duplicate Name. Use for clean restores into empty orgs.\n- **Upsert** — Creates new records OR updates existing records matched by the Name external ID. Use when some definitions may already exist in the target org (e.g., incremental deployment to production).\n\nWHEN TO USE:\n\n- After a sandbox refresh — restore definitions from backup in under a minute\n- For production deployment — import validated definitions from sandbox with simulation as the approval artifact\n- For template provisioning — import a standard definition set into each new engagement org\n- To test safely — simulate first with --simulation to validate the entire pipeline before committing\n\nCOMMAND SEQUENCE: `definition export` (save definitions to files) → `definition import --simulation` (validate against target) → `definition import` (execute) → `profile` (run profiling with restored definitions)",
+      "examples": [
+        "Restore definitions after a sandbox refresh:\n<%= config.bin %> <%= command.id %> --target-org myOrg --source ./backup/definitions",
+        "Validate the import before committing (simulation runs the full pipeline without writing):\n<%= config.bin %> <%= command.id %> --target-org myOrg --source ./backup/definitions --simulation",
+        "Deploy validated definitions to production with Upsert to handle mixed scenarios:\n<%= config.bin %> <%= command.id %> --target-org prodOrg --source ./release/definitions --operation Upsert",
+        "Provision a new engagement org from a standard definition template:\n<%= config.bin %> <%= command.id %> --target-org newClientOrg --source ./templates/standard-definitions",
+        "Output as JSON for scripted verification in CI pipelines:\n<%= config.bin %> <%= command.id %> --target-org myOrg --source ./backup/definitions --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Salesforce org to import definitions into. The command validates Cuneiform installation before executing the import.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "source": {
+          "char": "s",
+          "name": "source",
+          "required": true,
+          "summary": "Directory containing the CSV files to import. Point this at a previous `definition export` output directory or any directory with a `pnova__Profiling_Definition__c.csv` file (e.g., --source ./backup/definitions).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "operation": {
+          "name": "operation",
+          "summary": "How to handle existing definitions: Insert (default) creates new records and fails on duplicate Names; Upsert creates new records and updates existing records matched by Name. Use Insert for clean restores into empty orgs. Use Upsert when some definitions may already exist from earlier iterations.",
+          "default": "Insert",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "Insert",
+            "Upsert"
+          ],
+          "type": "option"
+        },
+        "simulation": {
+          "char": "m",
+          "name": "simulation",
+          "summary": "Validate the import without modifying data. Runs the full import pipeline — parsing, validation, duplicate checking — but skips all writes. Use before production imports to verify the operation would succeed. The simulation output serves as a change approval artifact.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:import",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Restore or migrate profiling definitions into a Salesforce org from portable CSV files, with simulation to validate the result before any records are written.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "import.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:import",
+        "definition:cuneiform:import",
+        "definition:import:cuneiform",
+        "cuneiform:import:definition",
+        "import:cuneiform:definition",
+        "import:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:list": {
+      "aliases": [],
+      "args": {},
+      "description": "The profiling definition inventory is the foundation of any data profiling workflow. Before you can decide what to profile, you need to see what has already been defined, which objects are in scope, and which definitions are active, complete, or stuck. This command retrieves all profiling definitions from a Salesforce org and presents them as a paginated, filterable table with seven columns: definition key, name, target object, profiling method, category, profiling status, and last profiled date.\n\nAn Org Identity summary box provides org context, and a Summary box shows aggregate counts: total definitions, active, inactive, profiled, and not profiled. Active filters display above the table so you always know which narrowing is in effect. Contextual next steps suggest `definition get`, `definition create`, and `profile` commands with the target org pre-populated.\n\n**When to use vs related commands:**\n\n- `definition list` — \"Show me everything\" / \"What definitions exist?\" / \"Which definitions need profiling?\" (browse and filter across many)\n- `definition get` — \"Show me PD-0001\" / \"Verify this definition before profiling\" (targeted lookup by key)\n\nFILTERING — six dimensions narrow results to precisely targeted subsets:\n\n--objects Account — Only definitions targeting the Account object\n--status active — Only active definitions (vs inactive or all)\n--method metadata — Only metadata-type definitions (vs historical or comparative)\n--category \"Phase 1\" — Only definitions in a specific category\n--namespace FinServ — Only definitions for Financial Services Cloud objects\n--pattern Account% — Definitions whose name matches a SOQL LIKE pattern\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\n\"show all definitions\" → (no filter flags)\n\"definitions for Account\" → --objects Account\n\"which definitions are active\" → --status active\n\"metadata definitions only\" → --method metadata\n\"definitions not yet profiled\" → --sort lastProfiledDate\n\"only FSC definitions\" → --namespace FinServ\n\nCOMMAND SEQUENCE: `definition create` (build definitions) → `definition list` (review inventory) → `definition get` / `profile` / `definition purge` (act on specific definitions)",
+      "examples": [
+        "Inventory all definitions in the org — see the full picture before deciding what to profile next:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Focus on a specific object — show only definitions targeting Account:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account",
+        "Find active definitions ready for profiling:\n<%= config.bin %> <%= command.id %> --target-org myOrg --status active",
+        "Isolate Financial Services Cloud definitions by namespace:\n<%= config.bin %> <%= command.id %> --target-org myOrg --namespace FinServ",
+        "Page through a large definition inventory (page 3 of 25-per-page):\n<%= config.bin %> <%= command.id %> --target-org myOrg --limit 25 --offset 50",
+        "Export the inventory as JSON for engagement reports or scripting:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Retrieve definitions from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "status": {
+          "name": "status",
+          "summary": "Filter by activity status: `active` (currently usable for profiling), `inactive` (disabled), or `all` (both). Defaults to `all`, which gives the broadest view for discovery.",
+          "default": "all",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "active",
+            "inactive",
+            "all"
+          ],
+          "type": "option"
+        },
+        "method": {
+          "name": "method",
+          "summary": "Filter by profiling method: `metadata`, `historical`, or `comparative`. Use this when reviewing definitions of a single analysis type (e.g., `--method historical` to see only historical definitions).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "metadata",
+            "historical",
+            "comparative"
+          ],
+          "type": "option"
+        },
+        "objects": {
+          "name": "objects",
+          "summary": "Narrow the inventory to definitions targeting specific objects (comma-separated). For example, `--objects Account,Contact` shows only definitions for Account and Contact.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "pattern": {
+          "name": "pattern",
+          "summary": "Filter definitions by name pattern using SOQL LIKE wildcards. Use `%` for multi-character and `_` for single-character wildcards (e.g., `Account%` matches all definitions whose name starts with \"Account\").",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "category": {
+          "name": "category",
+          "summary": "Filter by the category label assigned during definition creation (e.g., \"Phase 1\", \"Sales Cloud\"). Use this to view definitions grouped by engagement phase or functional area.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "namespace": {
+          "name": "namespace",
+          "summary": "Filter by the namespace prefix of the target object (e.g., `FinServ` for Financial Services Cloud, `SBQQ` for CPQ). Use this to isolate definitions belonging to a specific managed package.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "limit": {
+          "name": "limit",
+          "summary": "Maximum definitions per page (default: 25, max: 200). Use with `--offset` to paginate through large inventories.",
+          "default": 25,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "offset": {
+          "name": "offset",
+          "summary": "Skip this many definitions before returning results. Use with `--limit` for pagination (e.g., `--limit 25 --offset 25` returns the second page).",
+          "default": 0,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "sort": {
+          "name": "sort",
+          "summary": "Sort results by: `key` (definition key), `name` (definition name, the default), `objectName` (target object), or `lastProfiledDate` (most recently profiled first).",
+          "default": "name",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "key",
+            "name",
+            "objectName",
+            "lastProfiledDate"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:list",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Inventory profiling definitions across a Salesforce org — see what has been defined, what method each uses, and where profiling stands — so you know where to focus next.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "list.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:list",
+        "definition:cuneiform:list",
+        "definition:list:cuneiform",
+        "cuneiform:list:definition",
+        "list:cuneiform:definition",
+        "list:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:purge": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling definitions accumulate over iterative scoping cycles: test definitions, exploration definitions, definitions for objects the team decided not to profile. This command removes them, leaving the inventory focused on current business intent.\n\nThree selection modes: by specific definition key (`--keys`), by composable AND filters (object, pattern, method, category, status, namespace), or all definitions (`--all`). Before deletion, the command pre-categorizes every matched definition into two groups: deletable (no summaries) and blocked by summaries (must run `summary purge` first). A paginated preview table shows this categorization with a can-delete indicator per definition.\n\nIMPORTANT: Definitions with existing summaries must have their summaries purged first. The full cleanup dependency order:\n\n1. `sf cuneiform profile request cancel` — cancel queued requests\n2. `sf cuneiform profile request delete` — remove canceled and rejected requests\n3. `sf cuneiform summary purge` — remove summaries (cascade-deletes completed requests; resets definition status)\n4. `sf cuneiform definition purge` — remove definitions (requires zero summaries)\n\nTHREE SELECTION MODES:\n\n- **By key** (`--keys PD-0001,PD-0003`) — Delete specific definitions. Exclusive mode — all filter flags are ignored.\n- **By filter** (`--objects Account --method metadata`) — Delete definitions matching ALL specified filters (AND logic). Combine --objects, --filter, --pattern, --method, --category, --status, and --namespace.\n- **All** (`--all`) — Delete all eligible definitions. Can be combined with filters to narrow scope.\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"delete the Account definition\" → --keys PD-0001 (look up the key with `definition list`)\n\"remove all unused definitions\" → --all --status \"NOT PROFILED\"\n\"clean up custom object definitions\" → --all --filter custom\n\"delete metadata-only definitions\" → --all --method metadata\n\"remove FSC definitions\" → --all --namespace FinServ\n\"what would be deleted?\" → --all --dry-run\n\nCOMMAND SEQUENCE: `summary purge` (remove summaries from blocked definitions) → `definition purge --dry-run` (preview) → `definition purge` (execute)",
+      "examples": [
+        "Preview what would be deleted and what is blocked by summaries:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Delete specific definitions by key (exclusive mode ignores all filters):\n<%= config.bin %> <%= command.id %> --target-org myOrg --keys PD-0001,PD-0003",
+        "Remove definitions that were never profiled after exploration:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --status \"NOT PROFILED\"",
+        "Clean up Financial Services Cloud definitions no longer in profiling scope:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --namespace FinServ",
+        "Remove metadata-only definitions after upgrading to comparative analysis:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --method metadata",
+        "Scripted scratch org reset with JSON output for CI verification:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --no-prompt --format json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Salesforce org to purge definitions from. The command validates Cuneiform installation and permissions before any deletions.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "name": "all",
+          "summary": "Target all definitions for deletion. Combine with filter flags (--objects, --method, --status, etc.) to narrow scope. Definitions blocked by summaries are reported but not deleted — run `summary purge` for those first.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "keys": {
+          "char": "k",
+          "name": "keys",
+          "summary": "Delete specific definitions by key (e.g., --keys PD-0001,PD-0003). Exclusive mode — when --keys is specified, all other filter flags are ignored. Look up definition keys with `definition list`.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "objects": {
+          "char": "b",
+          "name": "objects",
+          "summary": "Filter definitions by target object API names (e.g., --objects Account,Contact). Limits deletion to definitions targeting the specified objects.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "filter": {
+          "char": "f",
+          "name": "filter",
+          "summary": "Filter definitions by object type: standard or custom. Targets definitions for one category of objects (e.g., --filter custom to clean up custom object definitions after scoping).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "standard",
+            "custom"
+          ],
+          "type": "option"
+        },
+        "pattern": {
+          "char": "p",
+          "name": "pattern",
+          "summary": "Filter definitions by name pattern using SOQL LIKE wildcards (e.g., --pattern Account% matches definitions whose name starts with \"Account\"). Use % for multi-character wildcard and \\_ for single-character wildcard.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "method": {
+          "char": "t",
+          "name": "method",
+          "summary": "Filter definitions by profiling method: metadata, historical, or comparative (e.g., --method metadata to remove metadata-only definitions). Targets definitions of a specific analysis type.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "metadata",
+            "historical",
+            "comparative"
+          ],
+          "type": "option"
+        },
+        "category": {
+          "char": "c",
+          "name": "category",
+          "summary": "Filter definitions by category label (e.g., --category \"Phase 1\"). Removes definitions from a completed engagement phase or functional area.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "status": {
+          "char": "s",
+          "name": "status",
+          "summary": "Filter definitions by profiling status: \"NOT PROFILED\", \"IN PROGRESS\", \"COMPLETE\", \"COMPLETE w/ FAILURES\", or \"ERROR\". Use --status \"NOT PROFILED\" to target definitions that were created but never executed.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "NOT PROFILED",
+            "IN PROGRESS",
+            "SUCCESS",
+            "COMPLETE w/ FAILURES",
+            "ERROR"
+          ],
+          "type": "option"
+        },
+        "namespace": {
+          "char": "n",
+          "name": "namespace",
+          "summary": "Filter definitions by the namespace prefix of their target object (e.g., --namespace FinServ for Financial Services Cloud, --namespace SBQQ for CPQ). Removes definitions for a managed package that is no longer in profiling scope.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Maximum number of definitions to process per batch (default: 50). Controls batch size for large deletion operations.",
+          "default": 50,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview what would be deleted without making changes. Shows the same two-category classification (deletable and blocked by summaries) as a real run. Use this first to verify scope and share the preview with stakeholders before committing.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and delete immediately. Use for scripted execution in CI pipelines and automation workflows.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "format": {
+          "name": "format",
+          "summary": "Output format: table (default, human-readable) or json (structured output for scripted pipelines).",
+          "default": "table",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "table",
+            "json"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:purge",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Delete profiling definitions that no longer represent current analysis intent — keeping the definition inventory focused on actively profiled objects.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "PURGE_NO_SELECTION_CRITERIA": "errors.noSelectionCriteria",
+        "PURGE_NO_ELIGIBLE_DEFINITIONS": "errors.noEligibleDefinitions",
+        "PURGE_QUERY_FAILED": "errors.queryFailed",
+        "PURGE_DELETE_FAILED": "errors.deleteFailed"
+      },
+      "REASON_LABELS": {
+        "has_summaries": "Has Summaries",
+        "not_found": "Not Found",
+        "lookup_failed": "Lookup Failed"
+      },
+      "QUEUED_REASON": "has related requests in queue",
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "purge.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:purge",
+        "definition:cuneiform:purge",
+        "definition:purge:cuneiform",
+        "cuneiform:purge:definition",
+        "purge:cuneiform:definition",
+        "purge:definition:cuneiform"
+      ]
+    },
+    "cuneiform:definition:update": {
+      "aliases": [],
+      "args": {},
+      "description": "A profiling definition has two distinct surfaces: its metadata attributes (name, category, time category, segment category, description) and its field selection. This command edits the metadata attributes only — the field selection set at creation time is not mutable through this command.\n\nSupply one or more of the five attribute flags to update exactly those columns; untouched attributes are preserved.\n\nWHAT IT DOES:\n\n- Writes only the supplied attributes; untouched columns are preserved on the record\n- Validates the definition ID format (15 or 18 character Salesforce ID)\n- Enforces length constraints: name, category, time category, segment category max 255 chars; description max 8192 chars\n- Returns the list of attribute names that were written\n\nWHEN TO USE:\n\n- To rename a definition after a scope change or project rebranding\n- To reclassify definitions under a new category for cleaner reporting\n- To assign or update time and segment labels after profiling results are reviewed\n- To add or revise the description for team documentation purposes\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"rename this definition\" → --name \"New Definition Name\"\n\"set the category to Revenue\" → --category \"Revenue\"\n\"tag this as Q1 2025\" → --time-category \"Q1 2025\"\n\"classify as Closed Won accounts\" → --segment-category \"Closed Won\"\n\"update the description\" → --description \"Detailed profiling of high-value accounts\"\n\nCOMMAND SEQUENCE: `definition get` (retrieve current metadata and definition ID) → `definition update` (update attributes) → `definition list` (confirm updated values)",
+      "examples": [
+        "Rename a definition:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a00000000000001AAA --name \"Q1 2025 Revenue Analysis\"",
+        "Update the category and time category together:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a00000000000001AAA --category \"Revenue\" --time-category \"Q1 2025\"",
+        "Add a segment category to an existing definition:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a00000000000001AAA --segment-category \"Closed Won\"",
+        "Update all five attributes at once:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a00000000000001AAA --name \"Full Profile\" --category \"Revenue\" --time-category \"2025\" --segment-category \"All\" --description \"Complete revenue profile\"",
+        "Output update results as JSON for scripted pipelines:\n<%= config.bin %> <%= command.id %> --target-org myOrg --id a00000000000001AAA --name \"Renamed\" --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Salesforce org containing the definition to update. The command validates permissions before writing.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "id": {
+          "aliases": [
+            "definition-id"
+          ],
+          "deprecateAliases": true,
+          "name": "id",
+          "required": true,
+          "summary": "Salesforce record ID (15 or 18 character) of the profiling definition to update. Retrieve definition IDs with `sf cuneiform definition get` or `sf cuneiform definition list`.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "name": {
+          "name": "name",
+          "required": false,
+          "summary": "New definition name (max 255 characters). Replaces the current Prop_Name\\_\\_c value.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "category": {
+          "name": "category",
+          "required": false,
+          "summary": "New category label (max 255 characters). Replaces the current Prop_Category\\_\\_c value. Use to group definitions for reporting.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "time-category": {
+          "name": "time-category",
+          "required": false,
+          "summary": "New time category label (max 255 characters). Replaces the current Prop_TimeCategory\\_\\_c value. Examples: \"Q1 2025\", \"Lifetime\", \"2024\".",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "segment-category": {
+          "name": "segment-category",
+          "required": false,
+          "summary": "New segment category label (max 255 characters). Replaces the current Prop_SegmentCategory\\_\\_c value. Examples: \"Closed Won\", \"PersonAccounts\", \"Open Cases\".",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "description": {
+          "name": "description",
+          "required": false,
+          "summary": "New description (max 8192 characters). Replaces the current Prop_Description\\_\\_c value. Supports HTML content.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "format": {
+          "name": "format",
+          "summary": "Output format: table (human-readable, default) or json (structured output for scripting).",
+          "default": "table",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "table",
+            "json"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:definition:update",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Update metadata attributes (name, category, time category, segment category, description) on an existing profiling definition.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "definition",
+        "update.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:definition:update",
+        "definition:cuneiform:update",
+        "definition:update:cuneiform",
+        "cuneiform:update:definition",
+        "update:cuneiform:definition",
+        "update:definition:cuneiform"
+      ]
+    },
+    "cuneiform:mcp:serve": {
+      "aliases": [],
+      "args": {},
+      "description": "Starts the Cuneiform MCP (Model Context Protocol) server, exposing Cuneiform CLI capabilities as tools for AI assistants. Once running, an LLM client can query your org, list objects, describe fields, manage definitions, and execute profiling through natural language — using the same permissions as your CLI session.\n\nThe server registers tools across categories covering org and metadata discovery, user management, definition lifecycle, definition import/export, analysis, and profiling execution. A system prompt provides LLMs with an incremental exploration workflow for the KYCD journey.\n\nDavid Chen wires this into Claude Desktop and Cursor workflows — the registered tools give him a well-defined API contract. Marcus Thompson uses it to accelerate org exploration through conversational queries. Andre Robitaille demonstrates MCP integration during workshops, where attendees experience Cuneiform through natural dialogue.\n\nTRANSPORT: The server uses stdio (stdin/stdout) with JSON-RPC 2.0 protocol. Logging goes to stderr (enable with --debug). The stdio transport ensures the server runs locally alongside the Salesforce CLI — same machine, same authenticated session.\n\nThis command blocks until the MCP client disconnects. It is designed to be launched by an MCP client (Claude Desktop, Cursor, etc.). The access gate validates Cuneiform permissions at startup — the same gate used by all Cuneiform commands. On access gate failure, the command exits with an error describing the missing permission and how to resolve it via `user details --configure`.\n\n**When to run this command:**\n\n- AI-guided org discovery — let Claude explore a new client org through natural language\n- Hands-free definition creation — describe what you want and let the AI translate to tool calls\n- Training demonstrations — show Cuneiform capabilities through interactive AI conversation\n- Automated workflows — integrate Cuneiform tools into AI agent pipelines\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"start the MCP server\" → --target-org myOrg\n\"troubleshoot MCP tool calls\" → --target-org myOrg --debug\n\"pin a specific API version\" → --target-org myOrg --api-version 59.0\n\nCONFIGURATION: Add the server to your AI tool's settings. For Claude Desktop, add to `claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"cuneiform\": {\n      \"command\": \"sf\",\n      \"args\": [\"cuneiform\", \"mcp\", \"serve\", \"--target-org\", \"myOrg\"]\n    }\n  }\n}\n```",
+      "examples": [
+        "Start the MCP server for an org — the standard launch configuration:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Start with debug logging — see tool invocations and parameters on stderr:\n<%= config.bin %> <%= command.id %> --target-org myOrg --debug",
+        "Pin a specific API version — for consistent behavior across environments:\n<%= config.bin %> <%= command.id %> --target-org myOrg --api-version 59.0"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "The Salesforce org to connect the MCP server to. The server inherits this org's authentication for all 18 tool invocations. Specify the org alias or username.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "char": "a",
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "summary": "Override the API version used for Salesforce API requests made through MCP tools. Use when troubleshooting version-specific behavior or testing against a specific API release.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "debug": {
+          "char": "d",
+          "name": "debug",
+          "summary": "Enable debug logging to stderr. Shows tool invocations, parameters, and response metadata for troubleshooting MCP communication. stdout remains reserved for MCP protocol traffic.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hidden": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:mcp:serve",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Start the MCP server to expose 18 Cuneiform tools to AI assistants — enabling natural language org discovery, definition management, and profiling through Claude Desktop, Cursor, or any MCP client.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "mcp",
+        "serve.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:mcp:serve",
+        "mcp:cuneiform:serve",
+        "mcp:serve:cuneiform",
+        "cuneiform:serve:mcp",
+        "serve:cuneiform:mcp",
+        "serve:mcp:cuneiform"
+      ]
+    },
+    "cuneiform:object:describe": {
+      "aliases": [],
+      "args": {},
+      "description": "Understanding an object before profiling it is the difference between a targeted assessment and a fishing expedition. Salesforce scatters object metadata across Object Manager, Schema Builder, and Setup. This command consolidates everything into structured sections from a single call:\n\n- **Object Summary** — record count, field totals, type\n- **Record Age Distribution** — year-by-year grid showing when records were created (Cuneiform-exclusive), revealing whether data is actively growing, historical, or stagnant\n- **Record Types** — name, developer name, active status, default flag\n- **Business Processes** — active processes with record type associations and per-process record age grids\n- **Field Summary** — total, standard, custom, formula, lookup counts\n- **Field Type Distribution** — type counts with percentages\n- **Namespace Breakdown** — fields grouped by namespace prefix showing which managed packages contribute fields\n- **External References** — other objects that reference this one via lookups or master-detail\n- **Outbound Lookups** — this object's lookup fields and their target objects\n- **Profiling Status** — existing definitions, summary counts, last profiled date\n- **Field Listing** (opt-in via `--with-fields`) — individual field detail with filtering and sorting\n\nThe record age distribution and per-business-process age grids directly inform the choice between metadata, historical, and comparative profiling methods. The profiling status section shows whether definitions already exist, preventing duplicate work.\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\n\"Show me the fields\" → `--with-fields`\n\"Just the lookup fields\" → `--with-fields --field-type lookup`\n\"Just custom fields\" → `--with-fields --field-pattern \"*__c\"`\n\"Sort fields by type\" → `--with-fields --sort type`\n\"Compare multiple objects\" → `--object Account,Contact,Opportunity`\n\nFor multiple objects (comma-separated), describes run in parallel with aggregate totals across all objects. Big Objects (**b) and External Objects (**x) are not supported — they lack standard SOQL support.\n\nRead-only. Does not modify objects, fields, or metadata. The access gate validates Cuneiform installation and permissions before queries execute.\n\nCOMMAND SEQUENCE: `object list` (identify objects of interest) → `object describe` (deep dive on specific objects) → `definition create` (define profiling scope based on what you learned)",
+      "examples": [
+        "Assess an object before building profiling definitions — see all 11 metadata sections:\n<%= config.bin %> <%= command.id %> --object Account --target-org myOrg",
+        "Compare multiple objects in parallel with aggregate totals for profiling scope decisions:\n<%= config.bin %> <%= command.id %> --object Account,Contact,Opportunity --target-org myOrg",
+        "Full field inventory — add detailed field listings to see every field on the object:\n<%= config.bin %> <%= command.id %> --object Account --with-fields --target-org myOrg",
+        "Relationship mapping — isolate lookup fields to understand the object's position in the data model:\n<%= config.bin %> <%= command.id %> --object Account --with-fields --field-type lookup --sort type --target-org myOrg",
+        "Custom field audit — filter to custom fields for a managed package or customization review:\n<%= config.bin %> <%= command.id %> --object Account --with-fields --field-pattern \"\\*\\_\\_c\" --target-org myOrg",
+        "JSON for automation — pipe structured metadata to assessment pipelines or architecture documentation:\n<%= config.bin %> <%= command.id %> --object Account --json --target-org myOrg"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Describe objects from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "object": {
+          "name": "object",
+          "required": true,
+          "summary": "Object API name(s), comma-separated. Use one name for a complete deep dive or multiple for side-by-side comparison with aggregate totals (e.g., `Account,Contact,Opportunity`).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "with-fields": {
+          "aliases": [
+            "show-fields"
+          ],
+          "deprecateAliases": true,
+          "name": "with-fields",
+          "summary": "Include a detailed field listing showing individual fields with API name, label, type, custom flag, and namespace. Use with `--field-type`, `--field-pattern`, and `--sort` to filter and organize the listing.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "field-type": {
+          "name": "field-type",
+          "summary": "Filter the field listing to a specific type (requires `--with-fields`). Valid types: text, picklist, lookup, number, date, formula, checkbox, id, address. Use `lookup` to map the object's relationship network.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "text",
+            "picklist",
+            "lookup",
+            "number",
+            "date",
+            "formula",
+            "checkbox",
+            "id",
+            "address"
+          ],
+          "type": "option"
+        },
+        "field-pattern": {
+          "name": "field-pattern",
+          "summary": "Filter the field listing by API name pattern with wildcard support (requires `--with-fields`). Examples: `*__c` for custom fields, `pnova__*` for Cuneiform namespace fields.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "sort": {
+          "name": "sort",
+          "summary": "Sort the field listing by: `name` (alphabetical, the default), `type` (grouped by field type), or `label`. Requires `--with-fields`.",
+          "default": "name",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "name",
+            "type",
+            "label"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:object:describe",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Retrieve comprehensive object metadata — fields, record types, data age distribution, relationships, and profiling status — to make informed decisions about what and how to profile.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "object",
+        "describe.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:object:describe",
+        "object:cuneiform:describe",
+        "object:describe:cuneiform",
+        "cuneiform:describe:object",
+        "describe:cuneiform:object",
+        "describe:object:cuneiform"
+      ]
+    },
+    "cuneiform:object:list": {
+      "aliases": [],
+      "args": {},
+      "description": "A typical Salesforce org contains 500 to 2,000 objects. Most are empty platform objects, managed package internals, or system metadata. Finding the objects that actually hold customer data — the ones worth profiling — requires navigating Object Manager, running SOQL counts, and cross-referencing namespace prefixes. This command transforms that exploration into a single call with filter flags and enrichment options.\n\nThe default customer-facing classification filter focuses attention on objects most likely relevant for profiling scope decisions. Record counts distinguish populated objects from empty shells. Namespace distribution reveals how the org's data is partitioned across standard Salesforce, industry clouds, managed packages, and custom development.\n\n**Six output sections:**\n\n- **Org Identity** — org name, edition, instance URL\n- **Summary Statistics** — total objects, objects with records, standard/custom/external counts, namespace distribution\n- **Namespace Distribution** — objects grouped by standard, industry, managed, and custom categories\n- **Objects Table** — name, label, record count, type, namespace — plus optional enrichment columns\n- **Contact Points** — email, phone, and URL field details (when `--with-contact-points` is specified)\n- **Next Steps** — `object describe` for field-level deep dives, `definition create` for profiling scope\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\n\"Which objects have data?\" → `--with-records`\n\"What custom objects exist?\" → `--filter custom`\n\"What did CPQ add to this org?\" → `--namespace SBQQ`\n\"Which objects match a name?\" → `--pattern Account*`\n\"Which objects have meaningful volume?\" → `--min-records 1000`\n\"Which objects can be assigned to users?\" → `--with-owner`\n\"Which objects have record type segmentation?\" → `--with-record-types`\n\"Where are email, phone, and address fields?\" → `--with-contact-points`\n\"How complex is each object?\" → `--with-fields`\n\"Which objects reference other objects?\" → `--with-references`\n\n**How this differs from `object describe`:** This command shows the broad inventory across many objects. Use `object describe` when you need the deep dive on a specific object's fields, record types, relationships, and data age.\n\nRead-only. Does not create, modify, or delete records or metadata. Results default to customer-facing classification, sorted by record count descending, paginated at 50 with a visible notice when more exist.\n\nCOMMAND SEQUENCE: `org details` (understand the org landscape) → `object list` (identify objects of interest) → `object describe` (deep dive on specific objects) → `definition create` (define profiling scope)",
+      "examples": [
+        "Explore a new org — see customer-facing objects sorted by data volume (the default starting point):\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Custom object audit — inventory custom objects for a handoff document or data model review:\n<%= config.bin %> <%= command.id %> --target-org myOrg --filter custom",
+        "Namespace-focused scope — see how Financial Services Cloud objects are populated:\n<%= config.bin %> <%= command.id %> --target-org myOrg --namespace FinServ --with-fields --with-record-types",
+        "Profiling candidates — focus on high-volume objects worth profiling:\n<%= config.bin %> <%= command.id %> --target-org myOrg --with-records --min-records 1000 --sort recordCount",
+        "Contact point discovery — find objects with email, phone, or address fields before an analysis engagement:\n<%= config.bin %> <%= command.id %> --target-org myOrg --with-contact-points --with-records",
+        "Complexity assessment — add field and reference counts to identify hub objects in the data model:\n<%= config.bin %> <%= command.id %> --target-org myOrg --with-fields --with-references --with-records"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "List objects from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "object": {
+          "char": "O",
+          "name": "object",
+          "summary": "Fetch a single object by API name — bypasses all filters and the limit cap, and always returns the real record count. Use this when you know the exact object you need (e.g., `--object Lead`). Mutually exclusive with --filter (non-default), --namespace, --pattern, --without-records, and --min-records.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "filter": {
+          "char": "f",
+          "name": "filter",
+          "summary": "Filter by object type: `standard`, `custom`, or `all`. Use `custom` to audit custom data model objects or `standard` to focus on platform objects. Defaults to `all`.",
+          "default": "all",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "all",
+            "standard",
+            "custom"
+          ],
+          "type": "option"
+        },
+        "namespace": {
+          "char": "n",
+          "name": "namespace",
+          "summary": "Filter by namespace prefix (case-insensitive). Scope to a specific managed package — e.g., `SBQQ` for CPQ, `FinServ` for Financial Services Cloud. Use an empty string for unmanaged objects only.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "pattern": {
+          "char": "p",
+          "name": "pattern",
+          "summary": "Filter by API name pattern with wildcard support. Examples: `Account*` matches Account and AccountContactRelation; `*__c` matches custom objects.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "with-records": {
+          "name": "with-records",
+          "summary": "Show only objects that contain data (record count > 0). Filters out empty platform infrastructure and focuses on populated objects worth profiling.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "without-records": {
+          "name": "without-records",
+          "summary": "Show only empty objects (record count = 0). Identifies unused objects during org cleanup or newly provisioned objects awaiting data.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-owner": {
+          "name": "with-owner",
+          "summary": "Show only objects with an OwnerId field — objects whose records can be assigned to users. Identifies ownership-trackable data for profiling scope.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-record-types": {
+          "name": "with-record-types",
+          "summary": "Show only objects with record types defined. Record types indicate segmented data entry or business processes — relevant for deciding whether to use record-type-based profiling.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-business-process": {
+          "name": "with-business-process",
+          "summary": "Add a business process count column showing lifecycle processes (Lead, Opportunity, Case, Solution). Identifies objects with stage-based workflows before profiling.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-fields": {
+          "name": "with-fields",
+          "summary": "Add field count columns (total fields and custom fields) to gauge object complexity. Identifies objects with large field inventories before running `object describe`.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-references": {
+          "name": "with-references",
+          "summary": "Add a reference/lookup field count column. High reference counts indicate hub objects in the data model with dense relationship networks.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "with-contact-points": {
+          "name": "with-contact-points",
+          "summary": "Add contact point columns showing email, phone, and URL field counts per object. Discovers identity resolution candidates before a contact point analysis engagement.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "classification": {
+          "char": "c",
+          "name": "classification",
+          "summary": "Object classification filter: `customer` (customer-facing objects most relevant to profiling, the default), `internal` (system/platform objects), or `all`. The customer-facing filter uses heuristics based on object type, namespace, and naming patterns.",
+          "default": "all",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "customer",
+            "internal",
+            "all"
+          ],
+          "type": "option"
+        },
+        "min-records": {
+          "name": "min-records",
+          "summary": "Minimum record count threshold. Show only objects with at least this many records (e.g., `--min-records 1000` to focus on high-volume objects).",
+          "default": 0,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "sort": {
+          "char": "s",
+          "name": "sort",
+          "summary": "Sort results by: `name` (alphabetical), `recordCount` (highest first, the default), or `label`.",
+          "default": "recordCount",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "name",
+            "recordCount",
+            "label"
+          ],
+          "type": "option"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Maximum objects to display (1-200, default: 50). A notice appears when results are truncated — increase to see more, or use --pattern / --object to bypass this cap entirely.",
+          "default": 50,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:object:list",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Enumerate Salesforce objects with record counts, type classifications, and namespace distribution — so you can identify which objects hold customer data and focus profiling on what matters.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "object",
+        "list.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:object:list",
+        "object:cuneiform:list",
+        "object:list:cuneiform",
+        "cuneiform:list:object",
+        "list:cuneiform:object",
+        "list:object:cuneiform"
+      ]
+    },
+    "cuneiform:org:details": {
+      "aliases": [],
+      "args": {},
+      "description": "Salesforce spreads org configuration across Company Information, Installed Packages, Org Limits, Feature Settings, License Management, and more. Understanding what an org contains before profiling typically means navigating between these pages to build a mental model. This command consolidates that orientation into a single call that returns in seconds.\n\n**Structured sections, one command:**\n\n- **Identity** — org name, type (Production/Sandbox/Scratch/Developer/Trial), edition, instance URL, namespace\n- **Cuneiform** — installation status, package version, and license state\n- **Features** — enabled capabilities (Multi-Currency, Person Accounts, Einstein AI, Enhanced Notes, and others)\n- **Clouds** — Salesforce products detected by license queries and namespace prefix matching (Financial Services, CPQ, Health Cloud, and others found in the org)\n- **Namespaces** — installed packages with object counts and population rates per namespace\n- **Processes** — active business processes with record type associations\n- **Limits** — current API request quotas, data and file storage consumption, with capacity warnings at 95%\n- **Next Steps** — command suggestions tailored to the org's namespace composition and data\n\nJames Morrison runs this first in every new org. Sarah Mitchell checks limits before profiling runs. Marcus Thompson uses the dynamic next steps to guide his exploration path.\n\n**When to run this command:**\n\n- Entering a new org for the first time and building a mental model of its product landscape\n- Checking API and storage capacity before submitting profiling requests\n- Verifying Cuneiform installation and license status in a new sandbox\n- Understanding which Salesforce products (Clouds, managed packages) are installed before scoping profiling\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"show me everything about this org\" → no flags (all sections)\n\"check my API limits\" → --sections limits\n\"is Cuneiform installed?\" → --sections cuneiform\n\"what Clouds are in this org?\" → --sections clouds\n\"show me all limits grouped\" → --sections limits-all\n\"how much storage is used?\" → --sections limits-storage\n\nCOMMAND SEQUENCE:\n`org details` → `object list` → `user details` → `definition create` → `profile`\n\nThis is typically the first command run in any engagement. It precedes `object list` (exploring what objects have data) and `user details` (verifying profiling readiness). Read-only — consolidates existing data from multiple API endpoints into a single view.",
+      "examples": [
+        "Engagement kickoff — see the full org picture (edition, products, features, capacity, namespace composition):\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Pre-profiling capacity check — verify API and storage capacity before submitting profiling requests:\n<%= config.bin %> <%= command.id %> --target-org myOrg --sections limits",
+        "Cuneiform readiness — confirm installation and license status in a new sandbox:\n<%= config.bin %> <%= command.id %> --target-org myOrg --sections cuneiform",
+        "Product landscape — see which Salesforce Clouds are installed to scope profiling by product:\n<%= config.bin %> <%= command.id %> --target-org myOrg --sections clouds",
+        "Namespace composition — identify managed packages and their object counts for profiling scope:\n<%= config.bin %> <%= command.id %> --target-org myOrg --sections namespaces",
+        "Storage detail — check data and file storage consumption before a profiling run:\n<%= config.bin %> <%= command.id %> --target-org myOrg --sections limits-storage",
+        "JSON for automation — pipe structured output to assessment pipelines or SOW templates:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "The Salesforce org to retrieve configuration details from. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "char": "a",
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "summary": "Override the Salesforce API version used for org configuration queries. Use this when troubleshooting version-specific behavior or testing against a specific API release.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "sections": {
+          "char": "s",
+          "name": "sections",
+          "required": false,
+          "summary": "Filter to specific sections instead of displaying the full eight-section report. Valid values: identity, cuneiform, features, clouds, namespaces, processes, limits. For limits granularity: limits-all (groups limits by category) or limits-api, limits-storage, limits-bulk, limits-apex, limits-streaming, limits-email (single category). Omit to display all sections.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:org:details",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Consolidate org configuration — products, features, capacity, and namespace composition — into a single view that replaces navigating six Setup pages.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "org",
+        "details.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:org:details",
+        "org:cuneiform:details",
+        "org:details:cuneiform",
+        "cuneiform:details:org",
+        "details:cuneiform:org",
+        "details:org:cuneiform"
+      ]
+    },
+    "cuneiform:org:reset": {
+      "aliases": [],
+      "args": {},
+      "description": "Purges all profiling definitions matching a name pattern (default: `[NUT-*]`), cancels active profiling requests, and deletes terminal requests. Use this command to restore a scratch org to a clean state after NUT test runs.\n\nThe reset sequence is:\n\n1. Query definitions matching the name pattern\n2. Cancel any active profiling requests\n3. Delete cancelled/rejected profiling requests\n4. Delete definitions that have no related summaries\n\nDefinitions with related summaries are skipped — use `sf cuneiform summary purge` first to remove them.",
+      "examples": [
+        "Reset org by removing all NUT-created test data: `sf cuneiform org reset --target-org myOrg`",
+        "Preview what would be deleted without making changes: `sf cuneiform org reset --target-org myOrg --dry-run`",
+        "Reset with a custom pattern: `sf cuneiform org reset --target-org myOrg --pattern \"Test%\"`",
+        "Reset without confirmation prompt: `sf cuneiform org reset --target-org myOrg --no-prompt`"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "pattern": {
+          "char": "p",
+          "name": "pattern",
+          "summary": "SOQL LIKE pattern for definition names to purge.",
+          "default": "[NUT-%",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview what would be deleted without making changes.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "n",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt before deleting.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hidden": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:org:reset",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Reset org by removing Cuneiform test data created by NUT tests.",
+      "enableJsonFlag": true,
+      "skipAccessGate": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "org",
+        "reset.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:org:reset",
+        "org:cuneiform:reset",
+        "org:reset:cuneiform",
+        "cuneiform:reset:org",
+        "reset:cuneiform:org",
+        "reset:org:cuneiform"
+      ]
+    },
+    "cuneiform:summary:purge": {
+      "aliases": [],
+      "args": {},
+      "description": "Every profiling run creates a summary — a result record containing Field Results, Value Results, and KPI Results. Over repeated profiling cycles, summaries accumulate. An org with 20 definitions profiled weekly generates over 1,000 summaries per year. The current profiling posture is the latest summary per definition; older summaries are historical artifacts.\n\nThis command deletes summaries and their child records from a Salesforce org. The `--prune` flag implements the standard housekeeping pattern: keep the latest summary per definition while removing older results. This is how Marcus Thompson closes engagement phases and how David Chen configures automated weekly cleanup.\n\n**Cleanup dependency order** — summary purge must happen BEFORE definition purge:\n\n1. `sf cuneiform profile request cancel` — cancel queued requests\n2. `sf cuneiform profile request delete` — remove canceled and rejected requests\n3. `sf cuneiform summary purge` — remove summaries (cascade-deletes completed requests; resets definition status to NOT PROFILED when all summaries are removed)\n4. `sf cuneiform definition purge` — remove definitions (requires zero summaries)\n\nTHREE SELECTION MODES:\n\n- **By ID** (`--ids`) — Delete specific summaries by Salesforce record ID. Exclusive mode — filter flags are ignored.\n- **By filter** (`--objects`, `--category`, `--is-active`) — Delete summaries matching filters. Summaries are resolved through their parent definitions: the command queries definitions first, then targets their associated summaries.\n- **All** (`--all`) — Delete all eligible summaries. Can be combined with filter flags to narrow scope.\n\nELIGIBILITY: Only summaries with a terminal profiling status (SUCCESS, COMPLETE w/ FAILURES, FAILED, CANCELED) can be deleted. In-progress summaries are automatically excluded and reported with a reason.\n\nSAFETY: Use --dry-run to preview the scope before deleting. The confirmation prompt shows affected summaries before proceeding. Cascade delete automatically removes child Field Results, Value Results, KPI Results, and related profiling requests (original and reprofile). Definition status resets to NOT PROFILED when all summaries for a definition are removed.\n\n**When to run this command:**\n\n- Post-sprint cleanup — prune intermediate results after iterative profiling cycles\n- Pre-sandbox-refresh storage reduction — free storage before the refresh window\n- Object-targeted cleanup after data model changes — remove stale summaries for redesigned objects\n- Before definition purge — clear summaries as a prerequisite for definition deletion\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"clean up old summaries, keep latest\" → --all --prune\n\"delete all summaries\" → --all\n\"delete Account summaries\" → --objects Account\n\"delete this specific summary\" → --ids a0Bxx0000001234AAA\n\"what would be deleted?\" → --all --dry-run\n\"clean up old summaries without asking\" → --all --prune --no-prompt\n\nCOMMAND SEQUENCE:\n`profile request cancel` → `profile request delete` → `summary purge` → `definition purge`",
+      "examples": [
+        "Preview what would be deleted — start here to verify scope:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Standard housekeeping — keep the latest summary per definition, remove older results:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --prune",
+        "Object-targeted cleanup — remove Account summaries after a data model redesign:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account",
+        "Complete cleanup — delete all terminal-state summaries:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all",
+        "Surgical removal — delete specific summaries by record ID:\n<%= config.bin %> <%= command.id %> --target-org myOrg --ids a0Bxx0000001234AAA,a0Bxx0000005678AAA",
+        "Automated weekly prune — for CI pipelines and scheduled jobs:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --prune --no-prompt --format json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "The Salesforce org to purge summaries from. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "name": "all",
+          "summary": "Target all eligible summaries for deletion. Can be combined with filter flags (--objects, --category, --is-active) to narrow scope. Combine with --prune to preserve the latest summary per definition while removing older results.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "ids": {
+          "char": "i",
+          "name": "ids",
+          "summary": "Specific summary record IDs to delete (comma-separated Salesforce record IDs). Exclusive mode — filter flags are ignored when --ids is specified. Use for surgical removal of individual summaries.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "objects": {
+          "aliases": [
+            "object-name"
+          ],
+          "char": "b",
+          "deprecateAliases": true,
+          "name": "objects",
+          "summary": "Filter by target object API name (matches the definition's profiled object). Scopes purge to summaries for specific objects (e.g., --objects Account removes only Account-related summaries).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "category": {
+          "char": "c",
+          "name": "category",
+          "summary": "Filter by definition category label (e.g., \"Phase 1\", \"Baseline\"). Scopes purge to summaries from a completed engagement phase or functional area.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "is-active": {
+          "name": "is-active",
+          "summary": "Filter by definition active status. Targets summaries belonging to active or inactive definitions.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Maximum number of summaries to process per invocation (default: 50). Controls batch size in large cleanup operations. Ignored when --all is specified.",
+          "default": 50,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "prune": {
+          "name": "prune",
+          "summary": "Preserve the latest summary for each definition and delete only older summaries. This is the standard housekeeping pattern — current profiling evidence is retained while historical results are removed. Combine with --all for org-wide pruning, or with filter flags to prune specific scopes.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview what would be deleted, applied to nothing. Shows the same categorization (eligible, skipped by status, preserved by prune) as a real purge. Run this first to verify scope before committing.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and delete immediately. Use in scripts and automation pipelines. The prompt normally shows which summaries (and their child records) will be permanently deleted.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "format": {
+          "name": "format",
+          "summary": "Output format: table (default, human-readable) or json (machine-readable for scripting and automation dashboards).",
+          "default": "table",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "table",
+            "json"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:summary:purge",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Delete profiling summaries and their child records — use --prune to preserve the latest summary per definition while removing older results.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "E4510": "errors.noSelectionCriteria",
+        "E4511": "errors.mutuallyExclusive",
+        "E4513": "errors.noEligibleSummaries",
+        "E4512": "errors.queryFailed",
+        "E4514": "errors.deleteFailed"
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "summary",
+        "purge.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:summary:purge",
+        "summary:cuneiform:purge",
+        "summary:purge:cuneiform",
+        "cuneiform:purge:summary",
+        "purge:cuneiform:summary",
+        "purge:summary:cuneiform"
+      ]
+    },
+    "cuneiform:summary:reprofile": {
+      "aliases": [],
+      "args": {},
+      "description": "When a profiling run fails due to transient errors or is manually stopped, the resulting summary has gaps — some fields completed, others did not. Those gaps in the KYCD evidence persist until someone acts on them. This command re-submits those summaries for targeted recovery.\n\nOnly failed and unprocessed fields are re-executed — previously completed fields are preserved. The existing summary record is reused. No definition recreation or reconfiguration is needed. This is a fire-and-forget operation: after submission, profiling re-executes asynchronously in the org. Use `sf cuneiform definition get` to check profiling status after submission.\n\nSTOP + REPROFILE form a natural pair: use `sf cuneiform summary stop` to halt a summary and free resources, then reprofile later to complete the remaining fields. This is the standard recovery pattern for resource management and transient failure recovery.\n\nTHREE SELECTION MODES (mutually exclusive):\n\n- **By ID** (`--ids`) — Reprofile specific summaries by Salesforce record ID\n- **All** (`--all`) — Reprofile all eligible (failed/stopped) summaries\n- **By object** (`--objects`) — Reprofile summaries for specific Salesforce objects\n\nOnly summaries with failed or stopped (canceled) status are eligible. In-progress and completed summaries are excluded.\n\nWHEN TO USE:\n\n- After stopping summaries — complete the fields that were not yet processed when the stop signal was sent\n- After transient failures — governor limits, API timeouts, or infrastructure interruptions caused partial results\n- Bulk recovery — re-submit all failed summaries in one command after a service disruption\n- Object-targeted recovery — reprofile only the objects that failed while leaving successful ones untouched\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"reprofile everything that failed\" → --all\n\"reprofile just Account\" → --objects Account\n\"reprofile this specific summary\" → --ids a0Bxx0000001234AAA\n\"what would be reprofiled?\" → --all --dry-run\n\"reprofile without asking\" → --all --no-prompt\n\nCOMMAND SEQUENCE:\n`summary stop` or failed profiling run → **`summary reprofile`** → `profile request list` (verify re-profiling completed)",
+      "examples": [
+        "Preview what would be reprofiled — assess recovery scope first:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Reprofile all failed and stopped summaries — bulk recovery:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all",
+        "Reprofile summaries for a specific object — targeted recovery:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account",
+        "Reprofile specific summaries by ID — surgical recovery:\n<%= config.bin %> <%= command.id %> --target-org myOrg --ids a0Bxx0000001234AAA,a0Bxx0000005678AAA",
+        "Reprofile summaries for multiple objects:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account,Contact",
+        "Reprofile immediately for automated recovery workflows:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --no-prompt"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Re-submit profiling summaries in this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ids": {
+          "char": "i",
+          "name": "ids",
+          "summary": "Reprofile specific summaries by Salesforce record ID (comma-separated). Use for targeted recovery of individual summaries when the failure scope is narrow. Find summary IDs with `definition get`. Mutually exclusive with --all and --objects.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "name": "all",
+          "summary": "Reprofile all eligible (failed or stopped) summaries across the org. Use for bulk recovery after infrastructure events, transient API failures, or governor limit spikes that affected multiple summaries. Mutually exclusive with --ids and --objects.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "objects": {
+          "char": "b",
+          "name": "objects",
+          "summary": "Reprofile summaries targeting specific Salesforce objects by API name (comma-separated). Use when only certain objects need recovery while others completed successfully. Mutually exclusive with --ids and --all.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview which summaries would be re-profiled, showing definition key, summary key, object, status, and planned action. Use to assess recovery scope and estimate the re-execution workload before committing.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and reprofile immediately. Use in automated recovery scripts or runbooks where interactive prompts are not available.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:summary:reprofile",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Re-submit failed or stopped profiling summaries for targeted recovery — only the failed and unprocessed fields are re-executed, preserving completed results.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "E4530": "errors.noSelectionCriteria",
+        "E4531": "errors.mutuallyExclusive",
+        "E4533": "errors.noEligibleSummaries",
+        "E4532": "errors.queryFailed",
+        "E4534": "errors.reprofileFailed"
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "summary",
+        "reprofile.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:summary:reprofile",
+        "summary:cuneiform:reprofile",
+        "summary:reprofile:cuneiform",
+        "cuneiform:reprofile:summary",
+        "reprofile:cuneiform:summary",
+        "reprofile:summary:cuneiform"
+      ]
+    },
+    "cuneiform:summary:stop": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling runs in the background and consumes org resources — API calls, processing time, and storage writes. When a profiling run needs to yield — because of resource contention, a scheduling conflict, or a configuration issue — this command provides immediate control.\n\nThe stop signal is sent and the command returns immediately (fire-and-forget). The backend handles the actual halting asynchronously. Fields that completed before the stop are preserved; unprocessed and in-progress fields are marked as failed. The summary status transitions to canceled.\n\nIMPORTANT: This command stops SUMMARIES, not requests. Summaries are the execution records created after a profiling request is processed. To prevent queued requests from being processed, use `sf cuneiform profile request cancel` instead.\n\nSTOP vs CANCEL — these address different objects at different lifecycle stages:\n\n- **Cancel** prevents a Request from being processed. No Summary is created.\n- **Stop** halts an active Summary. Partially completed results are preserved.\n\nSTOP + REPROFILE form a natural pair: stop a summary to release resources now, then use `sf cuneiform summary reprofile` later to re-execute only the failed and unprocessed fields. The existing summary is reused — no reconfiguration needed.\n\nTHREE SELECTION MODES (mutually exclusive):\n\n- **By ID** (`--ids`) — Stop specific summaries by Salesforce record ID\n- **All** (`--all`) — Stop all in-progress summaries\n- **By object** (`--objects`) — Stop summaries for specific Salesforce objects\n\nOnly summaries with in-progress profiling status are eligible. Completed, failed, and canceled summaries are excluded.\n\nWHEN TO USE:\n\n- Peak hours resource management — halt profiling to free API capacity, reprofile during off-hours\n- Long-running profiling on a large object — stop one object while others continue\n- Pre-maintenance window — stop active summaries before planned downtime\n- Definition adjustment — stop a run, fix the definition, then reprofile\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"stop everything\" → --all\n\"stop just Account profiling\" → --objects Account\n\"stop this specific summary\" → --ids a0Bxx0000001234AAA\n\"what would be stopped?\" → --all --dry-run\n\"stop without asking\" → --all --no-prompt\n\nCOMMAND SEQUENCE:\n`profile request list` (identify resource-consuming runs) → **`summary stop`** → `summary reprofile` (re-execute when conditions are appropriate)",
+      "examples": [
+        "Preview what would be stopped — verify scope before committing:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Stop all in-progress summaries — free resources during peak hours:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all",
+        "Stop profiling for a specific object while others continue:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account",
+        "Stop specific summaries by ID — targeted precision:\n<%= config.bin %> <%= command.id %> --target-org myOrg --ids a0Bxx0000001234AAA,a0Bxx0000005678AAA",
+        "Stop profiling for multiple objects at once:\n<%= config.bin %> <%= command.id %> --target-org myOrg --objects Account,Contact",
+        "Stop immediately for automated runbooks:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --no-prompt"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Stop profiling summaries in this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ids": {
+          "char": "i",
+          "name": "ids",
+          "summary": "Stop specific profiling summaries by Salesforce record ID (comma-separated). Use for targeted halting when only some summaries need to stop. Find summary IDs with `definition get`. Mutually exclusive with --all and --objects.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "name": "all",
+          "summary": "Stop all in-progress profiling summaries across the org. Use for peak hours resource management, pre-maintenance windows, or when the org needs its full API capacity immediately. Mutually exclusive with --ids and --objects.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "objects": {
+          "char": "b",
+          "name": "objects",
+          "summary": "Stop profiling for specific Salesforce objects by API name (comma-separated). Use when one object is consuming disproportionate resources while profiling on other objects should continue. Mutually exclusive with --ids and --all.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview which summaries would be stopped, showing definition key, summary key, object, status, and planned action. Use to verify scope before sending stop signals — especially important with --all.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and send stop signals immediately. Use in automated scripts, runbooks, or time-sensitive situations where interactive prompts are not practical.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:summary:stop",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Send a stop signal to in-progress profiling summaries — halt execution to free org resources, preserving fields that already completed.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "E4520": "errors.noSelectionCriteria",
+        "E4521": "errors.mutuallyExclusive",
+        "E4523": "errors.noEligibleSummaries",
+        "E4522": "errors.queryFailed",
+        "E4524": "errors.stopFailed"
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "summary",
+        "stop.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:summary:stop",
+        "summary:cuneiform:stop",
+        "summary:stop:cuneiform",
+        "cuneiform:stop:summary",
+        "stop:cuneiform:summary",
+        "stop:summary:cuneiform"
+      ]
+    },
+    "cuneiform:user:details": {
+      "aliases": [],
+      "args": {},
+      "description": "Remote profiling requires two configuration touchpoints spread across two Salesforce Setup pages: a permission set assignment and a Custom Metadata Type setting on your Configuration Profile. Missing either one produces a generic access error. This command checks both in one step and tells you exactly what is missing and who can fix it.\n\n**Three modes:**\n\n- **Diagnostic (default)** — Answer \"Am I set up to profile?\" Shows Cuneiform installation status, permission set assignments, Configuration Profile enablement, and resolution guidance for any gaps. Read-only — safe to run even when permissions are incomplete.\n- **Configure (`--configure`)** — Answer \"Set me up so I can profile.\" Assigns the required permission set via REST API and enables API-Based Profiling via Metadata API deployment in a single step. Idempotent — running it when already configured produces \"no changes needed.\" Blocked in production orgs.\n- **Preview (`--configure --dry-run`)** — Answer \"What would configure change?\" Shows exactly what would be assigned or enabled, applied to nothing. Use this in regulated environments where changes require documented approval before execution.\n\n**Resolution guidance routes by persona:** When gaps exist, the output distinguishes between steps you can take yourself (self-service via `--configure`) and steps that require a Salesforce administrator.\n\nSarah Mitchell uses this to onboard users for profiling. Marcus Thompson runs it on day one of every engagement — if access is missing, `--configure` resolves it in 15 seconds. Andre Robitaille uses `--configure` as the \"hello world\" of every workshop, turning NOT READY into READY as the first moment of participant success.\n\n**When to run this command:**\n\n- First time in a new org or after a sandbox refresh — confirm your user is configured before profiling\n- After getting an access error from any Cuneiform command — diagnose the exact gap\n- When onboarding workshop participants — each person runs `--configure` on their own account\n- Before a client-facing profiling session — verify readiness to prevent access failures mid-demo\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"am I set up to profile?\" → no flags (diagnostic mode)\n\"set me up for profiling\" → --configure\n\"what would configure change?\" → --configure --dry-run\n\"undo my configuration\" → --unconfigure\n\nCOMMAND SEQUENCE:\n`org details` → `user details` → `definition create` → `profile`\n\nThe scope is the authenticated user's profiling readiness: permission set assignment and API-Based Profiling enablement. It typically follows `org details` (confirming Cuneiform is installed) and precedes `definition create` (building profiling definitions).",
+      "examples": [
+        "First-time readiness check — confirm your user is configured before profiling:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Resolve all gaps at once — configure both touchpoints (permission set + API-Based Profiling) automatically:\n<%= config.bin %> <%= command.id %> --target-org myOrg --configure",
+        "Change management preview — document what would change before applying:\n<%= config.bin %> <%= command.id %> --target-org myOrg --configure --dry-run",
+        "Workshop onboarding — each participant configures their own account:\n<%= config.bin %> <%= command.id %> --target-org workshopOrg --configure",
+        "Troubleshooting output — attach structured JSON to a support ticket when diagnosing access errors:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json",
+        "Environment cleanup — reverse a previous configure when decommissioning a sandbox:\n<%= config.bin %> <%= command.id %> --target-org myOrg --unconfigure"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "The Salesforce org to check for profiling readiness. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "summary": "Override the Salesforce API version for readiness checks. Use this when troubleshooting version-specific behavior or testing against a specific API release.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "configure": {
+          "char": "c",
+          "exclusive": [
+            "unconfigure"
+          ],
+          "name": "configure",
+          "summary": "Resolve configuration gaps in one step. Assigns the required permission set via REST API and enables API-Based Profiling via Metadata API deployment. Idempotent — safe to run when already configured. Blocked in production orgs (Developer Edition, sandbox, scratch, and trial only).",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "unconfigure": {
+          "exclusive": [
+            "configure",
+            "dry-run"
+          ],
+          "hidden": true,
+          "name": "unconfigure",
+          "summary": "Reverse a previous --configure by removing the permission set assignment and disabling API-Based Profiling on the Configuration Profile. Use this when decommissioning an environment or cleaning up access after testing.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview what --configure would change, applied to nothing. Shows which permission set would be assigned and which Configuration Profile settings would be enabled. Use this in regulated environments to document changes for approval before execution. Implies --configure.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:user:details",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Check whether the authenticated user is configured for profiling and resolve gaps — two configuration touchpoints verified and fixed in one command.",
+      "enableJsonFlag": true,
+      "skipAccessGate": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "user",
+        "details.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:user:details",
+        "user:cuneiform:details",
+        "user:details:cuneiform",
+        "cuneiform:details:user",
+        "details:cuneiform:user",
+        "details:user:cuneiform"
+      ]
+    },
+    "cuneiform:profile:request:cancel": {
+      "aliases": [],
+      "args": {},
+      "description": "When profiling is triggered, the system creates a request record that tracks execution. Requests begin in a Queued state, waiting for the backend to process them. This command transitions queued requests to Canceled status before processing begins — preventing them from generating summaries that would need to be identified and cleaned up later.\n\nIMPORTANT: Cancel applies to QUEUED requests only. Once a request has been processed and its summary is actively executing, the request is complete. To halt an in-progress summary, use `sf cuneiform summary stop` instead.\n\nTWO SELECTION MODES (mutually exclusive):\n\n- **Broad** (`--all`) — Cancel all cancellable requests (Queued status)\n- **Targeted** (`--request-ids`) — Cancel specific requests by Salesforce record ID\n\nSAFETY: Completed, rejected, and already-canceled requests are automatically excluded. Use --dry-run to preview what would be canceled before committing. A confirmation prompt shows the count before proceeding — use --no-prompt to skip for scripted use.\n\nCancellation transitions status only — it does not delete records. Canceled requests remain visible in `profile request list` until permanently removed with `profile request delete`.\n\nCANCEL vs STOP — these address different objects at different lifecycle stages:\n\n- **Cancel** prevents a Request from being processed. No Summary is created.\n- **Stop** halts an active Summary that is already executing. Preserves completed fields.\n\nBy the time a Summary exists, its originating Request is already complete. These operations do not overlap.\n\nWHEN TO USE:\n\n- Wrong definition submitted — cancel the queued request before it generates incorrect results\n- Pre-maintenance window — clear the queue before planned downtime\n- Configuration issue discovered — pause processing until the issue is resolved\n- Selective cleanup in shared orgs — cancel specific requests by ID while preserving valid requests\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"cancel everything in the queue\" → --all\n\"cancel just this one request\" → --request-ids a0Xxx0000001AAA\n\"what would be canceled?\" → --all --dry-run\n\"cancel without asking\" → --all --no-prompt\n\nCOMMAND SEQUENCE:\n`profile` or `profile request list` → **`profile request cancel`** → `profile request delete` (remove artifacts) or re-submit with corrected parameters",
+      "examples": [
+        "Preview what would be canceled — verify scope before committing:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Cancel all queued requests — clear the processing queue before maintenance:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all",
+        "Cancel specific requests by ID — targeted cancellation in shared orgs:\n<%= config.bin %> <%= command.id %> --target-org myOrg --request-ids a0Xxx0000001AAA,a0Xxx0000002BBB",
+        "Cancel immediately for scripted workflows:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --no-prompt",
+        "Cancel specific requests as JSON output for automation:\n<%= config.bin %> <%= command.id %> --target-org myOrg --request-ids a0Xxx0000001AAA --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Cancel profiling requests in this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "exclusive": [
+            "request-ids"
+          ],
+          "name": "all",
+          "summary": "Cancel all queued requests in a single operation. Use for pre-maintenance windows, configuration corrections, or full queue pauses when processing should be deferred. Mutually exclusive with --request-ids.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "request-ids": {
+          "char": "i",
+          "exclusive": [
+            "all"
+          ],
+          "name": "request-ids",
+          "summary": "Cancel specific profiling requests by Salesforce record ID (comma-separated). Use for targeted cancellation when only some queued requests are problematic — preserving valid requests in shared environments. Find request IDs with `profile request list`. Mutually exclusive with --all.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview which requests would be canceled, showing the same request details as a real cancellation. Use first in production orgs or shared environments to verify scope before committing — particularly important when other users have valid requests in the queue.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and cancel immediately. Use in scripts or automation where interactive prompts are not available. JSON mode also skips the prompt.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:profile:request:cancel",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Transition queued profiling requests to Canceled status before they begin processing — prevent incorrect or unnecessary requests from generating summaries.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "E4903": "errors.invalidIds",
+        "E4904": "errors.noCancellable",
+        "E4902": "errors.cancelFailed",
+        "E4905": "errors.partialFailure"
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "profile",
+        "request",
+        "cancel.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:profile:request:cancel",
+        "profile:cuneiform:request:cancel",
+        "profile:request:cuneiform:cancel",
+        "profile:request:cancel:cuneiform",
+        "cuneiform:request:profile:cancel",
+        "request:cuneiform:profile:cancel",
+        "request:profile:cuneiform:cancel",
+        "request:profile:cancel:cuneiform",
+        "cuneiform:request:cancel:profile",
+        "request:cuneiform:cancel:profile",
+        "request:cancel:cuneiform:profile",
+        "request:cancel:profile:cuneiform",
+        "cuneiform:profile:cancel:request",
+        "profile:cuneiform:cancel:request",
+        "profile:cancel:cuneiform:request",
+        "profile:cancel:request:cuneiform",
+        "cuneiform:cancel:profile:request",
+        "cancel:cuneiform:profile:request",
+        "cancel:profile:cuneiform:request",
+        "cancel:profile:request:cuneiform",
+        "cuneiform:cancel:request:profile",
+        "cancel:cuneiform:request:profile",
+        "cancel:request:cuneiform:profile",
+        "cancel:request:profile:cuneiform"
+      ]
+    },
+    "cuneiform:profile:request:delete": {
+      "aliases": [],
+      "args": {},
+      "description": "Every profiling run begins with a request record that tracks who initiated profiling, which definition was targeted, and the execution outcome. Canceled and rejected requests are terminal — they never produced a summary and serve no ongoing purpose. This command permanently removes them.\n\nELIGIBLE STATUSES: Only Canceled and Rejected requests can be deleted. The eligibility filter is enforced at the query level — Queued and Completed requests are structurally excluded.\n\nPROTECTED STATUSES: Completed requests maintain the profiling user context reference needed for reprofiling. They are cascade-deleted automatically when their summary is purged via `summary purge`. Queued requests must be canceled first with `profile request cancel` before they become eligible for deletion.\n\nTWO SELECTION MODES (mutually exclusive):\n\n- **Broad** (`--all`) — Delete all deletable requests (Canceled and Rejected)\n- **Targeted** (`--request-ids`) — Delete specific requests by Salesforce record ID\n\nLIFECYCLE CONTEXT: Delete removes terminal, summary-less requests:\n\n1. `profile request cancel` — transition queued requests to Canceled status\n2. `profile request delete` — permanently remove Canceled and Rejected requests\n3. `summary purge` — cascade-deletes Completed requests automatically\n\nWHEN TO USE:\n\n- Post-cancellation cleanup — remove canceled request artifacts after resolving the issue\n- Engagement close-out — clean up the request history before org handoff\n- Periodic housekeeping — remove old canceled and rejected requests to keep the request list focused\n- CI pipeline reset — automate scratch org cleanup between test runs\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"delete all processed requests\" → --all\n\"delete just this one request\" → --request-ids a0Xxx0000001AAA\n\"what would be deleted?\" → --all --dry-run\n\"delete without asking\" → --all --no-prompt\n\nCOMMAND SEQUENCE: `profile request cancel` (cancel queued requests) → `profile request delete` (remove canceled/rejected) → `summary purge` (remove summaries, cascade-delete completed requests) → `definition purge` (remove definitions)",
+      "examples": [
+        "Preview what would be deleted (deletion is permanent — always preview first):\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --dry-run",
+        "Delete all canceled and rejected requests after resolving the underlying issues:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all",
+        "Delete specific requests by ID for targeted cleanup:\n<%= config.bin %> <%= command.id %> --target-org myOrg --request-ids a0Xxx0000001AAA,a0Xxx0000002BBB",
+        "Scripted scratch org reset in CI pipelines:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --no-prompt",
+        "Capture deletion results as JSON for engagement close-out documentation:\n<%= config.bin %> <%= command.id %> --target-org myOrg --all --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Salesforce org containing the profiling requests to delete. The command validates Cuneiform installation before executing.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "all": {
+          "char": "a",
+          "exclusive": [
+            "request-ids"
+          ],
+          "name": "all",
+          "summary": "Delete all deletable requests (Canceled and Rejected status). Targets request artifacts that never produced summaries. Completed requests are excluded — they are cascade-deleted when their summary is purged. Mutually exclusive with --request-ids.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "request-ids": {
+          "char": "i",
+          "exclusive": [
+            "all"
+          ],
+          "name": "request-ids",
+          "summary": "Specific profiling request IDs to delete (e.g., --request-ids a0Xxx0000001AAA,a0Xxx0000002BBB). Targets individual canceled or rejected requests. Look up request IDs with `profile request list`. Mutually exclusive with --all.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "dry-run": {
+          "char": "d",
+          "name": "dry-run",
+          "summary": "Preview what would be deleted without making changes. Shows the same request details and counts as a real deletion. Use this first — deletion is permanent and cannot be undone.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "y",
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and delete immediately. Use for scripted cleanup in CI pipelines and automation workflows. The irreversibility warning is bypassed — the caller accepts permanent deletion programmatically.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:profile:request:delete",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Permanently remove canceled and rejected profiling requests — cleaning up terminal request artifacts that never produced a summary.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "ERROR_CODE_MAP": {
+        "E4903": "errors.invalidIds",
+        "E4908": "errors.noDeletable",
+        "E4906": "errors.deleteFailed",
+        "E4909": "errors.partialFailure"
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "profile",
+        "request",
+        "delete.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "cuneiform:profile:request:delete",
+        "profile:cuneiform:request:delete",
+        "profile:request:cuneiform:delete",
+        "profile:request:delete:cuneiform",
+        "cuneiform:request:profile:delete",
+        "request:cuneiform:profile:delete",
+        "request:profile:cuneiform:delete",
+        "request:profile:delete:cuneiform",
+        "cuneiform:request:delete:profile",
+        "request:cuneiform:delete:profile",
+        "request:delete:cuneiform:profile",
+        "request:delete:profile:cuneiform",
+        "cuneiform:profile:delete:request",
+        "profile:cuneiform:delete:request",
+        "profile:delete:cuneiform:request",
+        "profile:delete:request:cuneiform",
+        "cuneiform:delete:profile:request",
+        "delete:cuneiform:profile:request",
+        "delete:profile:cuneiform:request",
+        "delete:profile:request:cuneiform",
+        "cuneiform:delete:request:profile",
+        "delete:cuneiform:request:profile",
+        "delete:request:cuneiform:profile",
+        "delete:request:profile:cuneiform"
+      ]
+    },
+    "cuneiform:profile:request:list": {
+      "aliases": [],
+      "args": {},
+      "description": "Profiling requests are the execution records of the KYCD journey — each one tracks who submitted profiling, against which definition, and the outcome. This command retrieves those records and displays them as a six-column table: request name, status, target object, parent definition name, submitted by (user), and created date.\n\nThe command is read-only. For cancelling queued requests, use `profile request cancel`. For deleting terminal requests, use `profile request delete`.\n\nLIFECYCLE CONTEXT: Profiling requests are created when `sf cuneiform profile` runs. Each request starts as Queued and ends in one of three terminal states: Completed (summary created and executing independently), Rejected (validation failed or capacity exceeded), or Canceled (user stopped it before processing). There are exactly 4 request statuses.\n\nWHEN TO USE:\n\n- After submitting profiling — \"Did my requests complete? Are they still queued?\"\n- To triage rejections — filter by Rejected status to isolate problematic requests\n- For multi-user coordination — the submitted-by column shows who triggered each request\n- To check queue depth — see how many requests are waiting to be processed\n\nRELATED COMMANDS:\n\n- `sf cuneiform profile` — creates the requests this command lists\n- `sf cuneiform profile request cancel` — cancel queued requests that should not be processed\n- `sf cuneiform profile request delete` — permanently remove processed requests\n- `sf cuneiform definition get` — check profiling results at the definition level\n\nNATURAL LANGUAGE → FLAG MAPPING:\n\"show me all requests\" → (no flags, lists all)\n\"what's still queued?\" → --status Queued\n\"were any rejected?\" → --status Rejected\n\"show canceled requests\" → --status Canceled\n\"show more results\" → --limit 100\n\nCOMMAND SEQUENCE:\n`profile` → **`profile request list`** → `profile request cancel` or `summary stop` (when intervention is needed)",
+      "examples": [
+        "List all profiling requests — monitor progress after submitting profiling:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "Triage rejected requests — isolate requests that need attention:\n<%= config.bin %> <%= command.id %> --target-org myOrg --status Rejected",
+        "Check queue depth — see how many requests are waiting for processing:\n<%= config.bin %> <%= command.id %> --target-org myOrg --status Queued",
+        "Confirm completed requests — verify which requests produced summaries:\n<%= config.bin %> <%= command.id %> --target-org myOrg --status Completed",
+        "View more results in a large profiling run:\n<%= config.bin %> <%= command.id %> --target-org myOrg --limit 100",
+        "Produce machine-readable output for scripting or dashboards:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Retrieve profiling requests from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "status": {
+          "char": "s",
+          "name": "status",
+          "summary": "Filter by request lifecycle status: Queued (waiting to be processed), Completed (summary created and executing), Rejected (validation failed or capacity exceeded), or Canceled (stopped before processing). There are exactly 4 valid values. Use --status Rejected for triage or --status Queued to check queue depth.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "Queued",
+            "Canceled",
+            "Completed",
+            "Rejected"
+          ],
+          "type": "option"
+        },
+        "limit": {
+          "char": "l",
+          "name": "limit",
+          "summary": "Control how many requests are displayed per page (default: 25, max: 200). Increase for large profiling runs where 25 results may not show the full picture.",
+          "default": 25,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "cuneiform:profile:request:list",
+      "pluginAlias": "@peernova/cuneiform-sf",
+      "pluginName": "@peernova/cuneiform-sf",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Retrieve profiling request execution records — see which requests are queued, completed, rejected, or canceled across the org.",
+      "enableJsonFlag": true,
+      "skipAccessGate": false,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "cuneiform",
+        "profile",
+        "request",
+        "list.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hello:world",
-        "world:hello"
+        "cuneiform:profile:request:list",
+        "profile:cuneiform:request:list",
+        "profile:request:cuneiform:list",
+        "profile:request:list:cuneiform",
+        "cuneiform:request:profile:list",
+        "request:cuneiform:profile:list",
+        "request:profile:cuneiform:list",
+        "request:profile:list:cuneiform",
+        "cuneiform:request:list:profile",
+        "request:cuneiform:list:profile",
+        "request:list:cuneiform:profile",
+        "request:list:profile:cuneiform",
+        "cuneiform:profile:list:request",
+        "profile:cuneiform:list:request",
+        "profile:list:cuneiform:request",
+        "profile:list:request:cuneiform",
+        "cuneiform:list:profile:request",
+        "list:cuneiform:profile:request",
+        "list:profile:cuneiform:request",
+        "list:profile:request:cuneiform",
+        "cuneiform:list:request:profile",
+        "list:cuneiform:request:profile",
+        "list:request:cuneiform:profile",
+        "list:request:profile:cuneiform"
       ]
     }
   },
-  "version": "1.0.2"
+  "version": "1.0.4-beta.8"
 }