[hannesrudolph]

What Problem This Solves

Hermit's /say help, helper-thread welcome, and Peter-mention automod response direct setup/troubleshooting requests into Discord instead of the official support destination.

Why This Change Was Made

https://community.openclaw.ai/ is the official OpenClaw support pathway. Runtime guidance must identify it consistently, including when an operator has customized the helper welcome with an environment override.

User Impact

• /say help links Get support and keeps diagnostic context, log redaction, and the troubleshooting FAQ.
• Helper welcomes retain the helper mention and practical diagnostic checklist; a fixed official-support link and redaction reminder follow either default or configured welcome text. Previously valid long overrides are preserved by sending the reminder separately if combined text exceeds 4,000 characters.
• The Peter-mention automod reply points ordinary help requests to official support while retaining PR discussion and Discord-specific reporting channels.
• Social conversation, collaboration, existing helper activity, command registration contexts, thread tracking, and moderation behavior remain unchanged.
• Documents override behavior without changing environment variables or deploying anything.

Evidence

• Bun 1.4.2 frozen Worker and forwarder dependency installs: passed.

• Worker and forwarder typechecks: passed.

• Focused real listener/Carbon serialization tests: 15 passed, 0 failed. Includes unset, blank, whitespace, and custom welcome overrides; archived/unrelated thread exclusion; persistent thread registration; exact 4,000/4,001-character combined message boundaries and valid 3,900/4,000-character overrides; and the actual loaded automod template with preserved reporting routes. Only external REST/webhook transports are replaced with in-memory fakes.

• bun run deploy:dry-run: passed; no deployment.

• bun run test: 332 passed, 0 failed, 185,358 assertions across 34 files (117.67 seconds).

• git diff --check: passed.

• Pinned local ClawSweeper completed for base 271ed2f61daa8f3040fdf86e57688d1c2bf4d363 through head 9f2171313776dacffc43cb798a344af279ac1032, verified checkout access, no actionable correctness or security findings. An initial custom-welcome text-budget regression was fixed before the final review.

• Final review: /Users/hrudolph/Data/clawsweeper-local-reviews/official-support-hermit-20261020-publish-candidate/0.md.

Full suite results are recorded in the implementation handoff beside this body. ClawSweeper explicitly notes missing live Discord delivery proof; source review and local integration tests do not establish production rendering. No Discord messages were sent, no bot configuration changed, and no production credentials were read for testing. Local REST capture proves serialized payloads, not live Discord delivery.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge.

What this changes

This PR directs help snippets, helper welcomes, and Peter-mention responses to the official OpenClaw support site.

Example: A member runs /say help.

• Before: The reply directs them to Discord channel 1459642797895319552.
• After: The reply links to https://community.openclaw.ai/ and retains diagnostic and log-redaction guidance.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The focused implementation appears correct and follows authorized direction; supplied validation reaches serialization through real listeners but stops before Discord delivery.
Proof confidence	🦐 gold shrimp (3/6)	This maintainer-authored PR is outside the ordinary contributor proof gate; its supplied listener and Carbon serialization tests exercise message construction with fake transports, and the body explicitly disclaims live Discord delivery.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Bug fix · Worth it: Yes · Fix scope: Complete
User problem: Members receive help instructions pointing to Discord instead of the support destination specified by the area owner.
Reason: The maintainer-authored direction is explicit, and all three named surfaces are updated while retaining existing helper activity.

Merge readiness

✅ Ready for maintainer review

Keep this maintainer-authored draft open: main still contains the old support guidance, and the focused patch has no actionable correctness or security findings.

Priority: P2
Reviewed head: 9f2171313776dacffc43cb798a344af279ac1032

Before merge

None.

Findings

None.

Tests

• Missing end-to-end proof: Live Discord rendering and delivery of the changed messages are not demonstrated; the supplied tests replace external transports.

Agent review details

How this fits together

Hermit receives Discord commands and listener events, selects configured guidance, and sends replies through Carbon and Discord REST.

flowchart TD
 A[Discord command or event] --> B[Hermit registered handlers]
 B --> C[Help snippet]
 B --> D[Welcome template]
 B --> E[Automod configuration]
 C --> F[Discord reply with support link]
 D --> F
 E --> F

Loading

Technical review

Best possible solution:

Retain the focused routing update, existing diagnostic guidance, and separate reminder for long custom welcomes.

Do we have a high-confidence way to reproduce the issue?

Pinned main source directly shows the old Discord support destinations; no target code was executed during this review.

Is this the best way to solve the issue?

The patch updates the existing message owners and preserves valid custom templates without introducing a parallel routing subsystem.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 271ed2f61daa.

Provenance checked

• Help snippet changes intended behavior with a stated reason (3d7bcd6: The earlier refresh consolidated help guidance around a Discord support channel, diagnostic details, and the FAQ.)
• Helper welcome changes intended behavior with a stated reason (f6d15fe: The helper implementation provided configurable onboarding and registered threads before sending their welcome; the subsequent blank-template fallback remains intact.)
• Peter-mention automod guidance changes intended behavior with a stated reason (ae6ce06: The earlier cleanup retained separate help, PR discussion, and Discord-report routes while removing a legacy direct-message contact.)

Testing

Proof path: in-process harness.

Security

None.

Evidence

What I checked:

• Pinned change and current main: The introduced diff updates all three routing surfaces; the pinned main still directs ordinary help into Discord. (src/commands/say.ts:16, 9f2171313776)
• Custom welcome compatibility: The existing override remains intact, blank overrides retain the default fallback, and the support reminder is sent separately when combined text exceeds 4,000 characters. (src/events/threadCreateWelcome.ts:39, 9f2171313776)
• Owner direction and workflow state: The MEMBER-authored PR explicitly establishes the official support destination and mandatory reminder for custom welcomes; GitHub reports a draft with a clean merge state. (9f2171313776)
• Earlier helper design: Add Hermit-managed thread length monitoring #6 established configurable welcome text and tracking before delivery; this PR preserves those owners and operations. (src/events/threadCreateWelcome.ts:54, f6d15fe2aac4)
• Repository policy: The full root AGENTS.md applies; no nested AGENTS.md, maintainer-notes directory, or pr-simplify skill is present. Changed welcomes retain Carbon components, and automod copy remains in its configured source. (AGENTS.md:5, 9f2171313776)
• Supplied validation boundary: The body reports passing tests and explicitly limits the evidence to local serialized REST capture; comments contain workflow status, with no additional live Discord artifact. (tests/supportRouting.test.ts:11, 9f2171313776)

Review metrics

Metric	Value	Why it matters
Change distribution	Production +16/-9; tests +173/-2; documentation +4	Production growth is small; listener tests cover custom welcome boundaries and preserved automod routes.

Labels

Label changes:

• add P2: Correcting support guidance is a useful, limited-scope improvement without evidence of an urgent runtime failure.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

• P2: Correcting support guidance is a useful, limited-scope improvement without evidence of an urgent runtime failure.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed October 20, 2026, 6:16 PM ET / 22:16 UTC.