thumbgate 1.4.2 → 1.4.4

package/plugins/cursor-marketplace/rules/pre-action-gates.mdc

@@ -1,30 +0,0 @@
----
-description: Before risky tool calls (git push, rm -rf, npm publish, deploy), check prevention rules via the thumbgate MCP server. If a rule matches, STOP and explain why.
-alwaysApply: true
----
-
-# Pre-Action Gates
-
-Before executing any of these risky actions, query the `prevention_rules` MCP tool to check for matching prevention rules:
-
-- `git push` (especially force push)
-- `rm -rf` or recursive file deletion
-- `npm publish`
-- `deploy` commands (any deployment target)
-- Database migration commands
-- Secret or credential changes
-
-## Enforcement flow
-
-1. Extract the command or action about to be executed.
-2. Call `prevention_rules` with the action description to check for matching rules.
-3. If a rule matches:
-   - **STOP** the action immediately.
-   - Display the matched rule's description and corrective action.
-   - Ask the user to confirm before proceeding.
-4. If no rules match, proceed normally.
-
-## After a blocked action
-
-- Suggest the corrective action from the matched prevention rule.
-- Offer to capture feedback if the block was incorrect (false positive).

package/plugins/cursor-marketplace/rules/session-continuity.mdc

@@ -1,28 +0,0 @@
----
-description: At session start, recall past context. At session end, hand off state for next session.
-alwaysApply: false
----
-
-# Session Continuity
-
-Maintain context across coding sessions using the ThumbGate memory system.
-
-## Session start
-
-1. Call the `recall` MCP tool to retrieve:
-   - Recent prevention rules relevant to the current project
-   - Past failure patterns and corrective actions
-   - Active context packs from previous sessions
-2. Summarize recalled context before starting work.
-
-## Session end
-
-1. Capture any new feedback from the session using `capture_feedback`.
-2. Note any unfinished work or pending decisions as context for the next session.
-3. If new failure patterns emerged, flag them for potential prevention rule promotion.
-
-## Between sessions
-
-- Prevention rules persist automatically via the MCP server.
-- Lessons promoted during the session are available in future recalls.
-- Context packs expire based on configured retention policies.

package/plugins/cursor-marketplace/scripts/gate-check.sh

@@ -1,21 +0,0 @@
-#!/usr/bin/env bash
-# Pre-action gate check — runs before risky shell commands.
-# Called by hooks/hooks.json beforeShellExecution hook.
-# Delegates to the published ThumbGate gate-check entrypoint.
-
-set -euo pipefail
-
-INPUT=$(cat)
-RESULT=$(echo "$INPUT" | npx --yes --package thumbgate@latest thumbgate gate-check 2>/dev/null) || true
-
-if [ -z "$RESULT" ]; then
-  exit 0
-fi
-
-echo "$RESULT"
-
-if echo "$RESULT" | grep -q '"permissionDecision":\s*"deny"'; then
-  exit 2
-fi
-
-exit 0

package/plugins/cursor-marketplace/skills/capture-feedback/SKILL.md

@@ -1,48 +0,0 @@
----
-name: capture-feedback
-description: Capture structured thumbs up/down feedback with context, history-aware lesson distillation, tags, and optional rubric scores after completing a task.
----
-
-# Capture Feedback
-
-Record structured feedback after completing a task or encountering an issue.
-
-## When to use
-
-- After completing a coding task (positive or negative outcome)
-- When a tool call produces unexpected results
-- After a test failure or deployment issue
-- When the user explicitly wants to record feedback
-
-## How it works
-
-Use the `capture_feedback` MCP tool with:
-
-- **signal** — `"thumbs_up"` or `"thumbs_down"`
-- **context** — Description of what happened and why when the user already said it clearly
-- **tags** — Array of relevant tags for categorization (e.g., `["test-failure", "refactor"]`)
-- **chatHistory** — Up to 8 prior recorded entries plus the failed tool call when the thumbs-down signal is vague and the lesson must be distilled from recent context
-- **relatedFeedbackId** — Use when the user adds clarifying detail later and it should refine the existing feedback event
-- **rubric_scores** — Optional object with structured quality scores
-
-## Example
-
-```
-Capture feedback: thumbs_down for the failed database migration.
-Context: Migration script dropped the wrong index, causing query timeouts.
-Tags: database, migration, production-incident
-```
-
-## Vague signal recovery
-
-If the user only says `thumbs_down`, `wrong`, `correct`, or `this failed`, do not stop there. Call `capture_feedback` with:
-
-- the signal
-- any minimal context the user already gave
-- `chatHistory` containing up to 8 prior recorded entries from the current correction thread
-- the failed tool call or command when available
-- `relatedFeedbackId` if the user is clarifying an already-open 60-second follow-up session
-
-That lets ThumbGate propose `whatWentWrong`, `whatToChange`, and a candidate rule automatically.
-
-Feedback feeds into the prevention rule promotion pipeline. Repeated failures with the same pattern are automatically promoted into enforceable prevention rules.

