@docusign/cli 1.0.1-rc → 1.2.0-rc

package/dist/templates/ai-skills/.claude/skills/ds-agm-autopilot/SKILL.md

@@ -403,7 +403,7 @@ I need values for <N> documents. Which fields do you want to populate?
 (Tip: you don't need to fill all columns — just what matters for your use case)
 
 Common metadata fields to fill:
-  • Salesforce ID (or other external system ID)
+  • Salesforce or other external-system linked records
   • Any fields that can't be AI-extracted from the document content
 
 Options:
@@ -417,6 +417,15 @@ Options:
 Which approach?
 ```
 
+For linked external records, use the exact `linked_data` column generated after `Filename`. Put the complete API array in one cell; do not create indexed columns such as `linked_data[0]` or `linked_data[0].application_name`. Leave the cell blank when the document has no linked records.
+
+```csv
+Filename,linked_data
+agreement.pdf,"[{""application_name"":""Salesforce"",""object_name"":""Opportunity"",""record_id"":""006xx000001abc""}]"
+```
+
+Multiple linked records belong in the same JSON array. Preserve the exact snake_case property names `application_name`, `object_name`, and `record_id`.
+
 **If A — inline collection:**
 
 ```
@@ -424,7 +433,9 @@ Enter values for each document.
 Format: one line per field, or a full row, or a paste from a spreadsheet.
 
   film_deal_001.html
-    Salesforce ID : _______________
+    Linked application name : _______________
+    Linked object name      : _______________
+    Linked record ID        : _______________
     [other fields the user chose]
 
   film_deal_002.html

package/dist/templates/ai-skills/.claude/skills/ds-agreement-manager-workflow/SKILL.md

@@ -188,12 +188,23 @@ ds agm ingest --directory ./agreement-manager/files/test --recursive -y
 
 # Preview
 ds agm ingest --directory ./agreement-manager/files/test --dry-run
+
+# Generate and then ingest with metadata
+ds agm ingest --directory ./agreement-manager/files/test --generate-metadata-template
+ds agm ingest --directory ./agreement-manager/files/test --with-metadata -y
 ```
 
 **Supported formats:** PDF, DOCX, DOC, HTML, XLSX, XLS, XLSB, PPTX, PPT, PPSX, RTF, JPG, PNG, TIF
 
 Tracked in `agreement-manager/files/tracking.json` to prevent duplicate ingestion.
 
+The generated `agreement-manager/metadata/metadata.csv` includes an optional `linked_data` column. Enter the complete Agreement Manager API array as JSON in that cell; do not use indexed headers such as `linked_data[0]`:
+
+```csv
+Filename,linked_data
+agreement.pdf,"[{""application_name"":""Salesforce"",""object_name"":""Opportunity"",""record_id"":""006xx000001abc""}]"
+```
+
 ---
 
 ## Step 7: Generate Test Template

package/dist/templates/ai-skills/.github/instructions/docusign.instructions.md

@@ -15,6 +15,8 @@ ds agm get catalog                                     # Fetch standard types/fi
 ds agm validate                                        # Validate manifest
 ds agm upload [-y|--dry-run]                           # Deploy manifest
 ds agm ingest --directory <path> [-y|--dry-run]        # Ingest documents
+ds agm ingest --directory <path> --generate-metadata-template  # Create metadata.csv
+ds agm ingest --directory <path> --with-metadata -y    # Validate and ingest metadata
 ds agm test generate-test-template [-y] [--prefill-extractions]  # Create test CSV
 ds agm test run [-y] [--partial-match]                 # Run extraction tests
 ```
@@ -33,6 +35,7 @@ ds agm test run [-y] [--partial-match]                 # Run extraction tests
         │   ├── tracking.json                          # Ingestion tracker
         │   ├── standard-catalog.json                  # After 'get catalog'
         │   └── custom-catalog.json
+        ├── metadata/metadata.csv                      # Optional ingest metadata
         ├── tests/testing.csv                          # Test expectations
         └── output/                                    # Test results
 ```
@@ -53,6 +56,17 @@ To drive the full Agreement Manager lifecycle interactively, invoke the `ds-agm-
 8. Fill expected values in `agreement-manager/tests/testing.csv`
 9. `ds agm test run -y`
 
+## Linked Data Metadata
+
+The generated `agreement-manager/metadata/metadata.csv` includes the exact reserved column `linked_data`. Put the complete API array in one CSV cell and leave it blank when no linked records apply:
+
+```csv
+Filename,linked_data
+agreement.pdf,"[{""application_name"":""Salesforce"",""object_name"":""Opportunity"",""record_id"":""006xx000001abc""}]"
+```
+
+Do not use indexed columns such as `linked_data[0]` or `linked_data[0].application_name`. Multiple linked records belong in the same array. Use the exact snake_case keys `application_name`, `object_name`, and `record_id`.
+
 ## Manifest Rules
 
 **Custom field `key`** must start with `C_` (e.g., `C_TerminationDate`). Use `displayName` for human-readable name. Add `aiDefinition` when `customExtractionEnabled: true`.

package/dist/templates/package/README.md

@@ -0,0 +1,25 @@
+# Package Feature
+
+This directory contains files for managing DocuSign packages in this project.
+
+## Directory Structure
+
+- **files/**: Package content files to include in your packages
+
+## Getting Started
+
+### Create a package
+
+```bash
+ds package create --name=my-package
+```
+
+### Get help
+
+```bash
+ds package -h
+```
+
+## About Packages
+
+Packages allow you to bundle and distribute your DocuSign configurations and assets. Each package has a unique ID assigned by the server. Names do not need to be unique — use descriptive names to identify packages by purpose.

package/dist/templates/packages/README.md

@@ -0,0 +1,59 @@
+# Packages Feature
+
+This directory contains the Packages feature for managing and distributing packages.
+
+## Directory Structure
+
+```
+packages/
+├── configs/             # Package configuration files
+├── files/
+│   ├── train/          # Training/example package files
+│   └── test/           # Test package files
+├── tests/              # Package tests and validation scripts
+└── README.md
+```
+
+## Getting Started
+
+### 1. Configure Your Packages
+
+Create package configuration files in `configs/`. These define:
+
+- Package metadata (name, version, description)
+- Package dependencies
+- Package contents and structure
+- Distribution settings
+
+### 2. Add Package Files
+
+Organize your package files in `files/`:
+
+- **files/train/**: Example or template package files
+- **files/test/**: Test packages for validation
+
+### 3. Define Tests
+
+Add test scripts and validation rules to `tests/` to ensure package quality and correctness.
+
+## Workflow
+
+1. **Create** package configurations in `configs/`
+2. **Organize** package files in `files/`
+3. **Define** validation tests in `tests/`
+4. **Validate** packages using the appropriate commands
+5. **Distribute** packages as needed
+
+## Tips
+
+- Keep package configurations modular and reusable
+- Use semantic versioning for package versions
+- Include clear documentation in package metadata
+- Test packages thoroughly before distribution
+- Version control your configurations for tracking changes
+
+## Next Steps
+
+- Configure your first package in `configs/`
+- Add example files to `files/train/`
+- Create validation tests in `tests/`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@docusign/cli",
-  "version": "1.0.1-rc",
+  "version": "1.2.0-rc",
   "author": "Docusign",
   "description": "The Docusign CLI simplifies the implementation of Docusign Agreement Manager. With this CLI, you can bulk configure Agreement Manager with custom fields and types, map fields to types, provide AI training sets for custom extractions, programmatically test extraction accuracy, and export/import your setup across accounts. This offering is currently in beta.",
   "main": "dist/index.mjs",