thumbgate 1.4.3 → 1.4.4

package/plugins/codex-profile/INSTALL.md

@@ -1,89 +0,0 @@
-# ThumbGate for Codex
-
-ThumbGate now ships a standalone Codex plugin bundle, a repo-local Codex app plugin surface, and the version-pinned MCP profile.
-
-## Option 1: Use the standalone release bundle
-
-Download the latest bundle:
-
-- `https://github.com/IgorGanapolsky/ThumbGate/releases/latest/download/thumbgate-codex-plugin.zip`
-
-Or build it from source:
-
-```bash
-npm run build:codex-plugin
-```
-
-After extracting `thumbgate-codex-plugin.zip`, the folder already contains:
-
-- `.codex-plugin/plugin.json`
-- `.mcp.json`
-- `.agents/plugins/marketplace.json`
-- `config.toml`
-
-The bundled marketplace catalog points at `./`, so the extracted directory is a self-contained plugin root instead of a repo-relative stub.
-
-## Option 2: Use the repo-local plugin files
-
-## Shipped plugin files
-
-- Codex plugin manifest: `plugins/codex-profile/.codex-plugin/plugin.json`
-- Codex MCP config: `plugins/codex-profile/.mcp.json`
-- Codex marketplace entry: `.agents/plugins/marketplace.json`
-- Manual install profile: `adapters/codex/config.toml`
-
-## Option 3: Manual MCP install
-
-Add the MCP server block to your Codex config:
-
-```bash
-cat adapters/codex/config.toml >> ~/.codex/config.toml
-```
-
-Or create the config file if it does not exist:
-
-```bash
-mkdir -p ~/.codex
-cat adapters/codex/config.toml >> ~/.codex/config.toml
-```
-
-## What Gets Added
-
-The following block is appended to `~/.codex/config.toml`:
-
-```toml
-[mcp_servers.thumbgate]
-command = "npx"
-args = ["--yes", "--package", "thumbgate@1.4.3", "thumbgate", "serve"]
-```
-
-The repo-local Codex app plugin ships the same runtime path through `plugins/codex-profile/.mcp.json`, so the manual config and plugin metadata stay aligned.
-
-## Verify
-
-Start the MCP server manually to confirm it runs:
-
-```bash
-node adapters/mcp/server-stdio.js
-# Expected: MCP server listening on stdio
-# Press Ctrl+C to stop
-```
-
-Then restart Codex. The `thumbgate` MCP server will appear in the tool list.
-
-## Available Tools (via MCP)
-
-- `capture_feedback` — POST `/v1/feedback/capture`
-- `feedback_summary` — GET `/v1/feedback/summary`
-- `prevention_rules` — POST `/v1/feedback/rules`
-- `plan_intent` — POST `/v1/intents/plan`
-
-## Requirements
-
-- Codex with MCP support
-- Node.js 18+ in PATH
-- Config file at `~/.codex/config.toml` when using the manual MCP install path
-
-## Uninstall
-
-Remove the `[mcp_servers.thumbgate]` section from `~/.codex/config.toml`.

package/plugins/codex-profile/README.md

@@ -1,61 +0,0 @@
-# ThumbGate for Codex
-
-ThumbGate now ships a standalone Codex plugin bundle in GitHub Releases, alongside the repo-local Codex profile in this repository.
-
-## Release surfaces
-
-- Latest standalone bundle: `https://github.com/IgorGanapolsky/ThumbGate/releases/latest/download/thumbgate-codex-plugin.zip`
-- Versioned bundle pattern: `https://github.com/IgorGanapolsky/ThumbGate/releases/download/v<VERSION>/thumbgate-codex-plugin-v<VERSION>.zip`
-- Source plugin manifest: `plugins/codex-profile/.codex-plugin/plugin.json`
-- Source MCP config: `plugins/codex-profile/.mcp.json`
-- Manual install profile: `adapters/codex/config.toml`
-
-## What it does
-
-- adds ThumbGate's Pre-Action Gates to Codex workflows
-- captures thumbs-up/down feedback that survives session boundaries
-- reuses the same local-first MCP runtime as Claude, Cursor, Gemini, Amp, and OpenCode
-
-## What's inside the standalone bundle
-
-- `.codex-plugin/plugin.json`
-- `.mcp.json`
-- `.agents/plugins/marketplace.json`
-- `config.toml`
-- `README.md`, `INSTALL.md`, and `AGENTS.md`
-
-The bundled marketplace catalog rewrites the plugin path to `./`, so the extracted folder can act as a self-contained plugin root instead of depending on this repository layout.
-
-## Install paths
-
-### Standalone Codex plugin bundle
-
-Download the latest `thumbgate-codex-plugin.zip`, unzip it, and point Codex at the extracted `thumbgate-codex-plugin/` directory when you want a standalone plugin release surface.
-
-### Repo-local Codex app plugin
-
-Use the plugin metadata and MCP config in this folder when Codex is loading plugin surfaces directly from the repository.
-
-### Manual install
-
-Copy the MCP profile from `adapters/codex/config.toml` into `~/.codex/config.toml`.
-
-That profile launches:
-
-```toml
-[mcp_servers.thumbgate]
-command = "npx"
-args = ["--yes", "--package", "thumbgate@1.4.3", "thumbgate", "serve"]
-```
-
-### Build from source
-
-Build the same standalone release bundle locally with:
-
-```bash
-npm run build:codex-plugin
-```
-
-## Why this exists
-
-The Codex support story is no longer just "copy this config block." ThumbGate now has a direct-download Codex plugin bundle, a repo-local plugin surface, and a pinned manual MCP profile so release assets, install docs, and the runtime stay aligned.

