agent-docs 1.0.2 → 1.2.0

package/PLAN.md

@@ -11,8 +11,8 @@ AI agent instruction documents ("docs") for AI-enabled IDEs.
 - **Primary contents**: Markdown documentation in `docs/`
 - **Code formatting**: Prettier (via `pnpm format` / `pnpm format:check`)
 - **CI**: GitHub Actions workflow that runs `pnpm format:check` on push/PR
-- **Postinstall script**: `postinstall.mjs` that creates symlinks/junctions to
-  `docs/` in consuming projects
+- **Postinstall script**: `postinstall.mjs` that copies the `docs/` directory to
+  consuming projects if they don't already have one
 - **AI Agent Guidance**: `.cursor/plans/` contains structured workflows and
   instructions for AI coding assistants
 - **IDE Rules**: `.cursor/rules/` contains agent rules for Cursor IDE
@@ -52,19 +52,15 @@ The README.md should contain:
         - When `agent-docs` is installed into another project, a `postinstall`
           script will run in the consuming project.
         - If the consuming project does **not** already have a `docs/`
-          directory, the script will create a single symlink/junction from the
-          consuming project's `docs/` directory to this package's `docs/`
-          directory:
-            - On Unix/macOS, a directory symlink is created
-            - On Windows, a junction is created
+          directory, the script will copy this package's `docs/` directory to
+          the consuming project's root directory.
         - If the consuming project **already has** a `docs/` directory, the
-          script does nothing and you can instead manage your own docs layout.
-    - Optional manual instructions for symlinking (Unix/macOS) or junction
-      linking (Windows) if you prefer not to rely on `postinstall`, or need a
-      custom layout:
-        - Individual files from the `docs/` folder to the root of the actual
-          project, OR
-        - The entire `docs` folder to the root of the actual project
+          script does nothing, and your existing docs layout is left unchanged.
+    - Optional manual instructions for copying files if you prefer not to rely
+      on `postinstall`, or need a custom layout:
+        - Copy individual files from the `docs/` folder to the root of the
+          actual project, OR
+        - Copy the entire `docs` folder to the root of the actual project
     - Explanation of how to update IDE agent rules (e.g., Cursor's
       `.cursor/rules/` or similar) to reference the linked docs using
       `@filename` syntax or relative paths, so the AI agent can access the
@@ -369,13 +365,14 @@ Add any other context, examples, or screenshots about the feature request here.
 ### `postinstall.mjs`
 
 The postinstall script that runs when this package is installed in another
-project. It should copy this package's `docs/` directory to the consuming
-project's root directory, but only if the consuming project doesn't already have
-a `docs/` directory.
+project. It copies this package's `docs/` directory to the consuming project's
+root directory, but only if the consuming project doesn't already have a `docs/`
+directory. The script uses file copying instead of symlinks/junctions for better
+cross-platform reliability.
 
 ```js
 // postinstall.mjs
-// Implementation details for creating cross-platform symlinks/junctions
+// Implementation details for copying docs directory cross-platform
 ```
 
 ### `prettier.config.js`
@@ -610,7 +607,7 @@ Standard MIT license with copyright holder: starch-uk
 
 - Name: `agent-docs`
 - Type: module
-- Version: `1.0.0`
+- Version: `1.1.0` (current)
 - Scripts: `format`, `format:fix`, `format:check`, `postinstall`
 - Dev dependencies: `prettier`
 - Engines: Node.js >= 20.0.0
@@ -640,16 +637,16 @@ The plan should:
     - **Major version bump** - Sections replaced or removed from a file compared
       to the version in the latest commit in the `main` branch
 - Document that the project as a whole maintains a version in `package.json`
-  (currently `1.0.0`)
+  (currently `1.1.0`)
 - Explain that changes to docs files should increment the project version
   (patch/minor/major based on the greatest change in any docs file) compared to
   the version in the latest commit in the `main` branch
 - **Document initialization of existing docs:** The existing documentation files
