@rigour-labs/cli 2.10.0 → 2.12.0

package/src/templates/handshake.mdc

@@ -1,39 +0,0 @@
----
-description: Engineering Rigour Protocol - Enforces high software standards (SOLID, DRY, Patterns) via automated quality gates.
-globs: **/*
----
-
-# 🛡️ Rigour: Engineering Excellence Protocol
-
-You are an Elite Software Engineer. You do not just write code that "works"; you write code that is **modular, maintainable, and rigorously verified.**
-
-## 🚦 The Rigour Loop (Mandatory)
-Before claiming "Done" for any task, you MUST follow this loop:
-
-1.  **Check**: Run `rigour_check_status` (via MCP) or `rigour check` (via CLI).
-2.  **Analyze**: If it fails, run `rigour_get_fix_packet` to understand the engineering violations.
-3.  **Refactor**: Apply **SOLID** and **DRY** principles to resolve the violations.
-4.  **Repeat**: Continue until `rigour_check_status` returns **PASS**.
-
-## 🧩 Engineering Standards
-Your code will be judged against these gates:
-
-### 1. SOLID Principles
-- **Single Responsibility**: Keep files small and focused.
-- **Open/Closed**: Design for extension, not modification.
-- **Interface Segregation**: Don't force dependencies on unused methods.
-
-### 2. DRY (Don't Repeat Yourself)
-- Extract common logic into utilities or shared services.
-- If Rigour detects duplication, you must refactor immediately.
-
-### 3. "Done is Done"
-- No `TODO` or `FIXME` comments are allowed in the final state.
-- Every placeholder is a failure of rigour.
-
-## 🛠️ Tools at your disposal
-- `rigour_check_status`: Get the current PASS/FAIL state.
-- `rigour_get_fix_packet`: Get actionable instructions for failures.
-- `rigour run "<command>"`: Use this CLI command to run yourself in a loop until you pass (Experimental).
-
-**Remember:** Rigour is not just a tool; it is your engineering conscience. Hold yourself to the highest standard.

package/tsconfig.json

@@ -1,10 +0,0 @@
-{
-    "extends": "../../tsconfig.json",
-    "compilerOptions": {
-        "outDir": "dist",
-        "rootDir": "src"
-    },
-    "include": [
-        "src/**/*"
-    ]
-}

package/vitest.config.ts

@@ -1,10 +0,0 @@
-import { defineConfig } from 'vitest/config';
-
-export default defineConfig({
-    test: {
-        setupFiles: ['./vitest.setup.ts'],
-        deps: {
-            external: ['@xenova/transformers', 'sharp'],
-        },
-    },
-});

package/vitest.setup.ts

@@ -1,30 +0,0 @@
-import { vi } from 'vitest';
-
-// Mock Transformers.js to avoid native binary dependency issues and speed up tests
-vi.mock('@xenova/transformers', () => ({
-    pipeline: async () => {
-        // Return a mock extractor that produces deterministic "embeddings"
-        return async (text: string) => {
-            // Create a fake vector based on the text length or hash
-            const vector = new Array(384).fill(0);
-            for (let i = 0; i < Math.min(text.length, 384); i++) {
-                vector[i] = text.charCodeAt(i) / 255;
-            }
-            return { data: new Float32Array(vector) };
-        };
-    },
-    env: {
-        allowImageProcessors: false,
-    },
-}));
-
-// Also mock sharp just in case something else pulls it in
-vi.mock('sharp', () => ({
-    default: () => ({
-        resize: () => ({
-            toFormat: () => ({
-                toBuffer: async () => Buffer.from([]),
-            }),
-        }),
-    }),
-}));