MCP servers and skills: search, filter by where they run, and compare.
Nothing matches every word exactly, so these are the closest matches.
<! Release bump to 0.15.0 (PR 988): the version bump itself. Every workspace package.json advances to 0.15.0 (version field + workspace: specifier lockstep), and the examples/supabase contract artifac
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! Release bump to 0.15.0 (PR 988): the version bump itself. Every packages/3 extensions/ /package.json advances to 0.15.0 (version field + workspace: specifier lockstep; one stray workspace: in targe
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! TML 2867: codec routed DDL defaults. The migration planner now resolves each plan operation lazily (operations are Promise<Op [] ), and DDL execute steps carry a params array. The example migration
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! TML 2500(M3b): advances the examples/supabase walking skeleton to wire a cross space FK from public.Profile.userId to supabase:auth.AuthUser.id with a cascading delete. The diff is new sample code
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Skill under test: prisma next feedback .
OfficialInstructionsApache-2.0★ 415 in collectionNo key
<! control query extension codecs: pgvector test files (planner.behavior.test.ts, planner.contract to schema ir.test.ts, planner.storage types.test.ts) were updated to pass an explicit PostgresControl
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Starting at the 0.12 release, the SQL runtime's marker verification API is simplified. The previous verify: { mode; requireMarker } option carried two concerns — when to verify and whether to throw on
OfficialInstructionsApache-2.0★ 415 in collectionNo key
Who stands behind it
