nimai-core 0.4.9 → 0.5.1

package/data/FORGE-spec-template.md

@@ -1,454 +0,0 @@
-# FORGE Spec Template
-> **You are here:** This is the Spec Template — the execution tool. Use it to turn a project direction into a complete agent-ready brief.
->
-> **The other docs in this system:**
-> - **Quick Reference** (`FORGE-quickref.md`) — start here if you don't have a project direction yet. If the request is a new idea or open-ended, go to the Quick Reference and run the Divergence → Convergence Loop or the Self-Spec Agent first. Come back here once you have a chosen direction.
-> - **Canonical Framework** (`FORGE-canonical.md`) — go there if you encounter a concept in this template you don't fully understand. Each section maps to a section in the canonical doc.
->
-> **When to be in this doc:** You have a specific project or direction. You are ready to define it completely before handing it to an agent. If you can't fill in a field, that is an unresolved decision — resolve it here, not mid-run.
->
-> **Solo operator shortcut:** Instead of filling this manually, use the Self-Spec Agent prompt in the Quick Reference to generate a draft, then review and approve it here.
-
----
-
-> Fill in every field before handing to an agent. A blank field is an unresolved decision — resolve it here, not mid-run.
-> *Based on the FORGE*
-
----
-
-## 0. Pre-Flight Decisions
-> These must be set first. Everything else is built on top of them.
-
-**Risk Tier:** [ ] Low  [ ] Medium  [ ] High
-*(If unsure, go one tier higher)*
-
-**Primary Cognitive Mode for this project:**
-[ ] Deterministic  [ ] Exploratory  [ ] Adversarial  [ ] Synthesis  [ ] Audit
-[ ] Multi-phase — using Divergence → Convergence Loop (see Section 6)
-*→ Unsure which mode? See Cognitive Mode table in Quick Reference or Canonical doc.*
-
-**Resource Governance:**
-- Model tier (Planner): `_______________`
-- Model tier (Workers): `_______________`
-- Max runtime per sub-task: `_______________`
-- Total compute / cost budget: `_______________`
-- Retry limit before escalation: `_______________`
-- Cost threshold that triggers stop-and-report: `_______________`
-
----
-
-## 1. Specification Layer — The Blueprint
-
-### 1.1 Final Deliverable
-*Describe precisely. Not "a good analysis" — describe the exact artifact, format, and measurable quality.*
-
-```
-Deliverable: _______________________________________________
-
-Format: ___________________________________________________
-
-Length / Size: _____________________________________________
-
-Measurable quality bar: ____________________________________
-
-Benchmark dataset (if quality bar requires measurement):
-  path: _______________  (e.g. tests/fixtures/receipts/ or N/A)
-  schema: _____________  (field names and types of each labeled example, or N/A)
-  threshold computation rule: ___  (e.g. "pass rate = correct / total labeled examples", or N/A)
-```
-
-### 1.2 Scope Boundaries
-*Be explicit. Ambiguity here becomes scope creep mid-run.*
-
-**In scope:**
-- `_______________`
-- `_______________`
-- `_______________`
-
-**Out of scope (Must-Not):**
-- `_______________`
-- `_______________`
-- `_______________`
-
-### 1.3 Task Decomposition
-*Break the project into sub-tasks. Each must satisfy the 5 Primitives and complete in under 2 hours.*
-*→ Need a reminder of the 5 Primitives? See Quick Reference or Canonical doc Section "5 Primitives."*
-
-| # | Sub-task | Cognitive Mode | Risk Tier | Acceptance Criteria | Eval Method |
-|---|---|---|---|---|---|
-| 1 | | | | | |
-| 2 | | | | | |
-| 3 | | | | | |
-| 4 | | | | | |
-| 5 | | | | | |
-
-*Add rows as needed. Every sub-task needs all five columns filled.*
-
-*Note: Sub-task risk tiers may differ from the overall project tier. A research sub-task and a production deployment sub-task in the same project have different risk profiles — assign each independently. The project-level tier sets the floor for escalation; sub-task tiers govern validation routing.*
-
-### 1.4 Acceptance Criteria — Master Definition of Done
-*Binary. Measurable. No subjective criteria.*
-
-The project is complete when ALL of the following are true:
-- [ ] `_______________`
-- [ ] `_______________`
-- [ ] `_______________`
-
----
-
-## 1.5 Mechanism Decision
-*One block per core architectural or algorithmic choice. If no core mechanism applies, write "N/A" and justify.*
-*A builder must be able to start coding without choosing missing architecture. If any mechanism is undecided, resolve it here first.*
-
----
-
-**Decision: [short name, e.g., "Primary parsing method"]**
-
-```
-Chosen approach: _______________________________________________
-
-Rejected alternatives: _________________________________________
-
-Why rejected: __________________________________________________
-
-Impact on ACs: _________________________________________________
-```
-
----
-
-## 1.6 Architecture Lock
-*Required for medium/high coding specs. Advisory for low/unknown/non-coding specs.*
-*All fields must be resolved before builder handoff. Blank placeholders and "TBD" are unresolved.*
-
-```
-Persistence layer: _______________________________________________
-
-File/object storage: _____________________________________________
-
-External model/service + env var: ________________________________
-
-API trigger flow: ________________________________________________
-
-Entity status state machine: _____________________________________
-
-Auth implementation: _____________________________________________
-```
-
----
-
-## 2. Intent Layer — The Compass
-
-### 2.1 Agent Deployment Purpose
-*Tell the agent what it is, what it is not, and who consumes its output. One clear paragraph.*
-
-```
-You are: ___________________________________________________
-
-You are NOT responsible for: _______________________________
-
-Your output is consumed by: ________________________________
-  (human decision-maker / another agent / automated pipeline)
-
-Your output feeds into: ____________________________________
-```
-
-### 2.2 Trade-off Hierarchy
-*Rank these in order of priority. The agent will use this when it hits a fork.*
-
-Rank the following from 1 (highest) to n (lowest) for this task:
-
-| Priority | Value |
-|---|---|
-| `___` | Accuracy / Correctness |
-| `___` | Speed / Efficiency |
-| `___` | Cost / Token economy |
-| `___` | Safety / Risk avoidance |
-| `___` | Novelty / Creativity |
-| `___` | Completeness |
-| `___` | Simplicity / Readability |
-| `___` | *(add domain-specific value)* |
-
-### 2.3 Constraint Architecture
-
-**Must (non-negotiable requirements):**
-- `_______________`
-- `_______________`
-
-**Must-Not (hard prohibitions):**
-- `_______________`
-- `_______________`
-
-**Prefer (soft preferences when trade-offs arise):**
-- `_______________`
-- `_______________`
-
-**Escalate (stop and surface to human when):**
-- `_______________`
-- `_______________`
-
-### 2.4 Forbidden Approaches
-*Specific methods, tools, frameworks, or reasoning patterns to avoid.*
-
-- `_______________`
-- `_______________`
-
----
-
-## 3. Context Layer — The Environment
-
-### 3.1 Provided Context
-*List all documents, artifacts, or data sources being provided. Mark each as AUTHORITATIVE or REFERENCE.*
-
-| Source | Type | Authority Level | Notes |
-|---|---|---|---|
-| | | AUTHORITATIVE / REFERENCE | |
-| | | AUTHORITATIVE / REFERENCE | |
-| | | AUTHORITATIVE / REFERENCE | |
-
-### 3.2 Known State
-*What has already been tried? What failed? What is known?*
-
-```
-Prior attempts: ____________________________________________
-
-Known failures / dead ends: ________________________________
-
-Known constraints: _________________________________________
-
-Current blockers: __________________________________________
-```
-
-### 3.3 Context Freshness
-*Tell the agent when to trust the provided context vs. when to re-fetch or verify.*
-
-[ ] All provided context is current — use as ground truth
-[ ] The following sources may be stale and should be verified: `_______________`
-[ ] The agent must re-fetch live data for: `_______________`
-[ ] MCP connections available: `_______________`
-
-### 3.4 Domain Conventions
-*Terminology, style, standards, or norms the agent must match.*
-
-```
-Terminology to use: ________________________________________
-
-Terminology to avoid: ______________________________________
-
-Style / format standards: __________________________________
-
-Domain-specific conventions: _______________________________
-```
-
----
-
-## 4. Prompt Layer — The Trigger
-
-### 4.1 Opening System Instruction
-*The master instruction that frames the entire run. Reference Sections 1–3 explicitly.*
-
-```
-You are [deployment purpose from 2.1].
-
-Your task is to produce [deliverable from 1.1].
-
-You are operating within the following constraints: [from 2.3].
-
-Your trade-off priority order is: [from 2.2].
-
-The context you have been provided is: [from 3.1].
-
-You will complete this task by executing the following sub-tasks in order: [from 1.3].
-
-For each sub-task, your completion criterion is: [from 1.4].
-```
-
-### 4.2 Per-Sub-Task Prompt Template
-*Use this template for each sub-task trigger.*
-
-```
-Sub-task [#]: [name]
-Cognitive mode: [mode]
-Your input: [what you're working from]
-Your output: [exact format and content required]
-Acceptance criteria: [binary criteria from 1.3]
-Evaluation: [how this will be checked]
-Resource cap: [max runtime / tokens for this sub-task]
-```
-
----
-
-## 5. Governance & Validation
-
-### 5.1 Escalation Contract
-
-**Escalation triggers** *(from 2.3 — repeated here for executor clarity)*:
-- `_______________`
-- `_______________`
-
-**Who reviews escalations:**
-```
-Name / Role: _______________________________________________
-Contact: __________________________________________________
-Response SLA: ______________________________________________
-```
-
-**If no response arrives within SLA, the agent should:**
-[ ] Hold and wait
-[ ] Attempt alternative path: `_______________`
-[ ] Abort and report
-
-### 5.2 Adversarial Reflection Trigger
-*(Required for Medium and High risk tasks)*
-
-[ ] Not required (Low risk)
-[ ] Required after sub-task(s): `_______________`
-[ ] Required before final delivery
-
-The agent should critique: `_______________`
-The revision threshold is: `_______________` *(what level of critique warrants a revision?)*
-
-### 5.3 Uncertainty Reporting
-*(Required for non-deterministic domains)*
-
-[ ] Not required
-[ ] Required — agent must report:
-  - Confidence estimate (0–100%) with justification
-  - Primary uncertainty drivers
-  - What data would most reduce uncertainty
-  - Alternative plausible interpretations
-
----
-
-## 6. Brainstorming Mode (Divergence → Convergence)
-*Complete this section only if primary mode is multi-phase brainstorming.*
-
-**Phase 1 — DIVERGE (Exploratory Mode)**
-```
-Generate: _________________________________________________
-Constraint: No filtering or judgment at this stage.
-Output format: ____________________________________________
-Volume target: ____________________________________________
-```
-
-**Phase 2 — CLUSTER (Synthesis Mode)**
-```
-Organize the output of Phase 1 by: ________________________
-Identify: _________________________________________________
-Output format: ____________________________________________
-```
-
-**Phase 3 — STRESS-TEST (Adversarial Mode)**
-```
-Attack the top [n] candidates from Phase 2.
-Criteria to stress-test against: __________________________
-Output format: ____________________________________________
-What constitutes a fatal flaw: ____________________________
-```
-
-**Phase 4 — FORMALIZE (Deterministic Mode)**
-```
-Selected direction: ______________________________________
-Formalize as: ____________________________________________
-Acceptance criteria: _____________________________________
-```
-
----
-
-## 7. Domain-Specific Additions
-
-### If Coding:
-- Language / framework / version: `_______________`
-- Performance targets: `_______________`
-- API / interface contracts: `_______________`
-- Security requirements: `_______________`
-- Test coverage expectation: `_______________`
-
-### If Science / Research:
-- Null hypothesis: `_______________`
-- Falsification criteria: `_______________`
-- Authorized data sources: `_______________`
-- Forbidden data sources: `_______________`
-- Statistical significance threshold: `_______________`
-- Correction method: `_______________`
-- Reproducibility requirements: `_______________`
-
-### If Writing / Content:
-- Audience: `_______________`
-- Purpose: `_______________`
-- Structure: `_______________`
-- Word count / length: `_______________`
-- Style reference: `_______________`
-- Mandatory inclusions: `_______________`
-- Mandatory exclusions: `_______________`
-
-### If Business / Strategy:
-- Decision-maker: `_______________`
-- Decision to be made: `_______________`
-- Options to evaluate: `_______________`
-- Recommendation format: `_______________`
-- Regulatory Must-Nots: `_______________`
-- Stakeholder sensitivities: `_______________`
-
----
-
-## 8. Spec Validation (Red-Team Checklist)
-*Complete before handing to the agent. Every unchecked box is a known risk.*
-
-**5 Primitives — does every sub-task have:**
-- [ ] A self-contained problem statement (zero questions needed to start)
-- [ ] A Constraint Architecture (Must / Must-Not / Prefer / Escalate)
-- [ ] A runtime under 2 hours
-- [ ] Binary acceptance criteria
-- [ ] A built-in evaluation method
-
-**Failure Mode Taxonomy — does this spec prevent:**
-- [ ] Scope Creep — explicit Must-Not list and scope boundaries
-- [ ] Hallucinated Completion — binary acceptance criteria defined
-- [ ] Intent Drift — ranked trade-offs and deployment purpose explicit
-- [ ] Context Collapse — context curated; noise removed
-- [ ] Runaway Cost — resource caps set before decomposition
-- [ ] Overconfident Output — uncertainty reporting required (if applicable)
-
-**Final gate:**
-- [ ] Risk tier and resource governance set *before* decomposition
-- [ ] Every agent has a deployment purpose statement
-- [ ] Escalation contract complete (who, when, SLA, no-response behavior)
-- [ ] Planner execution plan will be saved as artifact
-
----
-
-## 8.5 Edge Cases and Failure Modes
-> Required for medium/high risk specs. Red-team the spec before builder handoff.
-> For each scenario, document what the spec says the builder must do. A blank list is a hard stop.
-
-**FORGE failure mode coverage:**
-- Scope Creep — which Must-Not explicitly prevents it: `_______________`
-- Hallucinated Completion — which AC is hardest to fake: `_______________`
-- Intent Drift — which decision will the builder most likely get wrong: `_______________`
-- Context Collapse — what context is load-bearing and must not be dropped: `_______________`
-- Runaway Cost — what resource cap prevents unbounded execution: `_______________`
-- Overconfident Output — what requires uncertainty reporting: `_______________`
-
-**Domain-specific edge cases:**
-- `_______________`
-- `_______________`
-
----
-
-## 9. Spec Convergence
-> Fill before handing to a builder. A non-zero count or "no" is a hard stop.
-> Every [NEEDS HUMAN INPUT] flag from spec drafting must be resolved before this section is filled.
-
-```
-open_questions: 0
-ambiguities_remaining: 0
-ready_for_build: yes
-convergence_notes: _______________________________________________
-```
-
----
-
-*FORGE Spec Template v1.0 — companion to the FORGE system. A blank field is an unresolved decision.*
-*System docs: Quick Reference · Canonical Framework · Spec Template (this doc)*
-
-<!-- nimai-spec -->