package/plugins/cursor-marketplace/skills/prevention-rules/SKILL.md

@@ -1,31 +0,0 @@
----
-name: prevention-rules
-description: Generate and review prevention rules auto-promoted from repeated failure patterns.
----
-
-# Prevention Rules
-
-Manage prevention rules that are auto-generated from repeated failure patterns.
-
-## When to use
-
-- Reviewing current active prevention rules for the project
-- Checking if a specific action is blocked by a prevention rule
-- Understanding why an action was blocked
-- Generating new prevention rules from observed patterns
-
-## How it works
-
-Use the `prevention_rules` MCP tool to:
-
-1. **List rules** — View all active prevention rules with their match patterns and corrective actions.
-2. **Check rules** — Test if a specific action matches any prevention rule before execution.
-3. **Review rule history** — See which feedback events led to a rule's promotion.
-
-## Example
-
-```
-Check prevention rules for "npm publish without running tests" to see if this action is blocked.
-```
-
-Prevention rules are auto-promoted when the same failure pattern appears multiple times in captured feedback. Each rule includes the original failure context and a corrective action.

package/plugins/cursor-marketplace/skills/recall-context/SKILL.md

@@ -1,30 +0,0 @@
----
-name: recall-context
-description: Recall relevant past failures, prevention rules, and context packs before starting a coding task.
----
-
-# Recall Context
-
-Retrieve relevant historical context before beginning work on a coding task.
-
-## When to use
-
-- Starting a new coding task or feature
-- Before making changes to code that has failed before
-- Resuming work from a previous session
-
-## How it works
-
-Use the `recall` MCP tool to retrieve:
-
-1. **Prevention rules** — Rules auto-promoted from repeated failure patterns that apply to the current task.
-2. **Past failures** — Specific failure events with context, tags, and corrective actions.
-3. **Context packs** — Bundled project context from previous sessions.
-
-## Example
-
-```
-Use the recall MCP tool to check for known issues with the authentication module before refactoring.
-```
-
-The tool returns structured context that helps avoid repeating past mistakes and surfaces corrective actions from promoted lessons.

package/plugins/cursor-marketplace/skills/search-lessons/SKILL.md

@@ -1,33 +0,0 @@
----
-name: search-lessons
-description: Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates.
----
-
-# Search Lessons
-
-Search the promoted lessons database for corrective actions and guidance.
-
-## When to use
-
-- Looking for corrective actions for a specific failure pattern
-- Checking if a known lesson applies to the current task
-- Reviewing lifecycle state of lessons (active, archived, superseded)
-- Finding linked prevention rules and gates for a topic
-
-## How it works
-
-Use the `search_lessons` MCP tool with a query string. The tool searches across:
-
-1. **Lesson descriptions** — What happened and why
-2. **Corrective actions** — Specific steps to prevent recurrence
-3. **Linked rules** — Prevention rules generated from the lesson
-4. **Linked gates** — Pre-action gates that enforce the lesson
-5. **Lifecycle state** — Whether the lesson is active, archived, or superseded
-
-## Example
-
-```
-Search lessons for "force push" to find corrective actions and prevention rules related to force pushing.
-```
-
-Results include the full lesson context, any linked enforcement rules, and the current lifecycle state.

