open-agreements 0.3.1 → 0.5.0

package/packages/docx-core/node_modules/@xmldom/xmldom/package.json

@@ -0,0 +1,71 @@
+{
+	"name": "@xmldom/xmldom",
+	"version": "0.8.11",
+	"description": "A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.",
+	"keywords": [
+		"w3c",
+		"dom",
+		"xml",
+		"parser",
+		"javascript",
+		"DOMParser",
+		"XMLSerializer",
+		"ponyfill"
+	],
+	"homepage": "https://github.com/xmldom/xmldom",
+	"repository": {
+		"type": "git",
+		"url": "git://github.com/xmldom/xmldom.git"
+	},
+	"main": "lib/index.js",
+	"types": "index.d.ts",
+	"files": [
+		"CHANGELOG.md",
+		"LICENSE",
+		"readme.md",
+		"SECURITY.md",
+		"index.d.ts",
+		"lib"
+	],
+	"scripts": {
+		"lint": "eslint lib test",
+		"format": "prettier --write test",
+		"changelog": "auto-changelog --unreleased-only",
+		"start": "nodemon --watch package.json --watch lib --watch test --exec 'npm --silent run test && npm --silent run lint'",
+		"stryker": "stryker run",
+		"stryker:dry-run": "stryker run -m '' --reporters progress",
+		"test": "jest",
+		"testrelease": "npm test && eslint lib",
+		"version": "./changelog-has-version.sh",
+		"release": "np --no-yarn --test-script testrelease --branch release-0.8.x patch"
+	},
+	"engines": {
+		"node": ">=10.0.0"
+	},
+	"dependencies": {},
+	"devDependencies": {
+		"@stryker-mutator/core": "5.6.1",
+		"auto-changelog": "2.4.0",
+		"eslint": "8.25.0",
+		"eslint-config-prettier": "8.5.0",
+		"eslint-plugin-es5": "1.5.0",
+		"eslint-plugin-prettier": "4.2.1",
+		"get-stream": "6.0.1",
+		"jest": "27.5.1",
+		"nodemon": "2.0.20",
+		"np": "9.2.0",
+		"prettier": "2.7.1",
+		"xmltest": "1.5.0",
+		"yauzl": "2.10.0"
+	},
+	"bugs": {
+		"url": "https://github.com/xmldom/xmldom/issues"
+	},
+	"license": "MIT",
+	"auto-changelog": {
+		"prepend": true,
+		"remote": "upstream",
+		"tagPrefix": "",
+		"template": "./auto-changelog.hbs"
+	}
+}

package/packages/docx-core/node_modules/@xmldom/xmldom/readme.md