package/plugins/cursor-marketplace/.cursor-plugin/plugin.json

@@ -1,23 +0,0 @@
-{
-  "name": "thumbgate",
-  "displayName": "ThumbGate",
-  "description": "👍👎 Thumbs down a mistake — your AI agent won't repeat it. Thumbs up good work — it remembers the pattern.",
-  "version": "1.4.3",
-  "author": {
-    "name": "Igor Ganapolsky"
-  },
-  "homepage": "https://thumbgate-production.up.railway.app",
-  "repository": "https://github.com/IgorGanapolsky/ThumbGate",
-  "license": "MIT",
-  "keywords": [
-    "cursor",
-    "cursor-plugin",
-    "feedback",
-    "thumbs-up-down",
-    "thumbgate",
-    "ai-agent-memory",
-    "mistake-prevention",
-    "coding-agent"
-  ],
-  "logo": "assets/logo-400x400.png"
-}

package/plugins/cursor-marketplace/CHANGELOG.md

@@ -1,30 +0,0 @@
-# Changelog
-
-## 0.8.1 - 2026-03-26
-
-- Unified ThumbGate branding across all public surfaces (README, AGENTS.md, CLAUDE.md, GEMINI.md, landing page, package.json).
-- Landing page SEO: "human-in-the-loop enforcement", "vibe coding" positioning, FAQPage JSON-LD schema for Google rich results.
-- Added congruence CI check (`scripts/check-congruence.js`) — enforces version, branding, tech stack terms, and honest disclaimer across README and landing page on every PR.
-- Performance: deferred non-critical side-effects in `captureFeedback` (contextFs, RLAIF self-audit) via `setImmediate`.
-- Added `_captureMs` timing field to accepted feedback responses for observability.
-- Added `mcpize.yaml` to version sync targets.
-- Dead code removal: -1,551 lines (contract-audit.js, prove-rlaif.js, stale landing-page.html, 3 duplicate docs).
-- Fixed GitGuardian incident #29200799: scrubbed hardcoded Google API key from git history.
-- Social automation pipeline: post-everywhere CLI, reply monitor with AutoMod-safe Reddit posts.
-- TDS article draft: "Beyond Prompt Rules: How Pre-Action Gates Stop AI Coding Agents From Repeating Mistakes".
-
-## 0.8.0 - 2026-03-25
-
-- **Lesson DB:** SQLite + FTS5 full-text search replaces linear Jaccard token-overlap. Sub-millisecond ranked search indexed by signal, domain, tags, importance.
-- **Corrective actions:** On negative feedback, `capture_feedback` returns `correctiveActions[]` — top 3 remediation steps inferred from similar past failures.
-- **search_lessons MCP tool:** Exposes corrective actions, lifecycle state, linked rules, linked gates, and next harness fixes per lesson.
-- **search_thumbgate MCP tool:** Searches raw ThumbGate state across feedback logs, ContextFS memory, and prevention rules.
-- **Rejection ledger:** Tracks why vague feedback was rejected with revival conditions.
-- **Bayesian belief updates:** Each memory carries a posterior that updates on new evidence; high-entropy contradictions auto-prune.
-
-## 0.7.4 - 2026-03-20
-
-- Added `session_handoff` and `session_primer` MCP tools for seamless cross-session context continuity.
-- New `session` namespace in ContextFS stores primer.json with auto-captured git state (branch, last 5 commits, modified files, working tree status), last completed task, next step, and blockers.
-- `session_handoff` records provenance events for full audit trail of session transitions.
-- Closes Layer 2 (primer.md) of the 5-layer memory stack — no manual primer file needed.

