refactor(build): generate MCP tool catalog at build time instead of committing it (#997)

src/generatedMcpToolCatalog.ts had zero runtime importers and churned on every contract edit, guaranteeing merge conflicts on long-lived branches. It is now gitignored and regenerated by build:unlocked; typecheck and knip depend on build via turbo. Tests consume the build output unchanged. Adds a regen-generated CI workflow that pushes tracked generated metadata (product catalog, skill frontmatter, verification manifest/ledger, package metadata, error schema) to same-repo PR branches.

scripts/generate-mcp-tool-catalog.mjs

@@ -17,8 +17,9 @@ for (const argument of arguments_)
     throw new Error(`Unknown MCP tool catalog option: ${argument}`);
 
 const root = join(dirname(fileURLToPath(import.meta.url)), "..");
-// The checked-in catalog is a portable package artifact. Keep its canonical
-// provider metadata independent of the machine running the generator.
+// The build-generated catalog is a portable package artifact that is not
+// committed to git. Keep its canonical provider metadata independent of the
+// machine running the generator. It is regenerated by `npm run build`.
 const CATALOG_PLATFORM = "darwin";
 const sessionToolNames = new Set([
   ...TOOL_CONTRACTS.filter(({ kind }) => kind === "session").map(