bluera-knowledge 0.9.21

package/tests/fixtures/github-readmes/react.md

@@ -0,0 +1,74 @@
+# React
+
+[React](https://react.dev/) is a JavaScript library for building user interfaces.
+
+* **Declarative:** React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. Declarative views make your code more predictable, simpler to understand, and easier to debug.
+* **Component-Based:** Build encapsulated components that manage their own state, then compose them to make complex UIs. Since component logic is written in JavaScript instead of templates, you can easily pass rich data through your app and keep the state out of the DOM.
+* **Learn Once, Write Anywhere:** We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using [Node](https://nodejs.org/en) and power mobile apps using [React Native](https://reactnative.dev/).
+
+[Learn how to use React in your project](https://react.dev/learn).
+
+## Installation
+
+React has been designed for gradual adoption from the start, and **you can use as little or as much React as you need**:
+
+* Use [Quick Start](https://react.dev/learn) to get a taste of React.
+* [Add React to an Existing Project](https://react.dev/learn/add-react-to-an-existing-project) to use as little or as much React as you need.
+* [Create a New React App](https://react.dev/learn/start-a-new-react-project) if you're looking for a powerful JavaScript toolchain.
+
+## Documentation
+
+You can find the React documentation [on the website](https://react.dev/).
+
+Check out the [Getting Started](https://react.dev/learn) page for a quick overview.
+
+The documentation is divided into several sections:
+
+* [Quick Start](https://react.dev/learn)
+* [Tutorial](https://react.dev/learn/tutorial-tic-tac-toe)
+* [Thinking in React](https://react.dev/learn/thinking-in-react)
+* [Installation](https://react.dev/learn/installation)
+* [Describing the UI](https://react.dev/learn/describing-the-ui)
+* [Adding Interactivity](https://react.dev/learn/adding-interactivity)
+* [Managing State](https://react.dev/learn/managing-state)
+* [Advanced Guides](https://react.dev/learn/escape-hatches)
+* [API Reference](https://react.dev/reference)
+
+## Examples
+
+We have several examples [on the website](https://react.dev/). Here is the first one to get you started:
+
+```jsx
+import { createRoot } from 'react-dom/client';
+
+function HelloMessage({ name }) {
+  return <div>Hello {name}</div>;
+}
+
+const root = createRoot(document.getElementById('container'));
+root.render(<HelloMessage name="Taylor" />);
+```
+
+This example will render "Hello Taylor" into a container on the page.
+
+You'll notice that we used an HTML-like syntax; [we call it JSX](https://react.dev/learn#writing-markup-with-jsx). JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML.
+
+## Contributing
+
+The main purpose of this repository is to continue evolving React core, making it faster and easier to use. Development of React happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving React.
+
+### Code of Conduct
+
+Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](https://code.fb.com/codeofconduct) so that you can understand what actions will and will not be tolerated.
+
+### Contributing Guide
+
+Read our [contributing guide](https://reactjs.org/docs/how-to-contribute.html) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.
+
+### Good First Issues
+
+To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/facebook/react/labels/good%20first%20issue) that contain bugs that have a relatively limited scope. This is a great place to get started.
+
+## License
+
+React is [MIT licensed](./LICENSE).

package/tests/fixtures/github-readmes/typescript.md

@@ -0,0 +1,93 @@
+# TypeScript
+
+[![CI](https://github.com/microsoft/TypeScript/actions/workflows/ci.yml/badge.svg)](https://github.com/microsoft/TypeScript/actions/workflows/ci.yml)
+[![npm version](https://badge.fury.io/js/typescript.svg)](https://www.npmjs.com/package/typescript)
+[![Downloads](https://img.shields.io/npm/dm/typescript.svg)](https://www.npmjs.com/package/typescript)
+
+[TypeScript](https://www.typescriptlang.org/) is a language for application-scale JavaScript. TypeScript adds optional types to JavaScript that support tools for large-scale JavaScript applications for any browser, for any host, on any OS. TypeScript compiles to readable, standards-based JavaScript.
+
+## Installing
+
+For the latest stable version:
+
+```bash
+npm install -D typescript
+```
+
+For nightly builds:
+
+```bash
+npm install -D typescript@next
+```
+
+## Contribute
+
+There are many ways to [contribute](https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md) to TypeScript.
+
+* [Submit bugs](https://github.com/microsoft/TypeScript/issues) and help us verify fixes as they are checked in.
+* Review the [source code changes](https://github.com/microsoft/TypeScript/pulls).
+* Engage with other TypeScript users and developers on [StackOverflow](https://stackoverflow.com/questions/tagged/typescript).
+* Help each other in the [TypeScript Community Discord](https://discord.gg/typescript).
+* Join the [#typescript](https://twitter.com/search?q=%23TypeScript) discussion on Twitter.
+* [Contribute bug fixes](https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md).
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+
+## Documentation
+
+* [Quick Start](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html)
+* [Handbook](https://www.typescriptlang.org/docs/handbook/intro.html)
+* [TypeScript Website](https://www.typescriptlang.org/)
+
+## Building
+
+To build the TypeScript compiler, clone a copy of the repo:
+
+```bash
+git clone https://github.com/microsoft/TypeScript.git
+```
+
+Change to the TypeScript directory:
+
+```bash
+cd TypeScript
+```
+
+Install Jake tools and dev dependencies:
+
+```bash
+npm install -g jake
+npm ci
+```
+
+Use one of the following to build and test:
+
+```bash
+jake local            # Build the compiler into built/local.
+jake clean            # Delete the built compiler.
+jake LKG              # Replace the last known good with the built one.
+jake tests            # Build the test infrastructure using the built compiler.
+jake runtests         # Run tests using the built compiler and test infrastructure.
+jake baseline-accept  # This replaces the baseline test results with the results obtained from jake runtests.
+jake lint             # Runs tslint on the TypeScript source.
+jake help             # List the above commands.
+```
+
+## TypeScript Compiler Options
+
+The TypeScript compiler accepts a number of command-line options. Common options include:
+
+| Option | Description |
+|--------|-------------|
+| `--target` | Specify ECMAScript target version |
+| `--module` | Specify module code generation |
+| `--strict` | Enable all strict type-checking options |
+| `--outDir` | Redirect output structure to the directory |
+| `--declaration` | Generate corresponding `.d.ts` file |
+| `--sourceMap` | Generate corresponding `.map` file |
+
+For a full list, see the [compiler options documentation](https://www.typescriptlang.org/docs/handbook/compiler-options.html).
+
+## Roadmap
+
+For details on our planned features and future direction please refer to our [roadmap](https://github.com/microsoft/TypeScript/wiki/Roadmap).

package/tests/fixtures/github-readmes/vite.md

@@ -0,0 +1,79 @@
+# Vite ⚡
+
+> Next Generation Frontend Tooling
+
+- 💡 Instant Server Start
+- ⚡️ Lightning Fast HMR
+- 🛠️ Rich Features
+- 📦 Optimized Build
+- 🔩 Universal Plugin Interface
+- 🔑 Fully Typed APIs
+
+Vite (French word for "quick", pronounced `/vit/`, like "veet") is a new breed of frontend build tool that significantly improves the frontend development experience.
+
+## Overview
+
+Vite consists of two major parts:
+
+- A dev server that provides [rich feature enhancements](https://vite.dev/guide/features.html) over [native ES modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules), for example extremely fast [Hot Module Replacement (HMR)](https://vite.dev/guide/features.html#hot-module-replacement).
+
+- A build command that bundles your code with [Rollup](https://rollupjs.org), pre-configured to output highly optimized static assets for production.
+
+Vite is opinionated and comes with sensible defaults out of the box. Read about what's possible in the [Features Guide](https://vite.dev/guide/features.html). Support for frameworks or integration with other tools is possible through [Plugins](https://vite.dev/guide/using-plugins.html). The [Config Section](https://vite.dev/config/) explains how to adapt Vite to your project if needed.
+
+## Getting Started
+
+Try Vite online on [StackBlitz](https://vite.new/). Select a template and start coding in seconds.
+
+Create a new Vite project with one of the supported templates:
+
+```bash
+# npm 7+
+npm create vite@latest my-app -- --template react
+
+# yarn
+yarn create vite my-app --template react
+
+# pnpm
+pnpm create vite my-app --template react
+```
+
+Supported templates: `vanilla`, `vanilla-ts`, `vue`, `vue-ts`, `react`, `react-ts`, `react-swc`, `react-swc-ts`, `preact`, `preact-ts`, `lit`, `lit-ts`, `svelte`, `svelte-ts`, `solid`, `solid-ts`, `qwik`, `qwik-ts`
+
+## Documentation
+
+- [Guide](https://vite.dev/guide/)
+- [Config Reference](https://vite.dev/config/)
+- [Plugin API](https://vite.dev/guide/api-plugin.html)
+
+## Browser Support
+
+The default build targets browsers that support [native ESM via script tag](https://caniuse.com/es6-module), [native ESM dynamic import](https://caniuse.com/es6-module-dynamic-import), and [`import.meta`](https://caniuse.com/mdn-javascript_operators_import_meta). Legacy browsers can be supported via the official [@vitejs/plugin-legacy](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy).
+
+## Migrating from Other Tools
+
+### From Webpack
+
+If you're migrating from webpack, check out the [Vite migration guide](https://vite.dev/guide/migration.html) for tips on how to migrate your project.
+
+### From Create React App
+
+Vite can be used as a drop-in replacement for Create React App. Update your `package.json` scripts and install Vite dependencies:
+
+```json
+{
+  "scripts": {
+    "dev": "vite",
+    "build": "vite build",
+    "preview": "vite preview"
+  }
+}
+```
+
+## Contributing
+
+See [Contributing Guide](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
+
+## License
+
+[MIT](https://github.com/vitejs/vite/blob/main/LICENSE)

package/tests/fixtures/queries/core.json

@@ -0,0 +1,125 @@
+{
+  "version": "3.0.0",
+  "description": "Agentic coding task queries - representative of how Claude Code would query knowledge bases",
+  "queries": [
+    {
+      "id": "vue-001",
+      "query": "I have a counter variable that needs to update the UI when it changes. How do I make it reactive in Vue 3?",
+      "intent": "Implement reactive state in Vue",
+      "taskContext": "Building a click counter component",
+      "category": "implementation"
+    },
+    {
+      "id": "vue-002",
+      "query": "I need to show a filtered count based on an array of items. What's the Vue way to derive a value that updates automatically?",
+      "intent": "Use computed properties for derived state",
+      "taskContext": "Building a todo list with filter counts",
+      "category": "pattern"
+    },
+    {
+      "id": "vue-003",
+      "query": "How do I make sure a Vue component only accepts valid data? I want to validate that a 'user' prop has name and email fields.",
+      "intent": "Validate component props in Vue",
+      "taskContext": "Creating a reusable UserCard component",
+      "category": "implementation"
+    },
+    {
+      "id": "express-001",
+      "query": "My Express app crashes when a route throws an error. How do I set up error handling middleware that catches all errors?",
+      "intent": "Implement centralized error handling in Express",
+      "taskContext": "Adding production error handling to an API",
+      "category": "implementation"
+    },
+    {
+      "id": "express-002",
+      "query": "How do I get the userId from a URL like /users/123 in my Express route handler?",
+      "intent": "Extract route parameters in Express",
+      "taskContext": "Building a user profile endpoint",
+      "category": "implementation"
+    },
+    {
+      "id": "express-003",
+      "query": "My Express app is getting big. How do I split routes into separate files and import them into the main app?",
+      "intent": "Organize routes with express.Router()",
+      "taskContext": "Refactoring a growing Express application",
+      "category": "pattern"
+    },
+    {
+      "id": "express-004",
+      "query": "My async database call throws an error in an Express route but the error middleware never catches it. What am I doing wrong?",
+      "intent": "Handle async errors in Express routes",
+      "taskContext": "Debugging unhandled promise rejections",
+      "category": "debugging"
+    },
+    {
+      "id": "jwt-001",
+      "query": "I have a JWT token from the client. How do I verify it's valid and extract the user data from it?",
+      "intent": "Verify and decode JWT tokens",
+      "taskContext": "Implementing authentication middleware",
+      "category": "implementation"
+    },
+    {
+      "id": "jwt-002",
+      "query": "What's the difference between decoding a JWT and verifying it? When should I use each?",
+      "intent": "Understand JWT decode vs verify",
+      "taskContext": "Deciding on auth implementation approach",
+      "category": "understanding"
+    },
+    {
+      "id": "ts-001",
+      "query": "I want my generic function to only accept objects that have an 'id' property. How do I constrain the type parameter?",
+      "intent": "Use generic constraints in TypeScript",
+      "taskContext": "Building a generic entity repository",
+      "category": "implementation"
+    },
+    {
+      "id": "ts-002",
+      "query": "I need to make all properties of a type optional. Is there a built-in way to do this in TypeScript?",
+      "intent": "Use mapped types like Partial<T>",
+      "taskContext": "Creating a patch/update function type",
+      "category": "implementation"
+    },
+    {
+      "id": "react-001",
+      "query": "My useEffect sets up a WebSocket connection. How do I properly clean it up when the component unmounts?",
+      "intent": "Use cleanup functions in useEffect",
+      "taskContext": "Preventing memory leaks with WebSocket",
+      "category": "implementation"
+    },
+    {
+      "id": "react-002",
+      "query": "My useEffect runs on every render even though I only want it to run when 'userId' changes. What's wrong?",
+      "intent": "Understand dependency arrays in React hooks",
+      "taskContext": "Debugging excessive API calls",
+      "category": "debugging"
+    },
+    {
+      "id": "hono-001",
+      "query": "I need a route that matches /api/files/* where * can be any path including slashes. How do I set up a wildcard route in Hono?",
+      "intent": "Use wildcard routes in Hono",
+      "taskContext": "Building a file server endpoint",
+      "category": "implementation"
+    },
+    {
+      "id": "hono-002",
+      "query": "I'm building a high-traffic API and considering Hono vs Express. What are the performance differences?",
+      "intent": "Compare Hono and Express performance",
+      "taskContext": "Choosing a framework for a new project",
+      "category": "decision"
+    },
+    {
+      "id": "node-001",
+      "query": "I'm piping streams together with pipeline(). How do I properly handle errors if one of the streams fails?",
+      "intent": "Handle errors in Node.js stream pipelines",
+      "taskContext": "Building a file processing pipeline",
+      "category": "implementation"
+    },
+    {
+      "id": "node-002",
+      "query": "My producer is generating data faster than my consumer can process it. How does Node.js handle this backpressure situation?",
+      "intent": "Understand backpressure in Node.js streams",
+      "taskContext": "Debugging slow stream processing",
+      "category": "understanding"
+    }
+  ]
+}