package/plugins/cursor-marketplace/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 Igor Ganapolsky
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/plugins/cursor-marketplace/README.md

@@ -1,124 +0,0 @@
-# ThumbGate — for Cursor
-
-`ThumbGate` is the human-facing plugin name in Cursor listings.
-`thumbgate` stays the plugin slug, npm package, and launcher target.
-
-The canonical short description is:
-
-> 👍👎 Thumbs down a mistake — your AI agent won't repeat it. Thumbs up good work — it remembers the pattern.
-
-How it works:
-
-- 👎 **Thumbs down** a mistake — it gets blocked from happening again
-- 👍 **Thumbs up** good work — the agent remembers the pattern
-- **History-aware lesson distillation** — vague thumbs-down signals can be grounded in up to 8 prior recorded entries and the failed tool call
-- **Cross-session memory** — lessons persist between conversations
-- **Automatic enforcement** — repeated failures become prevention rules
-- **Zero config** — install and start giving feedback
-
-## What's included
-
-### Rules
-
-| File | Always on | Description |
-|------|-----------|-------------|
-| `rules/pre-action-gates.mdc` | Yes | Before risky tool calls (git push, rm -rf, npm publish, deploy), check prevention rules via the thumbgate MCP server. Blocks and explains if a rule matches. |
-| `rules/feedback-capture.mdc` | No | After any mistake or unexpected behavior, prompt to capture structured feedback with context and tags. |
-| `rules/session-continuity.mdc` | No | At session start, recall past context; at session end, hand off state for next session. |
-
-### Skills
-
-| Skill | Description |
-|-------|-------------|
-| `recall-context` | Recall relevant past failures, prevention rules, and context packs before starting a coding task. |
-| `capture-feedback` | Capture structured thumbs up/down feedback with context, tags, and optional rubric scores. |
-| `search-lessons` | Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates. |
-| `prevention-rules` | Generate and review prevention rules auto-promoted from repeated failure patterns. |
-
-### Agent
-
-| Agent | Description |
-|-------|-------------|
-| `reliability-reviewer` | A reliability-focused reviewer that checks code changes against known failure patterns from the project's ThumbGate memory. |
-
-### Commands
-
-| Command | Description |
-|---------|-------------|
-| `/check-gates` | Run a Pre-Action Gate check against prevention rules before executing a risky action. |
-| `/show-lessons` | Display promoted lessons and their corrective actions. |
-| `/capture-feedback` | Quick feedback capture with structured signals. |
-
-### Hooks
-
-| Hook | Trigger | Description |
-|------|---------|-------------|
-| `beforeShellExecution` | `git push`, `rm -rf`, `npm publish`, `deploy` | Runs `scripts/gate-check.sh` to evaluate the command through ThumbGate `gate-check` before execution. |
-
-### MCP Server
-
-| Server | Command |
-|--------|---------|
-| `thumbgate` | `npx --yes --package thumbgate@latest thumbgate serve` |
-
-## Install
-
-### Cursor Marketplace
-
-Search for **ThumbGate** in the Cursor marketplace and install.
-
-### Team Marketplace
-
-Cursor Teams and Enterprise can import this repository through `Dashboard -> Settings -> Plugins -> Team Marketplaces`. If Cursor exposes `Enable Auto Refresh`, turn it on so repo-backed plugin updates refresh automatically.
-
-### Cursor Directory
-
-Treat Cursor Directory as a discoverability surface, not the runtime distribution channel. It helps people find the plugin, but npm releases do not rewrite directory copy on their own. The Cursor Directory does not auto-refresh from npm.
-
-If a manual submission form asks for `Name`, use `ThumbGate` instead of the slug.
-
-### Manual setup
-
-Use the existing project bootstrap:
-
-```bash
-npx thumbgate init
-```
-
-Or copy the plugin MCP config into `.cursor/mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "thumbgate": {
-      "command": "npx",
-      "args": ["--yes", "--package", "thumbgate@latest", "thumbgate", "serve"]
-    }
-  }
-}
-```
-
-## Update behavior
-
-- Runtime updates: the plugin asks npm for `thumbgate@latest`, so new npm releases can flow into the Cursor runtime without editing the plugin config.
-- Metadata updates: `npm publish` does not refresh the marketplace description, screenshots, README, or directory listing copy. Republish the plugin bundle when those assets change.
-- Guaranteed rollouts: if you need deterministic behavior for a specific release, pin a version manually in local config instead of relying on `@latest`.
-
-## Feedback
-
-Use the `/capture-feedback` command or the `capture_feedback` MCP tool to send structured feedback directly to the ThumbGate memory system. Feedback drives prevention rule generation — repeated failure patterns are auto-promoted into enforceable gates.
-
-When the user only gives a quick `thumbs_down`, `wrong`, or `correct`, the Cursor plugin should include up to 8 prior recorded entries and the failed tool call in `chatHistory` so ThumbGate can propose the lesson automatically. If the explanation comes later, reuse the earlier event with `relatedFeedbackId` so the linked 60-second follow-up session refines the same feedback record instead of creating an isolated duplicate.
-
-## What makes this useful in Cursor
-
-ThumbGate gives Cursor agents a practical guardrail layer:
-
-- **Pre-Action Gates** block known-bad actions before tool use
-- **Prevention rules** auto-generated from repeated failures
-- **Context packs** keep relevant project history in scope
-- **Feedback capture** with structured up/down signals and history-aware lesson proposals
-- **Reliability reviewer** checks changes against known failure patterns
-
-Verification evidence for shipped behavior lives in `docs/VERIFICATION_EVIDENCE.md`.
-Release and promotion rules live in `docs/CURSOR_PLUGIN_OPERATIONS.md`.

