lurqrun 0.0.5 → 0.0.7

package/README.md

@@ -1,16 +1,21 @@
 # lurq
 
-> dynamic index of sdk's, frameworks, and libraries exposed as an mcp server. cli-based installable agent skill, compatible with agentic code assistants and ides, including vscode, cursor, windsurf, claude code, and codex. lurq focuses specifically on objective package recommendations from open-source dependencies. 
+> execution-verified answers for AI coding agents. a live index of npm scored from public signals, plus a sandbox that settles the questions metadata can't — exposed as an mcp server, a cli, an http api, and an installable agent skill, compatible with claude code, cursor, windsurf, vscode/copilot, codex, gemini cli, antigravity, and kiro.
 
-lurq is a **companion to your coding agent**: it recommends and explains packages, and your agent writes the code. prioritized for token cost, speed, and retrieval quality, and diagrams a stack you've chosen when prompted. notice: lurq contains a growing, comprehensive database of packages, allowing newer dependencies to be exposed to the agent outside of the training data of the underlying model. 
+your agent picks the dependencies now, and it picks them from training data frozen at its cutoff and ranked by how often a name appeared in text — not by whether the package is healthy today. so agents install libraries that are abandoned, carry open advisories, or don't exist at all.
 
-**v1 scope:** the javaScript/typeScript web stack (npm) only.
+lurq is what the agent checks first. most of what matters is readable — release cadence, advisories, deprecations, types/tests/docs, bundle cost — and lurq ingests all of it daily. the rest isn't readable at all. whether a package installs cleanly, whether it imports without throwing, whether two versions can coexist in one tree: those are only knowable by running them, so lurq runs them in an isolated sandbox and keeps the result.
+
+lurq recommends and explains packages; your agent writes the code. responses are compact and token-budgeted, built for an agent's context window rather than a human's screen.
+
+**v1 scope:** the javascript/typescript web stack (npm) only.
 
 ---
 
 ## quick start: connect your agent
 
-> **not public yet.** lurq unlocks at launch. [join the waitlist](https://lurq.run); the steps below are how it'll work once it's live.
+> **lurq is live.** [create a free account](https://lurq.run/sign-up) to generate
+> your API key, then connect your coding agent with the guided installer below.
 
 lurq is a **hosted service**: you don't run a database or a sync. get an API key,
 then run the guided installer:
@@ -20,26 +25,79 @@ npx lurqrun install
 ```
 
 it prompts for your key, validates it, detects your installed assistants
-(Claude Code, Cursor, Windsurf, VS Code/Copilot, Codex), and writes a keyed
-remote MCP entry:
+(claude code, cursor, windsurf, vscode/copilot, codex, gemini cli, antigravity,
+kiro), and writes a keyed
+remote mcp entry:
 `{ "type": "http", "url": "https://api.lurq.run/mcp", "headers": { "Authorization": "Bearer …" } }`.
 **no database credentials ever touch your machine.** restart your agent afterward.
 
 ## what your agent gets (mcp tools)
 
-once installed, the agent can call these tools over MCP. every response is
-compact and carries a `dataAsOf` timestamp.
+once installed, the agent can call these over mcp. every response is compact and
+carries a `dataAsOf` timestamp.
 
 - **`recommend`**: best current packages for a described need (≤5, scored, with confidence)
 - **`evaluate`**: full evidence read for one package (scores, advisories, usage guide)
-- **`compare`**: 2 to 5 packages ranked by health
+- **`compare`**: 2 to 5 packages ranked head-to-head
 - **`verify`**: is a package real, healthy, and not risky? (anti-hallucination guard)
-- **`diagram`**: a reference-architecture mermaid diagram for a stack (optional)
+- **`compat`**: will these packages actually install together? (peer/engine constraints)
+- **`plan`**: source every slot in a stack at once, checked for cross-slot coherence
+- **`diagram`**: a reference-architecture mermaid diagram for a stack
+- **`usage`**: a package version's *real* public api — exported symbols and signatures extracted from its shipped `.d.ts`, exact to the version and absent from any model's training data. pass the version your model knows and get the precise delta: what was added, removed, renamed, or changed.
+- **`report_outcome`**: what happened after a pick shipped — installed clean, broke the build, resolved the task. the signal only exists for whatever sits inside the decision, so it feeds back into scoring.
+
+## cli
+
+the same index, scriptable. every capability is a subcommand:
+
+```bash
+lurq recommend "a form library for react"
+lurq verify jsonwebtoken
+lurq compare date-fns dayjs moment
+lurq compat next react react-dom          # do these install together?
+lurq usage zod --known 3.22.4             # what changed in the api since? (--target pins a version)
+lurq plan ./project.md                    # a description in, a scored stack out
+lurq serve-http                           # run it as a rate-limited service of your own
+lurq weights                              # the exact ranking weights, printed
+```
+
+## where the evidence comes from
+
+two sources, and the distinction is the whole point.
+
+**readable** — npm, github, deps.dev, and osv, re-synced daily. downloads, release
+cadence, maintenance, advisories, deprecations, license, bundle cost. this is what
+scoring runs on.
+
+**executed** — an isolated sandbox (e2b, with a local driver for trusted work) that
+installs a package version, imports it, and records what happened. co-installing a
+set is how compatibility is established: a successful co-install is positive proof
+two versions coexist, a failure is proof they conflict, and the error is kept as
+evidence. `compat` and `plan` read those edges, which is why lurq can tell you a
+*stack* holds together rather than only that each package looks fine alone.
+
+facts of the second kind appear in no changelog and no model's training data, and
+they go stale unless someone keeps re-running the experiment.
+
+## how the ranking works
+
+deterministic, and public. no model sits in the ranking path — `recommend` is hybrid
+vector + full-text search over precomputed scores, which is why it's fast, cheap, and
+reproducible.
+
+- **health** = maintenance `0.35` · adoption `0.30` · reliability `0.25` · efficiency `0.10`
+- **quality** is a separate, adoption-independent axis — types, tests, docs, changelog,
+  dependency count, license, provenance — so a well-built new package isn't buried by an
+  old popular one
+- the two blend at a single tunable λ for the default sort
+
+every weight lives in [`src/scoring/weights.ts`](src/scoring/weights.ts) and is printable with
+`lurq weights`. an answer an agent acts on is worth nothing if it can't be audited.
 
-## outreach 
+## outreach
 
-for any inquiries, partnerships, or proposals, contact jaden ryu at jadenryu@gmail.com. 
+for any inquiries, partnerships, or proposals, contact jaden ryu at jadenryu@gmail.com.
 
 ## license
 
-Apache License 2.0 
+Apache License 2.0