New release — June 3: jurisdiction support, plaintiff-side litigation, and suite-wide refinements from launch feedback

.claude-plugin/marketplace.json

@@ -28,7 +28,7 @@
       "name": "product-legal",
       "displayName": "Product Legal",
       "source": "./product-legal",
-      "description": "Reviews product launches against your risk calibration, answers 'is this a problem?' questions in minutes, checks marketing copy for claims that need substantiation, and flags upcoming launches that need legal eyes before anyone asks.",
+      "description": "Reviews product launches against your risk calibration, answers 'is this a problem?' questions in minutes, checks marketing copy for claims that need substantiation, and flags upcoming launches that need legal review.",
       "author": {
         "name": "Anthropic"
       }
@@ -55,7 +55,7 @@
       "name": "regulatory-legal",
       "displayName": "Regulatory Legal",
       "source": "./regulatory-legal",
-      "description": "Watches regulatory feeds, diffs new rules against your policy library, tracks comment deadlines and open gaps, and writes the digest your team reads Monday morning.",
+      "description": "Watches regulatory feeds, diffs new rules against your policy library, tracks comment deadlines and open gaps, and writes a digest filtered by your materiality threshold.",
       "author": {
         "name": "Anthropic"
       }
@@ -82,7 +82,7 @@
       "name": "law-student",
       "displayName": "Law Student",
       "source": "./law-student",
-      "description": "Drills Socratically, briefs cases, builds outlines, runs bar prep sessions tuned to your jurisdiction, grades IRAC practice, and plans the study schedule — without ever writing it for you.",
+      "description": "Drills Socratically, scaffolds case briefs and outlines, runs bar prep sessions tuned to your jurisdiction, grades IRAC practice, and plans the study schedule — your briefs, outlines, and essays stay your own work.",
       "author": {
         "name": "Anthropic"
       }

.github/workflows/cla.yaml

@@ -15,7 +15,10 @@ jobs:
     timeout-minutes: 5
     steps:
       - name: "CLA Assistant"
-        if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'
+        # startsWith() rather than == so a signing comment with trailing
+        # whitespace or a newline still triggers the run; exact-match
+        # silently drops contributors' signatures.
+        if: github.event_name == 'pull_request_target' || startsWith(github.event.comment.body, 'recheck') || startsWith(github.event.comment.body, 'I have read the CLA Document and I hereby sign the CLA')
         # Upstream contributor-assistant/github-action was archived 2026-03-23
         # still on Node 20 (deprecated 2026-06-02). This fork bumps to Node 24
         # and adds: an impersonation guard (PR opener must be an author or
@@ -30,7 +33,8 @@ jobs:
           path-to-signatures: "signatures/cla.json"
           branch: "cla-signatures"
           # noreply@anthropic.com is the email AI assistants use on
-          # Co-authored-by trailers (e.g. Claude). Allowlisting it suppresses
-          # the synthetic co-author from the CLA check; the PR opener still
-          # has to sign.
-          allowlist: "iainmcgin,dependabot[bot],github-actions[bot],renovate[bot],noreply@anthropic.com"
+          # Co-authored-by trailers. Allowlisting it (and the claude[bot]
+          # app identity) suppresses synthetic co-authors and app-authored
+          # commits from the CLA check; the human PR opener still has to
+          # sign either way.
+          allowlist: "claude[bot],dependabot[bot],github-actions[bot],renovate[bot],noreply@anthropic.com"

CLA.md

