mirror of
https://github.com/openclaw/clawhub.git
synced 2026-08-14 08:52:21 +00:00
clawsweeper[bot]momothemageclawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>momothemageSummary: - The PR adds an admin-only personal publisher recovery flow with HTTP API, admin CLI support, shared response schema, docs/spec notes, and tests. - Reproducibility: yes. Source inspection shows current main lacks a publisher-recovery route and personal pub ... to an existing ClawHub user, so a replacement GitHub principal has no staff recovery path without this PR. Automerge notes: - PR branch already contained follow-up commit before automerge: fix: migrate publisher recovery resource owners - PR branch already contained follow-up commit before automerge: fix: add guarded personal publisher recovery Validation: - ClawSweeper review passed for head5cfb360520. - Required merge gates passed before the squash merge. Prepared head SHA:5cfb360520Review: https://github.com/openclaw/clawhub/pull/2642#issuecomment-4704078560 Co-authored-by: momothemage <niuzhengnan@163.com> Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Approved-by: momothemage Co-authored-by: momothemage <35096042+momothemage@users.noreply.github.com>
summary, read_when
| summary | read_when | ||
|---|---|---|---|
| Public ClawHub docs index and reading order. |
|
Docs
docs/ is the publishable source for user-facing ClawHub pages that can be
mirrored into the ClawHub tab on docs.openclaw.ai.
Keep product, CLI, publisher, API, policy, security, and troubleshooting docs here. These pages should explain how people use ClawHub: discover, install, publish, inspect, report, moderate, and integrate with the registry.
Use specs/ for repository setup, production deploy runbooks, implementation
plans, design rationale, regression notes, maintainer validation records, and
internal subsystem intent. If a page tells someone how to run or deploy the
ClawHub project itself, it belongs in specs/, not in the public OpenClaw docs
tab.
Reading order:
docs/clawhub.md: public overview for discovery, install, publish, and trust.docs/quickstart.md: product quickstart for users and publishers.docs/how-it-works.md: listings, versions, installs, publishing, scans, and API access.docs/publishing.md: owner-scoped skill/plugin publishing flow.docs/cli.md: ClawHub CLI reference.docs/skill-format.md: skill bundle metadata and package shape.docs/auth.md: GitHub OAuth, API tokens, and CLI login.docs/telemetry.md: install telemetry and how to opt out.docs/troubleshooting.md: user-facing CLI, install, publish, sync, update, and API fixes.
Policy, API, and trust docs:
docs/acceptable-usage.md: marketplace policy and enforcement boundaries.docs/api.md: public REST API overview.docs/http-api.md: detailed HTTP API reference.docs/security.md: reporting ClawHub security issues and vulnerability disclosure policy.docs/security-audits.md: user-facing security audit status, risk levels, findings, and interpretation.docs/moderation.md: reports, moderation holds, hidden listings, bans, and account standing.
Maintainer records:
specs/README.md: index for specs, plans, deployment runbooks, webhook notes, regression notes, and design records.
Publish flow:
- Changes under
docs/dispatch the OpenClaw docs sync workflow, which mirrors this directory into theClawHubtab ondocs.openclaw.ai. specs/is intentionally not mirrored.