package/plugins/cursor-marketplace/agents/reliability-reviewer.md

@@ -1,31 +0,0 @@
----
-name: reliability-reviewer
-description: A reliability-focused reviewer agent that checks code changes against known failure patterns from the project's ThumbGate memory. Prioritizes preventing repeated mistakes.
----
-
-# Reliability Reviewer
-
-You are a reliability-focused code reviewer. Your job is to check proposed code changes against the project's known failure patterns stored in ThumbGate memory.
-
-## Review process
-
-1. **Recall context** — Use the `recall` MCP tool to retrieve relevant prevention rules and past failures for the files being changed.
-2. **Search lessons** — Use the `search_lessons` MCP tool to find promoted lessons related to the components being modified.
-3. **Cross-reference changes** — Compare the proposed changes against known failure patterns. Flag any changes that match or resemble past failures.
-4. **Check gates** — Use the `prevention_rules` MCP tool to verify no active prevention rules are violated by the changes.
-5. **Report findings** — Summarize which past failures are relevant, what risks exist, and what corrective actions should be applied.
-
-## Review priorities
-
-1. **Repeated mistakes** — Changes that match previously captured failure patterns are highest priority.
-2. **Missing gate checks** — Risky operations without corresponding pre-action gate checks.
-3. **Untested paths** — Changes to code paths that previously caused failures without new test coverage.
-4. **Feedback gaps** — Changes in areas with no captured feedback history (unknown risk).
-
-## Output format
-
-For each finding, include:
-- The matched failure pattern or prevention rule
-- The specific code change that triggered the match
-- The recommended corrective action
-- Severity: critical (matches active prevention rule), warning (matches past failure), or info (no history)

package/plugins/cursor-marketplace/commands/capture-feedback.md

@@ -1,33 +0,0 @@
----
-name: capture-feedback
-description: Quick feedback capture with structured signals.
----
-
-# Capture Feedback
-
-Quickly capture structured feedback about the current task or action.
-
-## Usage
-
-Invoke this command to record a feedback signal with context and tags. If the user only gives a quick `thumbs_down`, `wrong`, or `correct`, the command should still call `capture_feedback` and pass recent context through `chatHistory`.
-
-## Steps
-
-1. Specify signal: `thumbs_up` or `thumbs_down`.
-2. If the user already gave a clear explanation, pass it as `context`.
-3. If the explanation is vague or omitted, gather up to 8 prior recorded entries plus the failed tool call into `chatHistory`.
-4. Add tags for categorization.
-5. If this is a later clarification for an existing feedback event, include `relatedFeedbackId`.
-6. Call the `capture_feedback` MCP tool and show the proposed lesson or corrective rule back to the user.
-
-## Example
-
-```
-/capture-feedback thumbs_down "Tests broke after migration" database,migration
-```
-
-```
-/capture-feedback thumbs_down
-```
-
-In the second example, the command should rely on history-aware distillation instead of refusing the signal outright. If the user adds more detail later, reuse `relatedFeedbackId` so the linked 60-second follow-up session updates the same record.

