fix(goose): preserve builtin extensions in config.yaml and stop emitting dead hook matchers

[dyoshikawa]

Fixes the three concrete Goose bugs recorded in the 2026-07-30 re-check comment on #2404. The open design item (gap 1, goose review checks-surface ownership) is untouched, so the issue stays open.

1. Global MCP generate deleted the user's builtin extensions (data loss)

GooseMcp.fromRulesyncMcp merged with { ...config, extensions: convertToGooseFormat(...) }, replacing the entire extensions: map. Starting from a config.yaml holding the standard developer and memory builtins, a global MCP generate produced a file containing only the rulesync servers — and losing developer costs the agent its shell and text-editor tools.

~/.config/goose/config.yaml is now declared in the shared-config gateway with mcp owning extensions, and the block is recomputed from the existing file before being applied: entries whose type is not one of stdio / streamable_http / sse (Goose's own builtin / platform / frontend / inline_python extensions) are carried over untouched, while every MCP-typed entry stays rulesync-owned, so a server deleted from .rulesync/.mcp.json is still retracted. Every other Goose setting (model, provider, ...) is preserved by the gateway's replace-owned-keys policy, and the file is declared invalidRootPolicy: "error" so a config that cannot be parsed aborts the write instead of being replaced.

2. Import rewrote builtin / platform extensions as broken stdio entries

developer: {type: builtin, bundled: true, timeout: 300} imported to a type-less server and regenerated as {name: developer, type: stdio, timeout: 300} with no cmd — a working builtin turned into an extension Goose cannot start. Non-MCP extension types are now skipped on import with a warning (they stay in config.yaml, which generation preserves), and generate never synthesizes a stdio extension without cmd: a canonical server with neither command nor url is skipped with a warning instead.

3. A "*" hook matcher silently killed the whole Goose hook rule

Goose compiles matcher with Regex::new and, on failure, logs "Invalid hook matcher regex; skipping rule" and drops the entire rule; a bare "*" is not a valid regex, and the v1.44.0 docs state outright that it is silently skipped. rulesync emitted the canonical matcher verbatim, so a shared canonical hooks file produced dead hooks on Goose.

The shared hooks converter gained a wildcardMatcherMeansAll option — the same "treat "*" as no matcher" rule amp-plugin-generator.ts, opencode-style-generator.ts, pi-extension-generator.ts and vibe-hooks.ts already apply — and goose-hooks.ts opts in. It normalizes at grouping time, so a "*" group collapses into the matcher-less group rather than emitting a second indistinguishable bare entry.

Verification

New unit tests cover builtin/platform preservation with retraction of a deleted MCP server, the command-less skip, the import skip, and the matcher collapse. Full pnpm cicheck is green, plus e2e-mcp.spec.ts and e2e-hooks.spec.ts.

Part of #2404

🤖 Generated with Claude Code