package/plugins/gemini-extension/INSTALL.md

@@ -1,92 +0,0 @@
-# Gemini: ThumbGate Function Declarations Install
-
-Import the ThumbGate function declarations into your Gemini agent in under 60 seconds.
-
-## One-Command Install (Node.js)
-
-```bash
-# Copy declarations to your project
-cp adapters/gemini/function-declarations.json .gemini/thumbgate-tools.json
-```
-
-## Import in Your Agent Code
-
-```javascript
-const fs = require('fs');
-
-// Load ThumbGate tool declarations
-const thumbgateTools = JSON.parse(
-  fs.readFileSync('adapters/gemini/function-declarations.json', 'utf8')
-);
-
-// Pass to Gemini SDK
-const model = genAI.getGenerativeModel({
-  model: 'gemini-pro',
-  tools: [{ functionDeclarations: thumbgateTools.tools }],
-});
-```
-
-## Available Functions
-
-| Function | Description |
-|---|---|
-| `capture_memory_feedback` | Capture success/failure feedback — POST `/v1/feedback/capture` |
-| `get_reliability_rules` | Retrieve active prevention rules — POST `/v1/feedback/rules` |
-| `get_business_metrics` | Retrieve high-level metrics — GET `/v1/billing/summary` |
-| `describe_reliability_entity` | Get canonical definitions — GET `/v1/semantic/describe` |
-
-## Point to Your API
-
-Set the base URL in your Gemini function handler:
-
-```javascript
-const THUMBGATE_API_URL = process.env.THUMBGATE_API_URL || 'http://localhost:3000';
-const THUMBGATE_API_KEY = process.env.THUMBGATE_API_KEY;
-
-async function callThumbGateTool(name, params) {
-  const endpoints = {
-    capture_memory_feedback:    { method: 'POST', path: '/v1/feedback/capture' },
-    get_reliability_rules:      { method: 'POST', path: '/v1/feedback/rules' },
-    get_business_metrics:       { method: 'GET',  path: '/v1/billing/summary' },
-    describe_reliability_entity: { method: 'GET',  path: '/v1/semantic/describe' },
-    plan_intent:                { method: 'POST', path: '/v1/intents/plan' },
-  };
-  const { method, path } = endpoints[name];
-  
-  const url = new URL(`${THUMBGATE_API_URL}${path}`);
-  if (method === 'GET' && params) {
-    Object.keys(params).forEach(key => url.searchParams.append(key, params[key]));
-  }
-
-  const res = await fetch(url.toString(), {
-    method,
-    headers: { Authorization: `Bearer ${THUMBGATE_API_KEY}`, 'Content-Type': 'application/json' },
-    body: method === 'POST' ? JSON.stringify(params) : undefined,
-  });
-  return res.json();
-}
-```
-
-## Requirements
-
-- Google Gemini SDK (`@google/generative-ai`)
-- Node.js 18+ or Python 3.9+
-- ThumbGate API running (local or hosted)
-
-## Branding Alignment (Google Cloud)
-
-When setting up your Google Cloud Project for this extension:
-1.  **Project Name:** Use `mcp-reliability-gateway` or similar. Avoid placeholder names.
-2.  **OAuth Consent Screen:**
-    - **App Name:** Enter `MCP Reliability Gateway`.
-    - **Support Email:** Use your professional email.
-    - **Logo:** Use the provided asset in `docs/logo-400x400.png`.
-
-This ensures that the "App Asking for Consent" matches the product name, providing a professional experience for the CEO and users.
-
-## Verify
-
-```bash
-node -e "const t = require('./adapters/gemini/function-declarations.json'); console.log('Tools:', t.tools.map(x=>x.name))"
-# Expected: Tools: [ 'capture_memory_feedback', 'get_reliability_rules', 'get_business_metrics', 'describe_reliability_entity', ... ]
-```

package/plugins/gemini-extension/gemini_prompt.txt