@@ -0,0 +1,39 @@
+# Individual Contributor License Agreement ("Agreement") v2.2
+
+Thank you for your interest in the Claude for Legal project (the "Project"), owned and managed by Anthropic, PBC (the "Company"). To clarify the intellectual property license granted with Contributions from any person or entity, the Company must have on file a signed Contributor License Agreement ("CLA") from each Contributor, indicating agreement with the license terms below. This agreement is for your protection as a Contributor as well as the protection of the Company and its users. It does not change your rights to use your own Contributions for any other purpose.
+
+You accept and agree to the following terms and conditions for Your Contributions (present and future) that you submit to the Company. In return, the Company shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its bylaws in effect at the time of the Contribution. Except for the license granted herein to the Company and recipients of software distributed by the Company, You reserve all right, title, and interest in and to Your Contributions.
+
+## 1. Definitions
+
+"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the Company. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Company for inclusion in, or documentation of, any of the products owned or managed by the Company (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Company or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Company for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
+
+## 2. Grant of Copyright License
+
+Subject to the terms and conditions of this Agreement, You hereby grant to the Company and to recipients of software distributed by the Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
+
+## 3. Grant of Patent License
+
+Subject to the terms and conditions of this Agreement, You hereby grant to the Company and to recipients of software distributed by the Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
+
+## 4. Legal Entitlement
+
+You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Company, or that your employer has executed a separate Corporate CLA with the Company.
+
+## 5. Original Creation
+
+You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
+
+## 6. Support and Warranties
+
+You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+## 7. Third-Party Work
+
+Should You wish to submit work that is not Your original creation, You may submit it to the Company separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
+
+## 8. Notification
+
+You agree to notify the Company of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.

CLAUDE.md

@@ -21,7 +21,8 @@ agents, hooks), plugin metadata, or cookbook config — not application code.
 external_plugins/<vendor>/        # vendor-maintained plugins (CoCounsel)
 managed-agent-cookbooks/<name>/   # CMA agent.yaml + subagents/ + steering-examples.json
 scripts/                          # validate.py, lint-tool-scope.py, orchestrate.py,
-                                  # deploy-managed-agent.sh, test-cookbooks.sh
+                                  # deploy-managed-agent.sh, test-cookbooks.sh,
+                                  # check-guardrail-sync.py
 references/                       # shared templates (company-profile, dashboard)
 ```
 
@@ -41,6 +42,10 @@ python3 scripts/lint-tool-scope.py
 
 # 3. JSON/YAML sanity
 python3 -c "import json,glob; [json.load(open(f)) for f in glob.glob('**/*.json', recursive=True)]"
+python3 -c "import yaml,glob; [yaml.safe_load(open(f)) for f in glob.glob('**/*.yaml', recursive=True)]"
+
+# 4. Shared-guardrail sync across the 12 plugin CLAUDE.md templates
+python3 scripts/check-guardrail-sync.py
 ```
 
 ### Marketplace invariants (I1–I11)
@@ -64,7 +69,7 @@ here too — the ones most likely to trip a contributor:
 
 Every `agents/*.md` needs `name` and `description`. Every
 `skills/<name>/SKILL.md` needs `description`. Every `commands/*.md` needs
-`description`. Multi-line descriptions use `>` block scalars and that's fine —
+`description`. Multi-line descriptions may use `>` block scalars —
 `claude plugin validate` parses them correctly.
 
 ## Conventions
@@ -105,8 +110,8 @@ fine since the vendor lands changes via PR rather than mirroring a fork.
 - 2-space indent in all JSON and `.mcp.json` files.
 - Final newline at end of every text file.
 - No trailing whitespace.
-- Markdown tables: pipe-aligned columns are nice but not required; just keep
-  the column count consistent.
+- Markdown tables: pipe-aligned columns are optional; keep the column count
+  consistent.
 
 ## Cookbooks
 
@@ -125,6 +130,9 @@ rules that `scripts/lint-tool-scope.py` enforces:
   intentional; ask before unifying.
 - `hooks/hooks.json` is missing in two plugins. Hooks are optional; the missing
   files are not a bug.
-- `references/` lives only at repo root and is not shipped inside any plugin
-  directory. Several plugin `CLAUDE.md` templates reference it as if it were —
-  that's a known gap, not a thing to silently move.
+- The shared templates (`references/company-profile-template.md`,
+  `references/dashboard-template.md`) live only at repo root, but five plugins
+  (`ai-governance-legal`, `privacy-legal`, `product-legal`, `legal-clinic`,
+  `legal-builder-hub`) ship their own `references/` content that their skills
+  depend on — leave those in place. Plugin `CLAUDE.md` templates that point at
+  the root-only shared templates are a known gap, not a thing to silently move.