package/dist/clarification.d.ts

@@ -1,22 +0,0 @@
-/**
- * Rule-based clarification heuristics for nimai_spec.
- *
- * These are pure functions — no IO, no LLM calls.
- * Trigger `clarifications_needed` when any heuristic fires.
- */
-export interface ClarificationResult {
-    needed: boolean;
-    reasons: string[];
-    questions: string[];
-}
-/**
- * Evaluate whether a spec request needs clarification before drafting.
- *
- * Heuristics (any one firing triggers clarification):
- * 1. Request is under 10 words
- * 2. Zero repo files matched by context extractor
- * 3. No domain nouns or action verbs detected
- * 4. Conflicting stack hints (two competing tech choices in same category)
- */
-export declare function detectClarifications(request: string, contextFileCount: number): ClarificationResult;
-//# sourceMappingURL=clarification.d.ts.map

package/dist/clarification.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"clarification.d.ts","sourceRoot":"","sources":["../src/clarification.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAuEH,MAAM,WAAW,mBAAmB;IAClC,MAAM,EAAE,OAAO,CAAC;IAChB,OAAO,EAAE,MAAM,EAAE,CAAC;IAClB,SAAS,EAAE,MAAM,EAAE,CAAC;CACrB;AAED;;;;;;;;GAQG;AACH,wBAAgB,oBAAoB,CAClC,OAAO,EAAE,MAAM,EACf,gBAAgB,EAAE,MAAM,GACvB,mBAAmB,CA+BrB"}