package/plugins/cursor-marketplace/commands/check-gates.md

@@ -1,25 +0,0 @@
----
-name: check-gates
-description: Run a Pre-Action Gate check against prevention rules before executing a risky action.
----
-
-# Check Gates
-
-Run a pre-action gate check to verify if a planned action is safe to execute.
-
-## Usage
-
-Invoke this command before performing risky operations like deployments, force pushes, or destructive file operations.
-
-## Steps
-
-1. Describe the action you are about to take.
-2. The command queries the `prevention_rules` MCP tool to check for matching rules.
-3. If a match is found, the blocked action and corrective action are displayed.
-4. If no match is found, the action is cleared to proceed.
-
-## Example
-
-```
-/check-gates git push --force origin main
-```

package/plugins/cursor-marketplace/commands/show-lessons.md

@@ -1,27 +0,0 @@
----
-name: show-lessons
-description: Display promoted lessons and their corrective actions.
----
-
-# Show Lessons
-
-Display promoted lessons from the project's ThumbGate memory along with their corrective actions and linked prevention rules.
-
-## Usage
-
-Invoke this command to review what the system has learned from past failures.
-
-## Steps
-
-1. The command calls the `search_lessons` MCP tool to retrieve all active promoted lessons.
-2. Results are displayed with:
-   - Lesson description
-   - Corrective action
-   - Linked prevention rules (if any)
-   - Lifecycle state (active, archived, superseded)
-
-## Example
-
-```
-/show-lessons
-```

package/plugins/cursor-marketplace/hooks/hooks.json

@@ -1,10 +0,0 @@
-{
-  "hooks": {
-    "beforeShellExecution": [
-      {
-        "command": "./scripts/gate-check.sh",
-        "matcher": "git push|rm -rf|npm publish|deploy"
-      }
-    ]
-  }
-}

package/plugins/cursor-marketplace/mcp.json

@@ -1,14 +0,0 @@
-{
-  "mcpServers": {
-    "thumbgate": {
-      "command": "npx",
-      "args": [
-        "--yes",
-        "--package",
-        "thumbgate@latest",
-        "thumbgate",
-        "serve"
-      ]
-    }
-  }
-}

package/plugins/cursor-marketplace/rules/feedback-capture.mdc

@@ -1,34 +0,0 @@
----
-description: After any mistake or unexpected behavior, prompt to capture structured feedback with context, history-aware lesson distillation, and tags.
-alwaysApply: false
----
-
-# Feedback Capture
-
-After any mistake, unexpected behavior, or completed task, prompt to capture structured feedback.
-
-## When to trigger
-
-- A tool call produces an unexpected error
-- A test fails after code changes
-- The user corrects an approach mid-task
-- A task completes successfully (capture positive signal)
-
-## How to capture
-
-1. Call the `capture_feedback` MCP tool with:
-   - `signal`: "thumbs_up" or "thumbs_down"
-   - `context`: Brief description of what happened when the explanation is already explicit
-   - `tags`: Relevant tags (e.g., "test-failure", "wrong-approach", "deployment-error")
-   - `chatHistory`: up to 8 prior recorded entries plus the failed tool call when the thumbs-down signal is vague and the lesson should be inferred from recent conversation
-   - `relatedFeedbackId`: use for a later clarification that should refine an existing feedback event
-   - `rubric_scores`: Optional structured scores if a rubric applies
-
-2. Include enough context so the feedback is useful for future prevention rule generation.
-3. If the user only gives a bare thumbs signal or short correction, still capture it and let ThumbGate propose `whatWentWrong` / `whatToChange` from recent history. If the explanation arrives later, reuse `relatedFeedbackId` so the linked 60-second follow-up session refines the same record.
-
-## Examples
-
-- Test failure after refactor: signal=thumbs_down, tags=["test-failure", "refactor"], context="Tests broke after extracting helper function — missed internal dependency"
-- Successful deployment: signal=thumbs_up, tags=["deployment", "success"], context="Clean deploy after running gate checks"
-- Vague correction after failed tool use: signal=thumbs_down, chatHistory=[up to 8 prior recorded entries + failed tool call], tags=["wrong-approach", "tool-failure"]

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.