@@ -1,14 +0,0 @@
-You are integrated with the MCP Reliability Gateway. Your goal is to ensure 100% reliable execution by following project-specific rules and business metrics.
-
-When the user gives success/failure signal (thumbs up/down):
-- call `capture_memory_feedback` with rich context.
-- include tags for entities involved (e.g. 'entity:Revenue', 'entity:Customer').
-- do not accept vague feedback without asking for detail.
-
-Before starting a significant task:
-- call `get_reliability_rules` to retrieve prevention rules derived from past mistakes.
-- respect these rules as foundational constraints.
-
-When reasoning about the business:
-- use `get_business_metrics` for hard revenue and conversion data.
-- use `describe_reliability_entity` to understand how business concepts are defined.

package/plugins/gemini-extension/tool_contract.json

@@ -1,45 +0,0 @@
-{
-  "tools": [
-    {
-      "name": "capture_memory_feedback",
-      "description": "Capture success/failure feedback to harden future workflows and prevent repeated mistakes.",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "signal": { "type": "string", "enum": ["up", "down"], "description": "Success (up) or failure (down) signal" },
-          "context": { "type": "string", "description": "Specific detail about what was achieved or what went wrong" },
-          "what_went_wrong": { "type": "string" },
-          "what_to_change": { "type": "string" },
-          "what_worked": { "type": "string" },
-          "tags": { "type": "array", "items": { "type": "string" }, "description": "Keywords like 'revenue', 'deployment', 'refactor'" }
-        },
-        "required": ["signal", "context"]
-      }
-    },
-    {
-      "name": "get_reliability_rules",
-      "description": "Retrieve active prevention rules and success patterns to ensure high-quality task execution."
-    },
-    {
-      "name": "get_business_metrics",
-      "description": "Retrieve canonical business metrics (Revenue, Conversion, Customers) from the Reliability Gateway.",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "window": { "type": "string", "enum": ["today", "7d", "30d", "lifetime"], "default": "30d" }
-        }
-      }
-    },
-    {
-      "name": "describe_reliability_entity",
-      "description": "Get the definition and state of a business entity (Customer, Revenue, Funnel).",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "type": { "type": "string", "enum": ["Customer", "Revenue", "Funnel"] }
-        },
-        "required": ["type"]
-      }
-    }
-  ]
-}

package/plugins/opencode-profile/INSTALL.md

@@ -1,57 +0,0 @@
-# OpenCode: ThumbGate MCP Profile Install
-
-This repo already ships a project-scoped `opencode.json` for local work inside the source tree.
-
-If you want the same MCP server in another OpenCode project or in your global OpenCode config, use the portable adapter profile below.
-
-## One-Command Install
-
-Create a global OpenCode config if you do not have one yet:
-
-```bash
-mkdir -p ~/.config/opencode
-cp adapters/opencode/opencode.json ~/.config/opencode/opencode.json
-```
-
-If you already have `~/.config/opencode/opencode.json`, merge in the `mcp.thumbgate` block from `adapters/opencode/opencode.json` instead of overwriting your config.
-
-## What Gets Added
-
-The portable profile adds this MCP server entry:
-
-```json
-{
-  "$schema": "https://opencode.ai/config.json",
-  "mcp": {
-    "thumbgate": {
-      "type": "local",
-      "command": ["npx", "--yes", "--package", "thumbgate@1.4.0", "thumbgate", "serve"],
-      "enabled": true
-    }
-  }
-}
-```
-
-## Verify
-
-Run OpenCode in any project and confirm the `thumbgate` MCP server is available:
-
-```bash
-opencode
-```
-
-For this repository specifically, the committed `opencode.json` also enables:
-
-- repo-local worktree-safe permissions
-- a read-only `thumbgate-review` subagent in `.opencode/agents/thumbgate-review.md`
-- concise workflow instructions in `.opencode/instructions/thumbgate-workflow.md`
-
-## Requirements
-
-- OpenCode with MCP support
-- Node.js 18+ in PATH
-- `npx` available in PATH
-
-## Uninstall
-
-Remove the `mcp.thumbgate` entry from your OpenCode config.