package/dist/clarification.js

@@ -1,106 +0,0 @@
-"use strict";
-/**
- * Rule-based clarification heuristics for nimai_spec.
- *
- * These are pure functions — no IO, no LLM calls.
- * Trigger `clarifications_needed` when any heuristic fires.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.detectClarifications = detectClarifications;
-// ─── Domain noun / action vocab ───────────────────────────────────────────────
-/**
- * Minimum set of technical domain nouns and action verbs that indicate the
- * request describes a real engineering task. If the request contains none of
- * these, it is likely too vague to spec reliably.
- */
-const DOMAIN_TOKENS = new Set([
-    // Action verbs
-    'add', 'build', 'create', 'implement', 'fix', 'refactor', 'update', 'migrate',
-    'design', 'integrate', 'deploy', 'remove', 'generate', 'optimize', 'extend',
-    'replace', 'extract', 'expose', 'wire', 'scaffold', 'test', 'benchmark',
-    // Technical nouns
-    'api', 'service', 'component', 'model', 'module', 'database', 'endpoint',
-    'interface', 'schema', 'type', 'function', 'class', 'route', 'handler',
-    'middleware', 'auth', 'token', 'config', 'cli', 'ui', 'hook', 'store',
-    'query', 'mutation', 'event', 'queue', 'cache', 'index', 'migration',
-    'server', 'client', 'backend', 'frontend', 'test', 'spec', 'pipeline',
-    'workflow', 'adapter', 'plugin', 'sdk', 'contract', 'validator', 'parser',
-]);
-/**
- * Returns true if the request contains at least one recognizable domain token.
- */
-function hasDomainNoun(request) {
-    const words = request.toLowerCase().match(/\b[a-z]+\b/g) ?? [];
-    return words.some(w => DOMAIN_TOKENS.has(w));
-}
-// ─── Conflicting stack detection ──────────────────────────────────────────────
-/** Groups of mutually-competing technology choices. Two items from the same group = conflict. */
-const STACK_GROUPS = [
-    // Programming languages — any two in the same request signals ambiguous stack
-    [
-        'python', 'ruby', 'java', 'golang', 'rust', 'kotlin', 'swift', 'scala',
-        'php', 'elixir', 'csharp', 'typescript', 'javascript',
-    ],
-    // JS UI frameworks
-    ['react', 'vue', 'angular', 'svelte'],
-    // CSS frameworks
-    ['tailwind', 'bootstrap'],
-    // Relational databases
-    ['postgresql', 'postgres', 'mysql', 'sqlite'],
-    // NoSQL databases
-    ['mongodb', 'dynamodb', 'firestore', 'cassandra'],
-    // JS test frameworks
-    ['jest', 'vitest', 'jasmine'],
-];
-/**
- * Returns true if the request mentions ≥2 items from the same competing stack group,
- * indicating an ambiguous or conflicting technology choice.
- */
-function hasConflictingStack(request) {
-    const lower = request.toLowerCase();
-    for (const group of STACK_GROUPS) {
-        const hits = group.filter(tech => {
-            // Match as whole word or compound (e.g. "typescript", "vue.js")
-            const pattern = new RegExp(`\\b${tech.replace(/[-.]/g, '[-.\\s]?')}\\b`, 'i');
-            return pattern.test(lower);
-        });
-        if (hits.length >= 2)
-            return true;
-    }
-    return false;
-}
-/**
- * Evaluate whether a spec request needs clarification before drafting.
- *
- * Heuristics (any one firing triggers clarification):
- * 1. Request is under 10 words
- * 2. Zero repo files matched by context extractor
- * 3. No domain nouns or action verbs detected
- * 4. Conflicting stack hints (two competing tech choices in same category)
- */
-function detectClarifications(request, contextFileCount) {
-    const reasons = [];
-    const wordCount = request.trim().split(/\s+/).length;
-    if (wordCount < 10) {
-        reasons.push(`request is too short (${wordCount} words — add more context)`);
-    }
-    if (contextFileCount === 0) {
-        reasons.push('no relevant repo files matched — is the repo path correct, or is this a new project?');
-    }
-    if (!hasDomainNoun(request)) {
-        reasons.push('no recognizable domain nouns or action verbs found — describe what should be built or changed');
-    }
-    if (hasConflictingStack(request)) {
-        reasons.push('conflicting technology stack hints detected — clarify which stack applies or separate into distinct tasks');
-    }
-    const needed = reasons.length > 0;
-    const questions = needed
-        ? [
-            'What is the primary goal or outcome you want to achieve?',
-            'Which specific files, components, or systems should be modified?',
-            'Are there constraints, dependencies, or requirements we should be aware of?',
-        ]
-        : [];
-    return { needed, reasons, questions };
-}
-//# sourceMappingURL=clarification.js.map

