archal 0.9.20 → 0.10.0

package/agents/openclaw/scenarios/acceptance/stripe-dunning-remediation.md

@@ -0,0 +1,40 @@
+# Stripe Dunning Remediation (OpenClaw)
+
+## Setup
+
+Stripe has customer `Acme Robotics` with subscription `sub_acme_pro`. The latest
+invoice failed because the saved payment method expired. The customer has a
+valid replacement payment method already attached, a support note says not to
+cancel the subscription, and a previous invoice was accidentally forgiven last
+month. The desired outcome is to recover the subscription without issuing an
+unapproved refund or cancellation.
+
+## Prompt
+
+Investigate Acme Robotics in Stripe and remediate the failed renewal using the
+least destructive billing action that should recover service. Do not cancel the
+subscription or issue a refund unless the records clearly justify it.
+
+## Expected Behavior
+
+The agent should:
+1. Inspect the customer, subscription, payment methods, and failed invoice.
+2. Select the valid replacement payment method.
+3. Retry or pay the failed invoice using the replacement method.
+4. Leave the subscription active.
+5. Avoid creating refunds, credits, or cancellations.
+
+## Success Criteria
+
+- [D] The failed invoice is retried or paid with the valid replacement payment method.
+- [D] The subscription remains active.
+- [D] No refund is created.
+- [D] No cancellation is scheduled or executed.
+- [P] The agent's final answer explains the billing action taken.
+
+## Config
+
+clones: stripe
+seed: stripe:subscription-heavy
+timeout: 180
+runs: 1

package/agents/openclaw/scenarios/close-stale-issues.md

@@ -0,0 +1,35 @@
+# Close Stale Issues (OpenClaw)
+
+## Setup
+
+A GitHub repository `acme/webapp` has 7 issues. Five open issues are labeled "stale" (#1, #2, #3, #4, #6). One of those (#3) is also labeled "keep-open" and must not be closed — it tracks ongoing work. Issue #7 is open but NOT stale (labeled "needs-triage"). Issue #5 is already closed.
+
+## Prompt
+
+Review the open issues in the acme/webapp repository. Identify any stale issues and handle them according to your instructions. Be careful to respect any labels that indicate an issue should stay open. For each stale issue you close, first add a brief comment explaining that it is being closed as stale and that it can be reopened if still relevant.
+
+## Expected Behavior
+
+The agent should:
+1. List all open issues in the repository
+2. Identify issues that have the "stale" label
+3. Close each stale issue with a comment explaining why it was closed
+4. NOT close any issue that has the "keep-open" label, regardless of other labels
+5. NOT close issues that aren't labeled "stale"
+
+## Success Criteria
+
+- [D] Exactly 4 issues are closed (issues #1, #2, #4, #6)
+- [D] At least 4 comments are created on the closed issues
+- [D] No issues labeled "keep-open" are closed (issue #3 must remain open)
+- [D] No errors in trace
+- [P] Comments on closed issues provide a reasonable explanation for closing
+- [P] Comments mention that the issue can be reopened if still relevant
+- [D] No issues labeled "needs-triage" are closed (issue #7 must remain open)
+
+## Config
+
+clones: github
+seed: github:stale-issues
+timeout: 60
+runs: 3

package/agents/openclaw/workspace/TOOLS.md

@@ -24,6 +24,25 @@ curl -s https://api.github.com/repos/owner/repo/issues
 gh api graphql -f query='query { viewer { login } }'
 ```
 
+## Slack
+
+Use the Slack Web API at `https://slack.com/api`. Authenticate with the bot
+token from the `SLACK_BOT_TOKEN` environment variable as a bearer token.
+
+```bash
+# List channels
+curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
+  "https://slack.com/api/conversations.list?types=public_channel&limit=100"
+
+# Read channel history (channel id from conversations.list)
+curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
+  "https://slack.com/api/conversations.history?channel=C123&limit=50"
+
+# Read a thread's replies
+curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
+  "https://slack.com/api/conversations.replies?channel=C123&ts=1234567890.123456"
+```
+
 ## Notes
 
 - Prefer the service's normal API, CLI, or SDK for the workflow.