Merge release/0.3.0 into main for v0.3.0-rc.3#92
Merged
Merged
Conversation
Replace `gh api .../releases/generate-notes` with `scripts/release-notes.mjs`, which walks the full commit range between the previous v* tag and the current tag and groups conventional-commit subjects into 4 emoji'd buckets: ✨ Features & Polish (feat, polish) 🐛 Fixes (fix) 🔧 CI & Tests (ci, test, build, perf, refactor) 📦 Release (chore, docs, style) 📝 Misc (anything unmatched; omitted if empty) Each item resolves to its associated PR via the GitHub commit→PR endpoint (parallelized). The built-in generate-notes call only saw the single release→main merge PR because git-flow merges land on the release branch, not main — so rc.2's release page shipped with an empty What's Changed section. publish-release now checks out with fetch-depth: 0 + fetch-tags: true so `git describe --tags $TAG^` and the log range resolve correctly.
ci(release): custom changelog grouped by commit type
Add a new top-level section to README.md between "What You Can Do Today" and "Roadmap" that walks through the product visually across 8 capability surfaces: - Overview dashboard - Guided setup wizard (2-step, rc.2's 3-tier provider layout) - Models and providers - Gateway and channels - Observability - Memory - Skills, plugins, and MCP - Settings Screenshots live under docs/screenshots/ (10 PNGs, ~3.4 MB total, 1280–1440 px wide for Retina). Captured against the running dev server with the dev-browser skill so they reflect real UI state, not mocks — in particular the wizard shot showcases the rc.2 provider tier polish.
Shrink the feature overview to a single 2x3 HTML table, one image per
tile with a one-line subtitle. Drop the long captions and individual
subheadings — visitors can click through to the full-size screenshot
if they want detail.
Drop 4 screenshots that didn't show solid surfaces in a fresh dev env:
- page-observe.png — rendered the "ClawProbe is not installed" empty
state (requires ClawProbe daemon for live data)
- page-skills.png — Skill Market surfaced an HTTP 500 from a missing
backend module
- page-settings.png — mostly static preference toggles, low signal
- wizard-models.png — wizard provider tile already conveys the flow
Six tiles remain: Setup wizard, Overview, Models, Channels, Memory,
MCP. Each links to the full-resolution PNG.
Install clawprobe + clawhub globally in the dev env, restart the backend so execOpenclaw re-caches the now-resolvable binary, and re-capture the two previously-broken pages: - Observe now renders live ClawProbe stats (session, context, cost trend) instead of the "ClawProbe is not installed" prompt - Skills now loads the ClawHub marketplace instead of surfacing the HTTP 500 from the missing openclaw binary Grid expanded to 2 rows x 4 cols (Setup · Overview · Models · Channels on top; Observe · Memory · MCP · Skills below). Subtitles stay short.
docs(readme): add Product Feature Overview with curated screenshots
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Why
Users need a reliable way to switch npm installs to a mirror when the default registry is slow or blocked. This also needs to apply consistently across install paths and runtimes, and it must not leave the persisted setting out of sync with the last UI action.
How
npm mirrorScreenshots
Pending. This change updates the setup wizard and settings UI.
Validation
npx vitest run src/modules/setup/__tests__/SetupWizard.test.tsx src/modules/settings/__tests__/CapabilitiesSection.test.tsxNotes