@reclaimprotocol/agent 0.1.28 → 0.1.29

package/lib/mcp/instructions.js

@@ -60,6 +60,8 @@ const SHARED_TOPIC_FILES = {
  *  topics a mode actually has are listed back to it. */
 const TOPIC_SUMMARIES = {
     'overview': 'Terminology, your stance, and the whole loop at a glance.',
+    'contributions': 'Contributing a public provider as a volunteer: the '
+        + 'candidate-and-review workflow and the extra rules it adds.',
     'auth': 'Signing in to the backend, and which token authorizes what.',
     'devtools-migration': 'Importing a public legacy provider with the same '
         + 'UUID.',

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@reclaimprotocol/agent",
 	"title": "Reclaim Agent",
-	"version": "0.1.28",
+	"version": "0.1.29",
 	"description": "Reclaim Protocol tools for AI coding agents. Reclaim lets your app verify data points about its users, such as a follower count, an account balance, or an order history. This package is the Reclaim MCP server: it gives your agent the tools to find, build, test, and fix data verification providers by capturing and replaying browser requests, drafting provider recipes, running zkTLS proofs, and publishing provider versions.",
 	"type": "module",
 	"main": "./lib/index.js",
@@ -83,7 +83,7 @@
 		"@modelcontextprotocol/sdk": "^1.29.0",
 		"@noble/hashes": "^2.2.0",
 		"@reclaimprotocol/attestor-core": "^5.0.8",
-		"@reclaimprotocol/client": "0.1.28",
+		"@reclaimprotocol/client": "0.1.29",
 		"@reclaimprotocol/tls": "^0.1.3",
 		"chrome-remote-interface": "^0.33.0",
 		"domhandler": "^6.0.0",

package/skill/SKILL.builder.md

@@ -5,16 +5,6 @@ For claimant-facing Builder-client integration, result verification, or optional
 TEE binding, read topic `integration`. Keep URLs without `api=2` on the
 existing legacy path.
 
-<!-- topic: contributions -->
-## Public provider contributions
-
-For an asynchronous volunteer contribution, read
-[community-contributions.md](community-contributions.md) before using Builder.
-It defines the history-first workflow, approved-field allowlist, fixed-US
-egress, privacy boundaries, generalized recipe checks, and candidate review.
-Never modify a published version in place; create a candidate and submit it
-for review.
-
 <!-- common: terminology -->
 
 ## The loop, at a glance
@@ -46,6 +36,16 @@ topic before a step you aren't already fluent in.
 Multi-request provider? Run steps 5–8 once per request, then publish every
 proven draft in one call. See topic `publish`.
 
+<!-- topic: contributions -->
+## Public provider contributions
+
+For an asynchronous volunteer contribution, read
+[community-contributions.md](community-contributions.md) before using Builder.
+It defines the history-first workflow, approved-field allowlist, fixed-US
+egress, privacy boundaries, generalized recipe checks, and candidate review.
+Never modify a published version in place; create a candidate and submit it
+for review.
+
 <!-- topic: auth -->
 ## Getting authenticated
 

package/src/mcp/instructions.ts

@@ -70,6 +70,8 @@ const SHARED_TOPIC_FILES: Record<string, string> = {
  *  topics a mode actually has are listed back to it. */
 const TOPIC_SUMMARIES: Record<string, string> = {
 	'overview': 'Terminology, your stance, and the whole loop at a glance.',
+	'contributions': 'Contributing a public provider as a volunteer: the '
+		+ 'candidate-and-review workflow and the extra rules it adds.',
 	'auth': 'Signing in to the backend, and which token authorizes what.',
 	'devtools-migration': 'Importing a public legacy provider with the same '
 		+ 'UUID.',