-  in the `docs/` directory (APEXANNOTATIONS.md, APEXDOC.md, CODEANALYZER.md,
-  CPD.md, ESLINT.md, ESLINTJSDOC.md, FLOWSCANNER.md, GRAPHBINARY.md,
-  GRAPHENGINE.md, GRAPHML.md, GRAPHSON.md, GREMLIN.md, GRYO.md, HUSKY.md,
-  JEST30.md, JORJE.md, JSDOC.md, PMD.md, PMDAPEXAST.md, PMDSUPPRESSWARNINGS.md,
-  PNPM.md, PRETTIER.md, PRETTIERAPEX.md, REGEX.md, RETIREJS.md, SFCLI.md,
+  in the `docs/` directory (A4DRULES.md, A4DWORKFLOWS.md, APEXANNOTATIONS.md,
+  APEXDOC.md, CML.md, CODEANALYZER.md, CONTEXTDEFINITIONS.md, ESLINT.md,
+  ESLINTJSDOC.md, FIELDSERVICE.md, GRAPHBINARY.md, GRAPHENGINE.md, GRAPHML.md,
+  GRAPHSON.md, GREMLIN.md, GRYO.md, HUSKY.md, JEST.md, JORJE.md, JSDOC.md,
+  PMD.md, PNPM.md, PRETTIER.md, PRETTIERAPEX.md, REVENUETRANSACTIONMANAGEMENT.md,
   TINKERPOP.md, VITEST.md, XPATH31.md) need to be initialized with version
   `1.0.0` (or appropriate version based on their current state) when the
   versioning system is first implemented. These existing docs will be tracked

package/README.md

@@ -76,6 +76,8 @@ with any technology.
 The `docs/` directory contains generated documentation files. Each doc follows a
 structured format optimized for AI agent consumption:
 
+- **[A4DRULES.md](docs/A4DRULES.md)** - Agentforce Rules Reference
+- **[A4DWORKFLOWS.md](docs/A4DWORKFLOWS.md)** - Agentforce Workflows reference
 - **[APEXANNOTATIONS.md](docs/APEXANNOTATIONS.md)** - Apex annotations reference
 - **[APEXDOC.md](docs/APEXDOC.md)** - ApexDoc documentation tool reference
 - **[CML.md](docs/CML.md)** - Constraint Modeling Language (CML) reference for
@@ -109,10 +111,58 @@ structured format optimized for AI agent consumption:
 - **[TINKERPOP.md](docs/TINKERPOP.md)** - Apache TinkerPop graph computing
   framework reference
 - **[VITEST.md](docs/VITEST.md)** - Vitest testing framework reference
-- **[CODEANALYZER.md#vs-code-integration](docs/CODEANALYZER.md#vs-code-integration)** -
-  VS Code editor integration
 - **[XPATH31.md](docs/XPATH31.md)** - XPath 3.1 query language reference
 
+## Usage
+
+### Creating and Maintaining Docs
+
+To create new documentation files:
+
+1. **Create a new markdown file** in the `docs/` directory following the naming
+   convention:
+    - Uppercase, no spaces, no dots
+    - Version numbers become part of the name (e.g., "XPath 3.1" → `XPATH31.md`)
+    - Remove redundant words like "plugin" when they appear between other words
+      (e.g., "prettier-plugin-apex" → `PRETTIERAPEX.md`)
+
+2. **Follow the structured format** optimized for AI agent consumption:
+    - Overview section with brief context
+    - Core Concepts / Key Features (bulleted lists)
+    - Configuration / Setup (tables when possible)
+    - Usage / Examples (minimal, essential code only)
+    - API Reference (condensed, often in tables)
+    - Patterns & Best Practices
+    - Important Notes (critical gotchas, limitations)
+
+3. **Apply optimization guidelines**:
+    - Keep token count low - be terse but precise
+    - Use bullet points over prose for scannability
+    - Prefer tables for structured data (config options, APIs, properties)
+    - Include code snippets only when essential
+    - Cross-reference related docs using `[Name](FILENAME.md)` format
+    - Include a document in a prompt or rule with @FILENAME.md
+
+### AI Agent Guidance
+
+This repository includes AI Agent Guidance files in `.cursor/plans/` that
+provide structured instructions and workflows for AI coding assistants (like
+Cursor's Agent). These plan files document processes, best practices, and
+step-by-step workflows for various tasks, making them accessible to AI agents
+through the `.cursor/plans/` directory structure.
+
+When AI agents need guidance on how to perform specific tasks or follow certain
+workflows, they can reference these plan files to understand the expected
+process and provide accurate assistance. Key plan files include:
+
+- **VERSIONING.md** - Semantic versioning rules and workflows for documentation
+  files
+- **OPTIMISE.md** - Strategies and best practices for maintaining low token
+  counts and efficient documentation formats
+
+These plans are used by AI-powered IDEs to optimize docs and maintain
+consistency across the documentation set.
+
 ## Contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on contributing to this

package/docs/A4DRULES.md

@@ -0,0 +1,145 @@
+# Agentforce Rules Reference
+
+> **Version**: 1.0.0
+
+Purpose
+
+- Provide persistent system‑level guidance Agentforce follows during Salesforce
+  development.
+- Enforce coding, metadata, org and team conventions across sessions.
+
+Key concepts
+
+- Rules are persistent instructions that influence Agentforce behavior.
+- Two scopes:
+    - Global — companywide standards applied to all projects.
+    - Workspace — project/org specific; stored in the project’s .a4drules
+      folder.
+- Out‑of‑the‑box global rules exist and can be toggled; shipped rules may be
+  overwritten by extension updates.
+
+Where to manage
+
+- Open Rules & Workflows (justice icon) in Agentforce chat.
+- Create: click + in Rules tab or use `/newrule` in chat.
+- Popover UI: view active rules, enable/disable, add, delete.
+- Workspace rules: project/.a4drules. Global rules: OS‑dependent location.
+
+Minimal file template (low‑token)
+
+```text
+# Rule: [Name]
+
+Description: [one-line purpose]
+
+Applies to: `[file pattern]`
+
+Guidelines:
+- [short guideline 1]
+- [short guideline 2]
+```
+
+Rule design patterns
+
+- Scope: choose Global for org‑wide policies (naming, security) or Workspace for
+  repo/org specifics.
+- One file type per rule when possible to reduce ambiguity.
+- Keep guidelines short, precise, and actionable (3–6 lines is ideal).
+- Version‑gate rules for fields/features that require a minimum API version.
+
+Validation checklist pattern (use inside rules)
+
+- File suffix & location (e.g., `folder/*.ext`, include generated meta filenames
+  like `*.ext-meta.xml`).
+- Required fields present and follow naming/format rules.
+- Mutually exclusive fields: only one of a defined set is present.
+- Enumerations: value belongs to allowed list.
+- Numeric fields: in allowed range and type (int/float).
+- Cross‑field constraints (e.g., boolean toggle requires another field match).
+- API version: ensure package API supports any fields used.
+- Manifest behavior: wildcard support and retrieval side effects.
+
+Common guideline examples (generic)
+
+- File naming & location
+    - Suffix must match the metadata type (e.g., `.ext` and optionally
+      `.ext-meta.xml`) and files stored in the corresponding folder.
+
+- Identity / fullName rules
+    - fullName must use only letters, numbers and underscores; start with a
+      letter; no spaces; not end with `_`; not contain `__`; unique within
+      package.
+
+- Exclusive content fields
+    - Exactly one of [fieldA, fieldB, fieldC, fieldD] may be set. Enforce count
+      == 1.
+
+- Required / conditional fields
+    - FieldX is required.
+    - If FieldY = true then FieldZ must equal the related resource name.
+    - If FieldType ∈ {type1, type2} then NumericHeight must be present and > 0.
+
+- Enumerations & presets
+    - Validate enumerated fields against the allowed list (store the list
+      centrally in the rule).
+
+- API gating
+    - Only allow fields introduced in API ≥ N when package.xml version >= N.
+
+- Manifest & retrieval
+    - Support for wildcard (\*) in package.xml — note older API versions may
+      behave differently.
+    - Retrieving a component can cause related Profile/PermissionSet entries to
+      include references; warn about side effects.
+
+Example minimal templates
+
+- Generic metadata file template
+
+```xml
+<MetadataType xmlns="http://soap.sforce.com/2006/04/metadata">
+  <fullName>MyResource</fullName>
+  <requiredField>value</requiredField>
+  <optionalField>value</optionalField>
+</MetadataType>
+```
+
+- Example rule pseudocode checks
+
+```text
+# Rule: SingleContentField
+
+Description: Ensure exactly one content source is defined.
+
+Applies to: `**/*.ext`
+
+Guidelines:
+- Count([fieldA, fieldB, fieldC, fieldD]) == 1
+- If fieldC set -> ensure frameHeight is present and integer > 0
+- Package API version must be >= 14 when using iconField
+```
+
+Best practices
+
+- Make rules atomic and single‑purpose to simplify enforcement and debugging.
+- Prefer short lines and plain tokens to keep rules compact for AI processing.
+- Store enumerations centrally to avoid duplication and speed validation.
+- Version‑gate rules for fields that depend on API releases.
+- Test rule behavior by toggling and running typical retrieve/deploy scenarios.
+- Review and update rules whenever package/API versions or team conventions
+  change.
+
+Rule lifecycle checklist
+
+- Create: Name + one-line Description + Applies pattern.
+- Add 3–6 precise Guidelines (format/validators/version gates).
+- Save to workspace .a4drules or global rules UI.
+- Enable and test with representative metadata files and package.xml.
+
+Usage notes for agents
+
+- Apply rules as filters during generation and validation steps.
+- Prefer minimal, deterministic responses based on active rules.
+- When multiple rules conflict, enforce Global rules last modified earlier than
+  Workspace (or use a defined precedence ordering).
+- Emit succinct validation errors with line/field hints to aid quick fixes.

package/docs/A4DWORKFLOWS.md

@@ -0,0 +1,121 @@
+# Agentforce Workflows — Agent Guide
+
+> **Version**: 1.0.0
+
+## Overview
+
+Workflows are reusable `.md` files defining multi-step Salesforce dev tasks. Invoke with `/[workflow-name.md]` in chat.
+
+**Benefits:** Automation, consistency, error reduction, time savings, team sharing.
+
+---
+
+## Creating & Managing
+
+| Action | Method |
+|--------|--------|
+| Access | Click **Rules & Workflows** (justice icon) in chat |
+| Scope | Choose **Global** or **Workspace** workflows |
+| Create | Click **+** |
+| Storage | Workspace: `.a4drules/workflows/` folder |
+
+Interface allows: view active workflows, toggle on/off, add/delete.
+
+---
+
+## Workflow Capabilities
+
+- **Built-in tools:** `ask_followup_question`, `read_file`, `search_files`, `new_task`
+- **CLI tools:** `sf` (Salesforce CLI), `git`
+- **External:** MCP tool calls
+- **Chaining:** Sequential action execution
+
+---
+
+## Common Workflow Types
+
+| Type | Purpose |
+|------|---------|
+| Deployment | Deploy/validate components across orgs |
+| Testing | Run test suites, analyze results |
+| Release | Package, validate, deploy releases |
+| Component | Create/test/deploy Lightning components |
+| Integration | Set up/validate external integrations |
+
+---
+
+## Example: `salesforce-deploy.md`
+
+```text
+You have access to the `sf` terminal command. Deploy components following this process:
+
+1. **Gather Info**
+   <ask_followup_question>
+     <question>Which components to deploy and to which org?</question>
+     <options>["Specific files/folders", "All local changes", "Specific metadata types"]</options>
+   </ask_followup_question>
+   
+   sf org display --target-org <target-org>
+
+2. **Pre-Deployment Validation**
+   sf project retrieve start --dry-run --target-org <target-org>
+   sf apex test run --code-coverage --result-format human
+   sf project deploy start --dry-run --target-org <target-org>
+
+3. **Confirm**
+   <ask_followup_question>
+     <question>Validation complete. Proceed with deployment?</question>
+     <options>["Yes, deploy now", "No, make changes first", "Show details"]</options>
+   </ask_followup_question>
+
+4. **Execute**
+   sf project deploy start --target-org <target-org>
+   sf project deploy report --target-org <target-org>
+
+5. **Post-Validation**
+   sf apex test run --target-org <target-org> --code-coverage --result-format human
+```
+
+---
+
+## SF CLI Quick Reference
+
+### Org Commands
+```bash
+sf org list                              # List authorized orgs
+sf org display --target-org <alias>      # Display org info
+sf config set target-org <alias>         # Set default org
+```
+
+### Deployment
+```bash
+sf project deploy start --target-org <alias>            # Deploy
+sf project deploy start --dry-run --target-org <alias>  # Validate only
+sf project deploy report --target-org <alias>           # Check status
+sf project retrieve start --target-org <alias>          # Retrieve metadata
+```
+
+### Testing
+```bash
+sf apex test run --target-org <alias> --code-coverage --result-format human
+sf apex test run --class-names "Test1,Test2" --target-org <alias>
+sf apex test report --target-org <alias>
+```
+
+### Data
+```bash
+sf data query --query "SELECT Id FROM Account LIMIT 10" --target-org <alias>
+sf data import tree --plan data/plan.json --target-org <alias>
+sf data export tree --query "SELECT Id FROM Account" --target-org <alias>
+```
+
+---
+
+## Custom Workflow Ideas
+
+| Workflow | Key Steps |
+|----------|-----------|
+| **Release** | Gather merged changes → Build changelog → Bump version → Create/validate package |
+| **New Component** | Create folder structure → Generate boilerplate files → Set up Jest tests → Deploy to dev |
+| **Integration Test** | Validate credentials → Test endpoints → Check error handling → Generate reports |
+| **Code Quality** | Run PMD analysis → Check accessibility → Validate naming → Generate reports |

package/docs/REVENUETRANSACTIONMANAGEMENT.md

@@ -1,6 +1,6 @@
 # Salesforce Revenue Cloud: Transaction Management
 
-> v1.0.1 | Editions: Enterprise, Unlimited, Developer (Lightning Experience)
+> v1.0.2 | Editions: Enterprise, Unlimited, Developer (Lightning Experience)
 
 ## Quick Reference
 
@@ -106,12 +106,14 @@ configuration.
 | `RecordResource`                 | Create record object from sales transaction field values                                         |
 | `RecordWithReferenceRequest`     | Associate record object with reference identifier                                                |
 
-**ConfigurationOptionsInput Properties:** | Property | Type | Description |
-|----------|------|-------------| | `addDefaultConfiguration` | Boolean |
-Auto-add default configuration (bundle/product attributes) | |
-`executeConfigurationRules` | Boolean | Require adherence to configuration rules
-| | `validateAmendRenewCancel` | Boolean | Run amend/renew/cancel validations |
-| `validateProductCatalog` | Boolean | Validate against product catalog |
+**ConfigurationOptionsInput Properties:**
+
+| Property                    | Type    | Description                                                |
+| --------------------------- | ------- | ---------------------------------------------------------- |
+| `addDefaultConfiguration`   | Boolean | Auto-add default configuration (bundle/product attributes) |
+| `executeConfigurationRules` | Boolean | Require adherence to configuration rules                   |
+| `validateAmendRenewCancel`  | Boolean | Run amend/renew/cancel validations                         |
+| `validateProductCatalog`    | Boolean | Validate against product catalog                           |
 
 **PlaceSalesTransactionExecutor.execute() Parameters:**
 
@@ -124,34 +126,39 @@ Auto-add default configuration (bundle/product attributes) | |
 - `catalogRatesPreferenceEnum` (CatalogRatesPreferenceEnum) — Rate card entries
   preference (optional)
 
-**Enums:** | Enum | Values | Description | |------|--------|-------------| |
-`CatalogRatesPreferenceEnum` | `Fetch`, `Skip` | Rate card entries for
-usage-based selling | | `ConfigurationExecutionEnum` | `RunAndAllowErrors`,
-`RunAndBlockErrors`, `Skip` | Configuration execution mode | |
-`PricingPreferenceEnum` | `Force`, `Skip`, `System` | Pricing preference during
-transaction |
+**Enums:**
+
+| Enum                         | Values                                           | Description                               |
+| ---------------------------- | ------------------------------------------------ | ----------------------------------------- |
+| `CatalogRatesPreferenceEnum` | `Fetch`, `Skip`                                  | Rate card entries for usage-based selling |
+| `ConfigurationExecutionEnum` | `RunAndAllowErrors`, `RunAndBlockErrors`, `Skip` | Configuration execution mode              |
+| `PricingPreferenceEnum`      | `Force`, `Skip`, `System`                        | Pricing preference during transaction     |
 
 ### CommerceTax
 
 Manages communication between Salesforce and external tax engines.
 
-**Classes:** | Class | Purpose | |-------|---------| | `AddressesResponse` |
-Ship To, Ship From, Sold To address responses | | `AmountDetailsResponse` | Tax
-amount, total with tax, exempt amount | | `CustomTaxAttributesResponse` |
-Additional custom tax attributes | | `DocumentCodeRequest` | Document code for
-tax calculation | | `ExemptDetailsResponse` | Exemption ID, number, reason | |
-`ImpositionResponse` | Tax imposition details (id, name, type, subType) | |
-`JurisdictionResponse` | Tax jurisdiction (country, region, state, level) | |
-`LineItemResponse` | Line item tax calculation results | |
-`LineTaxAddressesRequest` | Per-line-item addresses for tax calculation | |
-`RuleDetailsResponse` | Tax rules used (nonTaxableRuleId, rateRuleId,
-rateSourceId) | | `TaxAddressesRequest` | Ship From/To, Sold To, Bill To
-addresses | | `TaxAddressRequest` | Address details (city, country, state,
-postalCode, lat/long) | | `TaxApiException` | Tax calculation exceptions | |
-`TaxCustomerDetailsRequest` | Customer details (accountId, code,
-exemptionNo/Reason) | | `TaxDetailsResponse` | Tax calculation details per line
-| | `TaxEngineRequest` | Tax engine request payload | | `TaxEngineResponse` |
-Tax engine response |
+**Classes:**
+
+| Class                         | Purpose                                                      |
+| ----------------------------- | ------------------------------------------------------------ |
+| `AddressesResponse`           | Ship To, Ship From, Sold To address responses                |
+| `AmountDetailsResponse`       | Tax amount, total with tax, exempt amount                    |
+| `CustomTaxAttributesResponse` | Additional custom tax attributes                             |
+| `DocumentCodeRequest`         | Document code for tax calculation                            |
+| `ExemptDetailsResponse`       | Exemption ID, number, reason                                 |
+| `ImpositionResponse`          | Tax imposition details (id, name, type, subType)             |
+| `JurisdictionResponse`        | Tax jurisdiction (country, region, state, level)             |
+| `LineItemResponse`            | Line item tax calculation results                            |
+| `LineTaxAddressesRequest`     | Per-line-item addresses for tax calculation                  |
+| `RuleDetailsResponse`         | Tax rules used (nonTaxableRuleId, rateRuleId, rateSourceId)  |
+| `TaxAddressesRequest`         | Ship From/To, Sold To, Bill To addresses                     |
+| `TaxAddressRequest`           | Address details (city, country, state, postalCode, lat/long) |
+| `TaxApiException`             | Tax calculation exceptions                                   |
+| `TaxCustomerDetailsRequest`   | Customer details (accountId, code, exemptionNo/Reason)       |
+| `TaxDetailsResponse`          | Tax calculation details per line                             |
+| `TaxEngineRequest`            | Tax engine request payload                                   |
+| `TaxEngineResponse`           | Tax engine response                                          |
 
 **TaxAddressRequest Properties:** `city`, `country`, `countryCode`, `latitude`,
 `locationCode`, `longitude`, `postalCode`, `state`, `stateCode`, `street`
@@ -169,10 +176,13 @@ Tax engine response |
 - `RecordResource` — Create record from quote field values
 - `RecordWithReferenceRequest` — Associate record with reference ID
 
-**Enums:** | Enum | Values | |------|--------| | `CatalogRatesPreferenceEnum` |
-`Fetch`, `Skip` | | `ConfigurationInputEnum` | `RunAndAllowErrors`,
-`RunAndBlockErrors`, `Skip` | | `PricingPreferenceEnum` | `Force`, `Skip`,
-`System` |
+**Enums:**
+
+| Enum                         | Values                                           |
+| ---------------------------- | ------------------------------------------------ |
+| `CatalogRatesPreferenceEnum` | `Fetch`, `Skip`                                  |
+| `ConfigurationInputEnum`     | `RunAndAllowErrors`, `RunAndBlockErrors`, `Skip` |
+| `PricingPreferenceEnum`      | `Force`, `Skip`, `System`                        |
 
 ---
 

package/docs/XPATH31.md

@@ -1,4 +1,3 @@
-````markdown
 # XPath 3.1 Reference
 
 > **Version**: 1.0.0
@@ -207,7 +206,3 @@ $seq ! (./child/@attr)   # apply to each, flatten
 - Document order preserved
 - Namespaces: prefixes or `Q{uri}local`
 - Errors: `try/catch` in 3.1
-
-```
-
-```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-docs",
-  "version": "1.0.2",
+  "version": "1.2.0",
   "type": "module",
   "description": "A tool for generating reusable, low-token AI agent instruction documents",
   "keywords": [