You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CLAWHUB_READINESS.md
+16-10Lines changed: 16 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ Last audited: 2026-05-26
4
4
5
5
## Status
6
6
7
-
The plugin packageand local OpenClaw/Mautic stack are ready for ClawHub review, but public ClawHub deployment is blocked until the source repository is accessible to ClawHub.
7
+
The plugin package, public GitHub source, and local OpenClaw/Mautic stack are ready for ClawHub review.
GitHub reports the repository exists but is private. ClawHub community publishing expects source metadata that ClawHub can fetch and review. To finish public deployment, either make the repository public or configure a private-source review path supported by ClawHub.
55
+
Result: passed. ClawHub can fetch and package the public GitHub source.
50
56
51
57
Local-folder dry run with explicit source metadata:
This validates the local package shape. It does not remove the public-source review concern for a public ClawHub listing.
74
+
This validates the local package shape before publishing.
69
75
70
76
## Local Stack Security
71
77
@@ -88,8 +94,8 @@ Gateway auth rate limiting is configured:
88
94
89
95
## Deployment Decision
90
96
91
-
Do not publish this package publicly to ClawHub while the repository remains private unless ClawHub has an approved private-source review workflow for this owner.
97
+
The package is ready for ClawHub publish from the public `main` branch after an operator intentionally runs the publish command.
92
98
93
-
`npm run clawhub:publish`enforces that decision by refusing private-source publishing unless `CLAWHUB_ALLOW_PRIVATE_SOURCE=1` is set after review access is approved.
99
+
`npm run clawhub:publish`still guards against accidental private-source publishing if the repository visibility changes later.
94
100
95
-
If the repository stays private, use `docs/PRIVATE_SOURCE_REVIEW_REQUEST.md` as the handoff packet for ClawHub private-source review.
101
+
If the repository is made private again, use `docs/PRIVATE_SOURCE_REVIEW_REQUEST.md` as the handoff packet for a private-source review path.
Copy file name to clipboardExpand all lines: docs/COMPLETION_AUDIT.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,7 @@ Objective: make the `mautic-control` OpenClaw plugin production-ready for ClawHu
6
6
7
7
## Result
8
8
9
-
The plugin package is production-prepped for ClawHub package review and private/internal OpenClaw deployment. Public ClawHub listing remains blocked because the GitHub source repository is private and direct ClawHub GitHub-source dry-run cannot fetch it.
10
-
11
-
Do not mark public ClawHub deployment complete until one of these is true:
12
-
13
-
- The repository is made public.
14
-
- ClawHub has an approved private-source review path for `CompleteTech-LLC-AI-Research/openclaw-mautic-plugin`.
9
+
The plugin package is production-ready for ClawHub package review from the public GitHub repository. Local stack behavior is preserved, production defaults are restrictive, and the direct GitHub-source ClawHub dry run passes.
15
10
16
11
## Prompt-To-Artifact Checklist
17
12
@@ -41,7 +36,8 @@ Do not mark public ClawHub deployment complete until one of these is true:
41
36
| CI workflow |`.github/workflows/ci.yml` runs lint, tests, and package validation | Complete |
42
37
| ClawHub dry-run |`npm run clawhub:dry-run` passes from local folder with source metadata | Complete |
43
38
| Accidental publish guard |`npm run clawhub:publish` refuses private source unless `CLAWHUB_ALLOW_PRIVATE_SOURCE=1` is set after private-source review approval | Complete |
44
-
| Direct GitHub-source ClawHub dry-run |`clawhub package publish CompleteTech-LLC-AI-Research/openclaw-mautic-plugin --dry-run` fails because repo is private | Blocked |
39
+
| Direct GitHub-source ClawHub dry-run |`clawhub package publish CompleteTech-LLC-AI-Research/openclaw-mautic-plugin --dry-run` passes from public `main`| Complete |
40
+
| Public source access | GitHub repo visibility is public and `npm run readiness:check` verifies ClawHub can fetch it | Complete |
45
41
| Repo clean and pushed |`git status --short --branch` reports `main...origin/main` after latest push | Complete |
Copy file name to clipboardExpand all lines: docs/PRIVATE_SOURCE_REVIEW_REQUEST.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,19 @@
1
1
# Private Source Review Request
2
2
3
-
Use this when requesting a ClawHub private-source review path for `mautic-control`.
3
+
Historical/alternate handoff only. The repository is currently public, so this private-source path is not needed for standard ClawHub review. Use this if the repository is made private again and ClawHub supports private-source review for `mautic-control`.
CompleteTech LLC AI Research is keeping the source repository private unless ClawHub requires a public source repository for marketplace listing. The package is prepared for review with explicit source metadata and a reproducible local ClawHub dry run.
16
+
CompleteTech LLC AI Research may make the source repository private again after review. The package is prepared for review with explicit source metadata and reproducible local and GitHub-source ClawHub dry runs.
0 commit comments