Greptile Summary

This PR correctly fixes a schema validation gap introduced by the project rename from "clawd" to "openclaw" — the Zod schema now accepts "openclaw" as a valid browser.profiles.*.driver value while retaining "clawd" for backwards compatibility, and the help text and quality test are updated to match.

Key finding:

• The Zod schema (zod-schema.ts) accepts "openclaw" | "clawd" | "extension", but the hand-written TypeScript type in types.browser.ts only declares driver?: "openclaw" | "extension" — "clawd" is not in the TypeScript union. Any code consuming BrowserProfileConfig typed values won't be aware that "clawd" is a valid runtime value, which undermines the backwards-compatibility guarantee at the type level.

Confidence Score: 3/5

• Safe to merge but has a type inconsistency that should be addressed to maintain full type safety for legacy driver values.
• The core fix is correct and resolves a real user-facing validation error. The backwards-compat intent is sound. However, the TypeScript type definition in types.browser.ts is not updated alongside the Zod schema — "clawd" is missing from the driver union type — which means type-safe code consuming parsed config values will be unaware that "clawd" is a valid value.
• src/config/types.browser.ts — needs "clawd" added to the driver union type to match the Zod schema's accepted values.

_{Last reviewed commit: 1c17335}

Fixed — added "clawd" to the BrowserDriverType union in types.browser.ts to keep the TypeScript type in sync with the Zod schema.

Merged via squash.

• Prepared head SHA: 0eba5ab939e8074e44fe45dcb76e1a021d74156b
• Merge commit: e5fdfec9dc1fee5a33775a10f47dc4ff90246737

Thanks @gambletan!