@velinussage/locus-agent-skill 0.1.21 → 0.1.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@velinussage/locus-agent-skill",
-  "version": "0.1.21",
+  "version": "0.1.22",
   "description": "Install the general Locus agent skill, the surrounding-area purchase workflow, and the property-tax protest workflow for free and x402-paid property context.",
   "type": "module",
   "bin": {

package/skill/locus-agent-tools/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: locus-agent-tools
 preamble-tier: 1
-version: 1.35.0
+version: 1.35.1
 description: Use every time the task is a US address or place and you need cited official public records or local-government context — due diligence, flood, zoning, permits, taxes, what changed, or before you sign.
 triggers:
   - property due diligence
@@ -543,6 +543,8 @@ The paid catalog includes native products, promoted free duals, and the seven pa
 
 Locus may advertise more than one x402 option in `accepts[]`. Production offers USDC on Base and Solana when both rails are healthy. Choose one complete entry. Never combine the amount or asset from one entry with the network, recipient, or Solana `feePayer` from another entry. Solana clients use the standard `@x402/svm` exact-payment shape; the hosted facilitator verifies, fee-sponsors, and settles the partially signed transaction.
 
+Long-running endpoints may omit Solana because its recent blockhash cannot safely cover a 60-90 second build followed by settlement. `locus-place-report` uses a 180-second Base authorization and does not advertise Solana. Read the live `accepts[]` list instead of assuming every configured network appears on every tool.
+
 ### Probe the challenge without paying
 
 `GET` on any paid endpoint returns a side-effect-free discovery challenge. Do not sign that challenge for a Turnkey-backed workflow because it has no exact request body and reserves no provider capacity. Send the exact `POST` body without payment first. That charge-free preflight either returns a current 402 or an uncharged availability error.
@@ -585,7 +587,7 @@ A 402 challenge alone is not proof that end-to-end paid settlement works for you
 | `402` with a `reason` after paying | The facilitator rejected the payment (wrong network, expired authorization, insufficient funds). | Fix the payment per the reason and re-sign against a fresh challenge. |
 | `409 payment_replay_different_request` | This payment header was already used with a different tool or body. | Sign a new payment for the new request. |
 | `409 payment_processing_retry` | The same payment is mid-execution, usually a concurrent retry. | Wait briefly and resend the identical request. |
-| `502 payment_settlement_failed` | Analysis succeeded but settlement failed; the artifact was withheld. | Resend the identical request with the same payment header to resume settlement and receive the stored artifact. |
+| `502 payment_settlement_failed` | Analysis succeeded but settlement failed; the artifact was withheld. | Follow the response message. `locus-place-report` can resume its stored result when the identical payment remains valid. If the authorization expired, obtain a fresh challenge. Other tools may require a fresh payment. |
 | `200` with `charged: false` | Coverage or data was too thin to charge; you received a free diagnostic. | Follow the diagnostic's suggested free lanes; no funds moved. |
 | `409 clarification_required` | The property-update resolver could not confirm the requested subject or matched a different parcel. | If `retryInput` is present, confirm the matched subject and call again with that object. If absent, ask for a corrected exact address and build a new request. Never resend the original ambiguous body. |
 | `400 property_flyer_claim_rejected` | A specific flyer field or feature violated a pre-payment content rule. | Read `details.rejectedField`, `details.rejectedFeatureIndex` when present, and `details.reason`; rewrite only that item as a factual property condition. |