package/dist/clarification.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"clarification.js","sourceRoot":"","sources":["../src/clarification.ts"],"names":[],"mappings":";AAAA;;;;;GAKG;;AAsFH,oDAkCC;AAtHD,iFAAiF;AAEjF;;;;GAIG;AACH,MAAM,aAAa,GAAG,IAAI,GAAG,CAAC;IAC5B,eAAe;IACf,KAAK,EAAE,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,KAAK,EAAE,UAAU,EAAE,QAAQ,EAAE,SAAS;IAC7E,QAAQ,EAAE,WAAW,EAAE,QAAQ,EAAE,QAAQ,EAAE,UAAU,EAAE,UAAU,EAAE,QAAQ;IAC3E,SAAS,EAAE,SAAS,EAAE,QAAQ,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,EAAE,WAAW;IACvE,kBAAkB;IAClB,KAAK,EAAE,SAAS,EAAE,WAAW,EAAE,OAAO,EAAE,QAAQ,EAAE,UAAU,EAAE,UAAU;IACxE,WAAW,EAAE,QAAQ,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS;IACtE,YAAY,EAAE,MAAM,EAAE,OAAO,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO;IACrE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAE,OAAO,EAAE,OAAO,EAAE,OAAO,EAAE,WAAW;IACpE,QAAQ,EAAE,QAAQ,EAAE,SAAS,EAAE,UAAU,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU;IACrE,UAAU,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,UAAU,EAAE,WAAW,EAAE,QAAQ;CAC1E,CAAC,CAAC;AAEH;;GAEG;AACH,SAAS,aAAa,CAAC,OAAe;IACpC,MAAM,KAAK,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,aAAa,CAAC,IAAI,EAAE,CAAC;IAC/D,OAAO,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;AAC/C,CAAC;AAED,iFAAiF;AAEjF,iGAAiG;AACjG,MAAM,YAAY,GAAe;IAC/B,8EAA8E;IAC9E;QACE,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAE,OAAO;QACtE,KAAK,EAAE,QAAQ,EAAE,QAAQ,EAAE,YAAY,EAAE,YAAY;KACtD;IACD,mBAAmB;IACnB,CAAC,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,QAAQ,CAAC;IACrC,iBAAiB;IACjB,CAAC,UAAU,EAAE,WAAW,CAAC;IACzB,uBAAuB;IACvB,CAAC,YAAY,EAAE,UAAU,EAAE,OAAO,EAAE,QAAQ,CAAC;IAC7C,kBAAkB;IAClB,CAAC,SAAS,EAAE,UAAU,EAAE,WAAW,EAAE,WAAW,CAAC;IACjD,qBAAqB;IACrB,CAAC,MAAM,EAAE,QAAQ,EAAE,SAAS,CAAC;CAC9B,CAAC;AAEF;;;GAGG;AACH,SAAS,mBAAmB,CAAC,OAAe;IAC1C,MAAM,KAAK,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC;IACpC,KAAK,MAAM,KAAK,IAAI,YAAY,EAAE,CAAC;QACjC,MAAM,IAAI,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE;YAC/B,gEAAgE;YAChE,MAAM,OAAO,GAAG,IAAI,MAAM,CAAC,MAAM,IAAI,CAAC,OAAO,CAAC,OAAO,EAAE,UAAU,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC;YAC9E,OAAO,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAC7B,CAAC,CAAC,CAAC;QACH,IAAI,IAAI,CAAC,MAAM,IAAI,CAAC;YAAE,OAAO,IAAI,CAAC;IACpC,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAUD;;;;;;;;GAQG;AACH,SAAgB,oBAAoB,CAClC,OAAe,EACf,gBAAwB;IAExB,MAAM,OAAO,GAAa,EAAE,CAAC;IAE7B,MAAM,SAAS,GAAG,OAAO,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC;IACrD,IAAI,SAAS,GAAG,EAAE,EAAE,CAAC;QACnB,OAAO,CAAC,IAAI,CAAC,yBAAyB,SAAS,4BAA4B,CAAC,CAAC;IAC/E,CAAC;IAED,IAAI,gBAAgB,KAAK,CAAC,EAAE,CAAC;QAC3B,OAAO,CAAC,IAAI,CAAC,sFAAsF,CAAC,CAAC;IACvG,CAAC;IAED,IAAI,CAAC,aAAa,CAAC,OAAO,CAAC,EAAE,CAAC;QAC5B,OAAO,CAAC,IAAI,CAAC,+FAA+F,CAAC,CAAC;IAChH,CAAC;IAED,IAAI,mBAAmB,CAAC,OAAO,CAAC,EAAE,CAAC;QACjC,OAAO,CAAC,IAAI,CAAC,2GAA2G,CAAC,CAAC;IAC5H,CAAC;IAED,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC;IAElC,MAAM,SAAS,GAAa,MAAM;QAChC,CAAC,CAAC;YACE,0DAA0D;YAC1D,kEAAkE;YAClE,6EAA6E;SAC9E;QACH,CAAC,CAAC,EAAE,CAAC;IAEP,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,SAAS,EAAE,CAAC;AACxC,CAAC"}

package/dist/context.d.ts

@@ -1,3 +0,0 @@
-import { ContextItem } from './types';
-export declare function extractContext(repoPath: string, request: string): ContextItem[];
-//# sourceMappingURL=context.d.ts.map

package/dist/context.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../src/context.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,WAAW,EAAE,MAAM,SAAS,CAAC;AA4DtC,wBAAgB,cAAc,CAAC,QAAQ,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,WAAW,EAAE,CAiB/E"}