@plurnk/plurnk-service 1.2.0 → 1.3.1

package/.env.defaults

@@ -223,6 +223,9 @@ PLURNK_SERVICE_SEMANTIC_CHUNK_TOKENS=
 # Overlap fraction [0,1): trailing context re-covered at each chunk boundary so a
 # concept split across a cut still matches in both. ~0.15 is a standard RAG default.
 PLURNK_SERVICE_SEMANTIC_CHUNK_OVERLAP=0.15
+# Optional maximum UTF-8 body size eligible for vectors. Oversized entries remain
+# readable, graph-derived, and FTS-indexed. 0 = unlimited (the shipped default).
+PLURNK_SERVICE_MAX_EMBED_SIZE=0
 # =1 forces the FTS-only path even with the embeddings package installed — the ~query
 # degrades to keyword ranking and no vectors are derived (no MiniLM pool spun up). For
 # hosts/runs that don't want vector search; the fast test lane sets it in .env.test.
@@ -238,8 +241,7 @@ PLURNK_SERVICE_SEARCH_MAX_PER_TURN=3
 # steer instead of enumerating every match (§find-count-not-contents) — a repo-scale FIND(**) over
 # a 19k-entry workspace grinds clean instead of overflowing the window. 0/unset = no gate.
 PLURNK_SERVICE_FIND_MAX_MATCHES=500
-# Derivation-pump concurrency: how many entries' embeds run at once. The embedder's worker pool is
-# data-parallel but starves on sequential per-entry calls (#416) — overlapping K embeds saturates
-# it (a large-workspace ingest goes from a single-core minutes-long grind to a fast multi-core
-# pass). 1 = sequential (default, safe). Set to ~cores for repo-scale ingest.
-PLURNK_SERVICE_DERIVE_CONCURRENCY=1
+# Derivation producer concurrency: how many entries may materialize graphs/chunk plans at once.
+# Unset uses a host-relative square-root fan-out; the separate embedding pool uses the available
+# cores. A positive integer is an exact operator budget; -1 explicitly claims every available core.
+PLURNK_SERVICE_DERIVE_CONCURRENCY=

package/README.md

@@ -1,6 +1,9 @@
 # plurnk-service
 
-LLM agent runtime engine. Consumes [plurnk-grammar](https://github.com/plurnk/plurnk-grammar); exposes WebSocket JSON-RPC. User-facing CLI: [plurnk](https://github.com/plurnk/plurnk). Provider-agnostic, MIT — no vendor or model lock-in.
+The PLURNK daemon: persistent agent state, model loops, packet assembly, and
+operation dispatch. Its client surface is AG-UI over HTTP/SSE through
+`@plurnk/plurnk-agui`. The user-facing CLI lives in
+[plurnk](https://github.com/plurnk/plurnk).
 
 ## What an agent can do
 
@@ -12,16 +15,11 @@ Over schemes: `file://` project files · `exec://` command output · `http(s)://
 
 Workspace = the shared world (one filesystem + membership overlay). Run = one agent's private log. Loop = one `prompt → ops → SEND[terminal]` cycle; every turn leads with `PLAN`. Runs fork and message each other — many clients, many runs, one workspace.
 
-## Integration (WebSocket JSON-RPC)
+## Integration
 
-Methods: `workspace.*` (create / attach / constrain / list…) · `loop.run` / `loop.inject` / `loop.resolve` · `op.*` (read / edit / find / exec / send…) · `log.read` · `run.fork`. Streams: `log/entry` → … → `loop/terminated`, plus `loop/proposal`, `telemetry/event`. Full live catalog: the `discover` RPC.
-
-```
-ws connect → workspace.create({ projectRoot }) → loop.run({ prompt })
-           → read log/entry notifications until loop/terminated
-```
-
-The human CLI over this surface is [plurnk](https://github.com/plurnk/plurnk).
+Clients use AG-UI management actions and run streams exposed by
+`@plurnk/plurnk-agui`. Core supplies an in-process daemon seam; it does not open
+a second client transport.
 
 ## Run
 
@@ -34,8 +32,11 @@ Config + state live in `~/.plurnk/` (created on first run): put your config in `
 
 ## Contract & siblings
 
-- [`SPEC.md`](./SPEC.md) — canonical specification. One `§<tag>` namespace; anchors `{§<tag>}` bind 1:1 to `test/intg/spec-anchors.test.ts`.
-- [plurnk-providers](https://github.com/plurnk/plurnk-providers) §provider · [plurnk-schemes](https://github.com/plurnk/plurnk-schemes) §scheme-surface · [plurnk-mimetypes](https://github.com/plurnk/plurnk-mimetypes) §mimetype-surface · [plurnk-execs](https://github.com/plurnk/plurnk-execs) §bundled-set.
+- [`SPEC.md`](./SPEC.md) — detailed behavioral reference.
+- `@plurnk/plurnk-providers` — model endpoint contract.
+- `@plurnk/plurnk-schemes` — addressable resource contract.
+- `@plurnk/plurnk-mimetypes` — content handling contract.
+- `@plurnk/plurnk-execs` — executable capability contract.
 
 ## Semantic search
 
@@ -47,4 +48,6 @@ Plurnk sees what git sees. The model's file surface is defined by three external
 
 ## Tests
 
-`test:lint`, `test:unit`, `test:intg`, `test:live`, `test:demo`; off-hot-path `test:installation`.
+Run the root monorepo commands for deterministic lint, unit, and integration
+coverage. Live-model, demo, and installation tests declare their external
+requirements separately.