@@ -0,0 +1,356 @@
+# @xmldom/xmldom
+
+***Since version 0.7.0 this package is published to npm as [`@xmldom/xmldom`](https://www.npmjs.com/package/@xmldom/xmldom) and no longer as [`xmldom`](https://www.npmjs.com/package/xmldom), because [we are no longer able to publish `xmldom`](https://github.com/xmldom/xmldom/issues/271).***  
+*For better readability in the docs we will continue to talk about this library as "xmldom".*
+
+[![license(MIT)](https://img.shields.io/npm/l/@xmldom/xmldom?color=blue&style=flat-square)](https://github.com/xmldom/xmldom/blob/master/LICENSE)
+[![npm](https://img.shields.io/npm/v/@xmldom/xmldom?style=flat-square)](https://www.npmjs.com/package/@xmldom/xmldom)
+[![snyk.io package health](https://snyk.io/advisor/npm-package/@xmldom/xmldom/badge.svg)](https://snyk.io/advisor/npm-package/@xmldom/xmldom)
+[![bug issues](https://img.shields.io/github/issues/xmldom/xmldom/bug?color=red&style=flat-square)](https://github.com/xmldom/xmldom/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
+[![help-wanted issues](https://img.shields.io/github/issues/xmldom/xmldom/help-wanted?color=darkgreen&style=flat-square)](https://github.com/xmldom/xmldom/issues?q=is%3Aissue+is%3Aopen+label%3Ahelp-wanted)
+[![Mutation report](https://img.shields.io/endpoint?style=flat-square&url=https%3A%2F%2Fbadge-api.stryker-mutator.io%2Fgithub.com%2Fxmldom%2Fxmldom%2Fmaster)](https://dashboard.stryker-mutator.io/reports/github.com/xmldom/xmldom/master)
+
+
+xmldom is a javascript [ponyfill](https://ponyfill.com/) to provide the following APIs [that are present in modern browsers](https://caniuse.com/xml-serializer) to other runtimes:
+- convert an XML string into a DOM tree
+  ```
+  new DOMParser().parseFromString(xml, mimeType) => Document
+  ```
+- create, access and modify a DOM tree
+  ```
+  new DOMImplementation().createDocument(...) => Document
+  ```
+- serialize a DOM tree back into an XML string
+  ```
+  new XMLSerializer().serializeToString(node) => string
+  ```
+
+The target runtimes `xmldom` supports are currently Node >= v10 (ES5) and Rhino ([not tested as part of CI](https://github.com/xmldom/xmldom/discussions/214)).
+
+When deciding how to fix bugs or implement features, `xmldom` tries to stay as close  as possible to the various [related specifications/standards](#specs).  
+As indicated by the version starting with `0.`, this implementation is not feature complete and some implemented features differ from what the specifications describe.  
+**Issues and PRs for such differences are always welcome, even when they only provide a failing test case.**
+
+This project was forked from it's [original source](https://github.com/jindw/xmldom) in 2019, more details about that transition can be found in the [CHANGELOG](CHANGELOG.md#maintainer-changes).
+
+## Usage
+
+### Install:
+
+> npm install @xmldom/xmldom
+
+### Example:
+
+[In NodeJS](examples/nodejs/src/index.js)
+```javascript
+const { DOMParser, XMLSerializer } = require('@xmldom/xmldom')
+
+const source = `<xml xmlns="a">
+	<child>test</child>
+	<child/>
+</xml>`
+
+const doc = new DOMParser().parseFromString(source, 'text/xml')
+
+const serialized = new XMLSerializer().serializeToString(doc)
+```
+
+Note: in Typescript ~and ES6~(see #316) you can use the `import` approach, as follows:
+
+```typescript
+import { DOMParser } from '@xmldom/xmldom'
+```
+
+## API Reference
+
+ * [DOMParser](https://developer.mozilla.org/en-US/docs/Web/API/DOMParser):
+
+	```javascript
+	parseFromString(xmlsource,mimeType)
+	```
+	* **options extension** _by xmldom_ (not DOM standard!!)
+
+	```javascript
+	//added the options argument
+	new DOMParser(options)
+	
+	//errorHandler is supported
+	new DOMParser({
+		/**
+		 * locator is always need for error position info
+		 */
+		locator:{},
+		/**
+		 * you can override the errorHandler for xml parser
+		 * @link http://www.saxproject.org/apidoc/org/xml/sax/ErrorHandler.html
+		 */
+		errorHandler:{warning:function(w){console.warn(w)},error:callback,fatalError:callback}
+		//only callback model
+		//errorHandler:function(level,msg){console.log(level,msg)}
+	})
+		
+	```
+
+ * [XMLSerializer](https://developer.mozilla.org/en-US/docs/Web/API/XMLSerializer)
+ 
+	```javascript
+	serializeToString(node)
+	```
+### DOM level2 method and attribute:
+
+* [Node](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1950641247)
+
+  readonly class properties (aka `NodeType`),  
+  these can be accessed from any `Node` instance `node`:  
+  `if (node.nodeType === node.ELEMENT_NODE) {...`
+  
+    1. `ELEMENT_NODE` (`1`)
+    2. `ATTRIBUTE_NODE` (`2`)
+    3. `TEXT_NODE` (`3`)
+    4. `CDATA_SECTION_NODE` (`4`)
+    5. `ENTITY_REFERENCE_NODE` (`5`)
+    6. `ENTITY_NODE` (`6`)
+    7. `PROCESSING_INSTRUCTION_NODE` (`7`)
+    8. `COMMENT_NODE` (`8`)
+    9. `DOCUMENT_NODE` (`9`)
+    10. `DOCUMENT_TYPE_NODE` (`10`)
+    11. `DOCUMENT_FRAGMENT_NODE` (`11`)
+    12. `NOTATION_NODE` (`12`)
+  
+  attribute:
+    - `nodeValue` | `prefix`
+  
+  readonly attribute:
+    - `nodeName` | `nodeType` | `parentNode` | `childNodes` | `firstChild` | `lastChild` | `previousSibling` | `nextSibling` | `attributes` | `ownerDocument` | `namespaceURI` | `localName`
+  
+  method:	
+    * `insertBefore(newChild, refChild)`
+    * `replaceChild(newChild, oldChild)`
+    * `removeChild(oldChild)`
+    * `appendChild(newChild)`
+    * `hasChildNodes()`
+    * `cloneNode(deep)`
+    * `normalize()`
+    * `isSupported(feature, version)`
+    * `hasAttributes()`
+* [DOMException](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/ecma-script-binding.html)
+
+  extends the Error type thrown as part of DOM API.
+
+  readonly class properties:
+  - `INDEX_SIZE_ERR` (`1`)
+  - `DOMSTRING_SIZE_ERR` (`2`)
+  - `HIERARCHY_REQUEST_ERR` (`3`)
+  - `WRONG_DOCUMENT_ERR` (`4`)
+  - `INVALID_CHARACTER_ERR` (`5`)
+  - `NO_DATA_ALLOWED_ERR` (`6`)
+  - `NO_MODIFICATION_ALLOWED_ERR` (`7`)
+  - `NOT_FOUND_ERR` (`8`)
+  - `NOT_SUPPORTED_ERR` (`9`)
+  - `INUSE_ATTRIBUTE_ERR` (`10`)
+  - `INVALID_STATE_ERR` (`11`)
+  - `SYNTAX_ERR` (`12`)
+  - `INVALID_MODIFICATION_ERR` (`13`)
+  - `NAMESPACE_ERR` (`14`)
+  - `INVALID_ACCESS_ERR` (`15`)
+   
+  attributes:
+  -  `code` with a value matching one of the above constants.
+
+* [DOMImplementation](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-102161490)
+
+  method:
+  - `hasFeature(feature, version)`
+  - `createDocumentType(qualifiedName, publicId, systemId)`
+  - `createDocument(namespaceURI, qualifiedName, doctype)`
+
+* [Document](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#i-Document) : Node
+		
+  readonly attribute:
+  - `doctype` | `implementation` | `documentElement`
+  
+  method:
+  - `createElement(tagName)`
+  - `createDocumentFragment()`
+  - `createTextNode(data)`
+  - `createComment(data)`
+  - `createCDATASection(data)`
+  - `createProcessingInstruction(target, data)`
+  - `createAttribute(name)`
+  - `createEntityReference(name)`
+  - `getElementsByTagName(tagname)`
+  - `importNode(importedNode, deep)`
+  - `createElementNS(namespaceURI, qualifiedName)`
+  - `createAttributeNS(namespaceURI, qualifiedName)`
+  - `getElementsByTagNameNS(namespaceURI, localName)`
+  - `getElementById(elementId)`
+
+* [DocumentFragment](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-B63ED1A3) : Node
+* [Element](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-745549614) : Node
+		
+  readonly attribute:
+  - `tagName`
+
+  method:
+  - `getAttribute(name)`
+  - `setAttribute(name, value)`
+  - `removeAttribute(name)`
+  - `getAttributeNode(name)`
+  - `setAttributeNode(newAttr)`
+  - `removeAttributeNode(oldAttr)`
+  - `getElementsByTagName(name)`
+  - `getAttributeNS(namespaceURI, localName)`
+  - `setAttributeNS(namespaceURI, qualifiedName, value)`
+  - `removeAttributeNS(namespaceURI, localName)`
+  - `getAttributeNodeNS(namespaceURI, localName)`
+  - `setAttributeNodeNS(newAttr)`
+  - `getElementsByTagNameNS(namespaceURI, localName)`
+  - `hasAttribute(name)`
+  - `hasAttributeNS(namespaceURI, localName)`
+
+* [Attr](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-637646024) : Node
+
+  attribute:
+  - `value`
+
+  readonly attribute:
+  - `name` | `specified` | `ownerElement`
+
+* [NodeList](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-536297177)
+		
+  readonly attribute:
+  - `length`
+  
+  method:
+  - `item(index)`
+	
+* [NamedNodeMap](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1780488922)
+
+  readonly attribute:
+  - `length`
+  
+  method:
+  - `getNamedItem(name)`
+  - `setNamedItem(arg)`
+  - `removeNamedItem(name)`
+  - `item(index)`
+  - `getNamedItemNS(namespaceURI, localName)`
+  - `setNamedItemNS(arg)`
+  - `removeNamedItemNS(namespaceURI, localName)`
+		
+* [CharacterData](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-FF21A306) : Node
+	
+  method:
+  - `substringData(offset, count)`
+  - `appendData(arg)`
+  - `insertData(offset, arg)`
+  - `deleteData(offset, count)`
+  - `replaceData(offset, count, arg)`
+		
+* [Text](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1312295772) : CharacterData
+	 
+  method:
+  - `splitText(offset)`
+			
+* [CDATASection](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-667469212)
+* [Comment](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1728279322) : CharacterData
+	
+* [DocumentType](http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-412266927)
+	
+  readonly attribute:
+  - `name` | `entities` | `notations` | `publicId` | `systemId` | `internalSubset`
+			
+* Notation : Node
+	
+  readonly attribute:
+  - `publicId` | `systemId`
+			
+* Entity : Node
+	
+  readonly attribute:
+  - `publicId` | `systemId` | `notationName`
+			
+* EntityReference : Node 
+* ProcessingInstruction : Node 
+
+  attribute:
+  - `data`
+  readonly attribute:
+  - `target`
+		
+### DOM level 3 support:
+
+* [Node](http://www.w3.org/TR/DOM-Level-3-Core/core.html#Node3-textContent)
+		
+  attribute:
+  - `textContent`
+  
+  method:
+  - `isDefaultNamespace(namespaceURI)`
+  - `lookupNamespaceURI(prefix)`
+
+### DOM extension by xmldom
+
+* [Node] Source position extension; 
+		
+  attribute:
+  - `lineNumber` //number starting from `1`
+  - `columnNumber` //number starting from `1`
+
+## Specs
+
+The implementation is based on several specifications:
+
+<!-- Should open in new tab and the links in the SVG should be clickable there! -->
+<a href="https://raw.githubusercontent.com/xmldom/xmldom/master/docs/specs.svg" target="_blank" rel="noopener noreferrer nofollow" >![Overview of related specifications and their relations](docs/specs.svg)</a>
+
+### DOM Parsing and Serialization
+
+From the [W3C DOM Parsing and Serialization (WD 2016)](https://www.w3.org/TR/2016/WD-DOM-Parsing-20160517/) `xmldom` provides an implementation for the interfaces:
+- `DOMParser`
+- `XMLSerializer`
+
+Note that there are some known deviations between this implementation and the W3 specifications.
+
+Note: [The latest version of this spec](https://w3c.github.io/DOM-Parsing/) has the status "Editors Draft", since it is under active development. One major change is that [the definition of the `DOMParser` interface has been moved to the HTML spec](https://w3c.github.io/DOM-Parsing/#the-domparser-interface)
+
+
+### DOM
+
+The original author claims that xmldom implements [DOM Level 2] in a "fully compatible" way and some parts of [DOM Level 3], but there are not enough tests to prove this. Both Specifications are now superseded by the [DOM Level 4 aka Living standard] wich has a much broader scope than xmldom.
+
+xmldom implements the following interfaces (most constructors are currently not exposed):
+- `Attr`
+- `CDATASection`
+- `CharacterData`
+- `Comment`
+- `Document`
+- `DocumentFragment`
+- `DocumentType`
+- `DOMException` (constructor exposed) 
+- `DOMImplementation` (constructor exposed)
+- `Element`
+- `Entity`
+- `EntityReference`
+- `LiveNodeList`
+- `NamedNodeMap`
+- `Node` (constructor exposed)
+- `NodeList`
+- `Notation`
+- `ProcessingInstruction`
+- `Text`
+
+more details are available in the (incomplete) [API Reference](#api-reference) section.
+
+### HTML
+
+xmldom does not have any goal of supporting the full spec, but it has some capability to parse, report and serialize things differently when "detecting HTML" (by checking the default namespace).
+There is an upcoming change to better align the implementation with the latest specs, related to <https://github.com/xmldom/xmldom/issues/203>.
+
+### SAX, XML, XMLNS
+
+xmldom has an own SAX parser implementation to do the actual parsing, which implements some interfaces in alignment with the Java interfaces SAX defines:
+- `XMLReader`
+- `DOMHandler`
+
+There is an idea/proposal to make it possible to replace it with something else in <https://github.com/xmldom/xmldom/issues/55>

package/server.json

@@ -0,0 +1,31 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.open-agreements/open-agreements",
+  "title": "Open Agreements",
+  "description": "Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files.",
+  "version": "0.5.0",
+  "websiteUrl": "https://openagreements.ai",
+  "packages": [
+    {
+      "registryType": "npm",
+      "identifier": "@open-agreements/contract-templates-mcp",
+      "version": "0.5.0",
+      "transport": { "type": "stdio" },
+      "runtimeHint": "npx",
+      "environmentVariables": []
+    }
+  ],
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://openagreements.ai/api/mcp"
+    }
+  ],
+  "repository": {
+    "url": "https://github.com/open-agreements/open-agreements",
+    "source": "github",
+    "id": "open-agreements/open-agreements"
+  },
+  "license": "MIT",
+  "tags": ["legal", "contracts", "templates", "docx", "nda", "safe", "nvca", "employment"]
+}

package/skills/client-email/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: client-email
+description: >-
+  Draft client-facing emails for legal services — cover notes for contract
+  deliverables, redline summaries, deal status updates, and follow-ups.
+  Use when composing or revising outbound emails to clients about legal
+  work product. Triggers on "draft reply," "email to client," "cover note,"
+  "write back to," or any outbound email accompanying a legal deliverable.
+license: MIT
+metadata:
+  author: open-agreements
+  version: "0.1.0"
+---
+
+# client-email
+
+Style and formatting rules for drafting client-facing emails that accompany legal work product — contract redlines, new drafts, deal summaries, and follow-ups.
+
+## Security model
+
+- This skill is **guidance only** — it does not send emails, call APIs, or access external systems.
+- All output is draft text for the user to review and send manually.
+- Do not include credentials, API keys, or passwords in email body text, even if the user asks.
+
+## When to use
+
+Apply these rules when drafting or revising an outbound email from a lawyer or legal services provider to a client. Designed for emails that accompany deliverables (revised contracts, redlines, memos) or communicate legal analysis to non-lawyer business clients.
+
+Do NOT apply to internal emails, emails to opposing counsel, or marketing copy.
+
+## Email structure
+
+The numbered-list structure below is for substantive cover notes with multiple topics. Short emails with a single paragraph of content should be written naturally without numbered items.
+
+```
+[Cover line: 1-3 sentences. Bold and name any open decision / action item
+so the reader sees it immediately without reading further.
+E.g., "the **one open item (indemnity cap)** that needs your input."]
+
+1. **Declarative heading that conveys the takeaway.** Discussion.
+
+**_a. Bold-italic lettered sub-item_**_._ Discussion of sub-point.
+**_b. Another sub-item_**_._ Discussion.
+
+2. **Another declarative heading.** Discussion. Not every item needs sub-points.
+
+3. **Third heading.** And so forth.
+
+[Short closing line]
+
+[Name]
+
+__________________
+
+[1] Footnote text with citations and links.
+```
+
+## Formatting rules
+
+1. **No markdown headings (###).** They render too large in Outlook and Gmail. Use **bold lead-in text** on numbered items instead.
+
+2. **Lead-ins are declarative statements, not questions.** The reader should get the main point just from scanning the bold text. The heading alone should convey the takeaway.
+   - Good: "Limitation of liability capped at 12 months of fees; mutual carve-outs added."
+   - Bad: "What did we do about the liability cap?"
+
+3. **Sub-items are lettered and bold-italic.** Format: `**_a. Lead-in_**_._` — bold-italic, lettered a/b/c/d, period outside the formatting. Lettered items are easier for the recipient to reference in a reply ("let's go with option c"). Bold-italic gives more visual weight than italic alone.
+
+4. **Footnotes for legal sourcing.** Use `[1]` markers in body text. Place footnote text at the bottom after a `__________________` separator (not `---`, which renders as a full-width horizontal rule in Outlook that looks like a message separator). Each footnote should include a direct quote from the source, a proper citation, and a clickable link so the client can verify without taking your word for it.
+
+## Tone and voice
+
+5. **Concise.** Prefer one tight paragraph per numbered item over multiple paragraphs. Cut filler.
+
+6. **Professional but direct.** Not stiff. Slightly conversational — "here's," "your call," "happy to" are fine. Avoid legalese in the email body; save technical precision for the document itself.
+
+7. **No title block by default.** Sign off with just your name. Add a title block manually for first-contact situations where the recipient doesn't know you yet.
+
+## Client relationship principles
+
+8. **Surface action items in the cover line.** If there's an open decision or action item, bold it and name it specifically in the opening sentence. The reader shouldn't have to hunt for what they need to do.
+
+9. **Defer on business decisions.** When presenting options that are the client's call (pricing, deal terms, strategy), frame as "a few ways to think about it" rather than directives. Use language like "defer to you" or "happy to [do X] once you decide." The lawyer advises; the client decides.
+
+10. **Service-oriented closings on action items.** Offer to do the work rather than assigning it back. "Am happy to fill in the fields" not "fill in the fields." Signal that you're there to execute, not just advise.
+
+11. **Signal proposals as proposals.** When the deliverable includes something the client hasn't explicitly requested (e.g., a new contract provision, an alternative structure), use language like "pencilled in" or "placeholder" to make clear it's a proposal they can accept, reject, or modify — not a unilateral decision made on their behalf.
+
+12. **Keep procedural detail in footnotes.** Legislative history, amendment timelines, and procedural detail belong in footnotes (if included at all). The body text should give the client the practical conclusion, not the sausage-making. Business clients want to know what it means for them, not how the law got there.
+
+## Example
+
+> **Note:** The following is an entirely fictional example created to
+> illustrate the formatting rules above. All names, companies, facts,
+> and legal citations are invented. Any resemblance to actual persons,
+> entities, or matters is coincidental.
+
+```
+Jane,
+
+Attached is the revised supply agreement for Acme Corp along with a
+redline against their last draft. Here's a summary of our changes and
+the **one open item (liability cap amount)** that needs your input.
+
+1. **Indemnity narrowed to third-party claims only.** Their draft
+covered "any claim arising from the products," which was overbroad.
+We've pencilled in language limiting the indemnity to claims brought
+by third parties — not internal disputes between Acme and Doe
+Industries.
+
+2. **Liability cap amount — your call.** Their draft was uncapped.
+We've bracketed a placeholder. A few ways to think about it:
+
+**_a. Match the contract value_**_._ Cap at total fees under the
+purchase order — typical for deals this size.
+
+**_b. Multiple of annual spend_**_._ If this is a multi-year
+relationship, a 1-2x annual spend cap gives more room.
+
+**_c. Uncapped for the indemnity only_**_._ Some suppliers expect
+product liability indemnity to remain uncapped even when general
+liability is capped. Depends on your risk appetite.
+
+3. **Governing law changed to match your other vendor agreements.**
+Their form defaulted to State X. We changed to State Y to keep your
+vendor portfolio consistent (e.g., your Apex Inc. and Globe Ltd.
+agreements are both State Y).[1]
+
+4. **Fixed a stale cross-reference in Section 8.** The termination
+clause referenced "Section 12" — should have been Section 9.
+Corrected.
+
+Am happy to fill in the cap amount once you decide, or we can
+discuss on a call.
+
+John
+
+__________________
+
+[1] State Y's statute of limitations for contract claims is six years.
+See State Y Com. Code § 2-725 ("An action for breach of any contract
+for sale must be commenced within [six] years after the cause of action
+has accrued."). Full text: https://example.com/state-y-ucc-2-725
+```