sovara 0.2.7__tar.gz → 0.2.9__tar.gz

{sovara-0.2.7 → sovara-0.2.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sovara
-Version: 0.2.7
+Version: 0.2.9
 Summary: A development tool for LLM call visualization and debugging
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
@@ -23,6 +23,7 @@ Requires-Dist: google-cloud-aiplatform
 Requires-Dist: flatten_dict
 Requires-Dist: flatten_json
 Requires-Dist: pymongo
+Requires-Dist: sqlite-vec==0.1.9
 Provides-Extra: dev
 Requires-Dist: black==25.1.0; extra == "dev"
 Requires-Dist: pytest; extra == "dev"

{sovara-0.2.7 → sovara-0.2.9}/pyproject.toml

@@ -26,7 +26,7 @@ line-length = 100
 
 [project]
 name = "sovara"
-version = "0.2.7"
+version = "0.2.9"
 description = "A development tool for LLM call visualization and debugging"
 readme = "docs/release/PYPI_DESC.md"
 requires-python = ">=3.10"
@@ -49,7 +49,8 @@ dependencies = [
     "google-cloud-aiplatform",
     "flatten_dict",
     "flatten_json",
-    "pymongo"
+    "pymongo",
+    "sqlite-vec==0.1.9",
 ]
 
 [project.optional-dependencies]

sovara-0.2.9/src/sovara/__init__.py

@@ -0,0 +1,3 @@
+from sovara.runner.context_manager import disable_prior_injection, log, sovara_launch as launch
+
+__all__ = ["launch", "log", "disable_prior_injection"]

{sovara-0.2.7 → sovara-0.2.9}/src/sovara/assets/SKILL.md

@@ -430,26 +430,13 @@ The ideal prior has three properties:
   2. generalizes well to other scenarios where the same problem could occur in a slightly different way
   3. and it does not conflict with other existing priors.
 
+Good priors are actionable, concise, self-contained, specific, generalizable, faithful to the lesson, retrieval-friendly, and non-conflicting. If a prior captures the right lesson but is verbose, vague, overly run-specific, or hard to scan, polish it before saving or updating it. In the UI, use the **Polish** action in the content editor. From the CLI, use `so-cli priors polish <prior_id>` to get a non-mutating polished content proposal.
+
 Once you have constructed a prior, check if the problem is solved by doing A/B testing. You should inject the prior at any point you see fit, and use the `edit-and-rerun` functionality. If you want to try different versions of the prior, run `edit-and-rerun` in parallel.
 Once you verified that the prior addresses the problem, retrieve the available priors, and check if you introduced a conflict with another prior. If so, resolve the conflict by iteratively tuning and running the agent with the adapted priors, until you are satisfied.
 If the prior came from debugging or improving a specific Sovara run, attach that provenance when you save it: pass `--run-id <full_run_uuid>` to `so-cli priors create` or `so-cli priors update`. Use the full UUID from `so-cli record` or `so-cli runs`; unlike `probe` and `logs`, this field should not use a short prefix.
 When you learned the prior from a concrete run and omit `--run-id`, treat that as a mistake and fix it before you move on. The only normal case for a missing `run_id` is when the prior came from broad repository inspection or synthesis across multiple runs rather than one specific trace.
 
-When a prior constrains correctness, also attach prior-adherence metadata:
-
-- `--consequence-if-not-followed`: the concrete failure mode expected when the prior is relevant but the model violates it.
-- `--non-adherence-severity`: an integer from 1 to 10 used as the fixed penalty when the adherence judge finds the prior relevant and not followed.
-
-Use this severity scale:
-
-- `1-2`: cosmetic or negligible; unlikely to affect outcome
-- `3-4`: minor quality, consistency, or preference issue
-- `5-6`: material correctness or interpretation risk
-- `7-8`: serious issue likely to cause wrong output, wrong action, output-contract violation, or major degradation
-- `9-10`: direct correctness break, safety-critical violation, hard contract violation, or likely primary reason the step failed
-
-The adherence judge decides whether the prior was relevant and followed, but it does not reinterpret the severity. If the prior is violated, the stored `non_adherence_severity` is used as-is.
-
 ### How to use
 
 First, inject priors into the context by modifying the user code.
@@ -486,7 +473,7 @@ priors_context = inject_priors(
 `so-cli priors` mirrors the public priors API exposed by the main `so-server`.
 
 ```
-usage: so-cli priors [-h] {start-server,list,get,create,update,delete,query,retrieve,migrate,restructure,ls,mkdir,mv,cp,rm} ...
+usage: so-cli priors [-h] {start-server,list,get,create,update,polish,delete,query,retrieve,migrate,restructure,ls,mkdir,mv,cp,rm} ...
 ```
 
 When you need to target a project explicitly, list projects first:
@@ -501,7 +488,7 @@ Then pass `--project-id` or `--proj-id` with a full project ID or any unambiguou
 uv run so-cli runs --project-id a6cbns64
 uv run so-cli priors ls --proj-id a6cbns64
 uv run so-cli priors ls path/to/subfolder/ --proj-id a6cbns64
-uv run so-cli priors create --title "<title>" --content "<content>" --summary "<summary>" --path "path/to/subfolder/" --consequence-if-not-followed "<failure mode>" --non-adherence-severity <severity_1_to_10> --project-id a6cbns64
+uv run so-cli priors create --title "<title>" --content "<content>" --summary "<summary>" --path "path/to/subfolder/" --project-id a6cbns64
 ```
 
 For root scope, omit the path entirely. Examples: `uv run so-cli priors ls --project-id a6cbns64`, `uv run so-cli priors list --project-id a6cbns64`, or `uv run so-cli priors retrieve "<context>" --project-id a6cbns64`.
@@ -510,8 +497,9 @@ The main commands are:
 
 - `list`: list priors, optionally filtered by `--path`
 - `get <prior_id>`: fetch one prior
-- `create`: create a prior with `--title`, `--content`, and optional `--summary`, `--path`, `--run-id`, `--when-to-use`, `--consequence-if-not-followed`, `--non-adherence-severity`, `--alias`, `--keyword`, and `--related-prior`. If you omit `--summary`, the server generates one with a cheap model and a fallback. Pass `--run-id <full_run_uuid>` whenever the prior came from a specific run; if you just verified a fix with `so-cli record`, this should usually be present.
-- `update <prior_id>`: update `--title`, `--content`, `--path`, `--run-id`, `--when-to-use`, `--consequence-if-not-followed`, `--non-adherence-severity`, `--alias`, `--keyword`, and/or `--related-prior`. Preserve or add `--run-id <full_run_uuid>` when the prior is tied to a run; do not drop provenance during follow-up edits.
+- `create`: create a prior with `--title`, `--content`, and optional `--summary`, `--path`, `--run-id`, `--when-to-use`, `--alias`, and `--keyword`. If you omit `--summary`, the server generates one with a cheap model and a fallback. Pass `--run-id <full_run_uuid>` whenever the prior came from a specific run; if you just verified a fix with `so-cli record`, this should usually be present.
+- `update <prior_id>`: update `--title`, `--content`, `--path`, `--run-id`, `--when-to-use`, `--alias`, and/or `--keyword`. Preserve or add `--run-id <full_run_uuid>` when the prior is tied to a run; do not drop provenance during follow-up edits.
+- `polish <prior_id>`: return a non-mutating polished content proposal for a prior
 - `delete <prior_id>`: delete one prior
 - `query`: return all priors in a path plus an injected `<sovara-priors>` block
 - `retrieve "<context>"`: use the LLM retriever to select relevant priors
@@ -524,8 +512,9 @@ Examples:
 ```bash
 so-cli priors list --path "path/to/subfolder/"
 so-cli priors get <prior_id>
-so-cli priors create --title "<title>" --content "<content>" --summary "<summary>" --path "path/to/subfolder/" --run-id "<full_run_uuid>" --consequence-if-not-followed "<failure mode>" --non-adherence-severity <severity_1_to_10> --alias "<alias>" --keyword "<keyword>" --related-prior "<prior_id>"
-so-cli priors update <prior_id> --content "<new_content>" --path "path/to/another-subfolder/" --consequence-if-not-followed "<failure mode>" --non-adherence-severity <severity_1_to_10> --alias "<alias>" --keyword "<keyword>"
+so-cli priors create --title "<title>" --content "<content>" --summary "<summary>" --path "path/to/subfolder/" --run-id "<full_run_uuid>" --alias "<alias>" --keyword "<keyword>"
+so-cli priors polish <prior_id>
+so-cli priors update <prior_id> --content "<new_content>" --path "path/to/another-subfolder/" --alias "<alias>" --keyword "<keyword>"
 so-cli priors delete <prior_id>
 so-cli priors query --path "path/to/subfolder/"
 so-cli priors retrieve "Find validation guidance"
@@ -541,7 +530,7 @@ so-cli priors rm -r path/to/old-folder/
 
 Restructure workflow:
 
-1. Run `so-cli priors restructure propose` to get a proposal with `task_id`, `moves`, `new_folders`, and `snapshot`.
+1. Run `so-cli priors restructure propose` to get a proposal with `task_id`, `moves`, `new_folders`, and `prior_tree_hash`.
 2. Optionally inspect or edit the JSON proposal file.
 3. Run `so-cli priors restructure execute --proposal-file proposal.json` to execute it.
 4. If you do not want to apply it, run `so-cli priors restructure abort <task_id>` to release the lock.
@@ -554,18 +543,15 @@ Representative outputs:
 {
   "priors": [
     {
-      "id": "24d90294",
+      "prior_id": "24d90294",
       "title": "Rate Limiting Best Practices",
       "summary": "Use exponential backoff with jitter when upstream APIs rate-limit requests.",
       "content": "When dealing with rate limits, implement exponential backoff...",
       "path": "path/to/subfolder/",
       "prior_status": "active",
       "run_id": "<run_uuid_or_null>",
-      "consequence_if_not_followed": "Violating this prior can cause retries to duplicate side-effecting calls.",
-      "non_adherence_severity": "<integer_1_to_10>",
       "aliases": ["rate limit retries", "429 retry policy"],
-      "keywords": ["rate-limit", "backoff", "jitter", "429"],
-      "related_priors": []
+      "keywords": ["rate-limit", "backoff", "jitter", "429"]
     }
   ]
 }
@@ -578,9 +564,7 @@ Active priors now store:
 - `content`: mandatory raw markdown without a title heading
 - `status`: active or draft
 - `run_id`: optional source trace/run UUID; pass it whenever the prior was derived from a specific run
-- `consequence_if_not_followed`: optional expected failure mode when a relevant prior is violated
-- `non_adherence_severity`: optional integer `1-10` fixed severity penalty for a violated relevant prior
-- `aliases`, `keywords`, `related_priors`: optional string lists
+- `aliases`, `keywords`: optional string lists
 - `created_at`, `updated_at`: UTC timestamps
 - `validation_metadata`: latest validation payload
 
@@ -589,17 +573,14 @@ Active priors now store:
 ```json
 {
   "status": "created",
-  "id": "<prior_id>",
+  "prior_id": "<prior_id>",
   "title": "<title>",
   "summary": "<manual_or_generated_summary>",
   "content": "<content>",
   "path": "path/to/subfolder/",
   "run_id": "<run_uuid_or_null>",
-  "consequence_if_not_followed": "<failure_mode_or_empty_string>",
-  "non_adherence_severity": "<integer_1_to_10>",
   "aliases": ["<manual_or_generated_alias>"],
-  "keywords": ["<manual_or_generated_keyword>"],
-  "related_priors": ["<prior_id>"]
+  "keywords": ["<manual_or_generated_keyword>"]
 }
 ```
 
@@ -610,14 +591,14 @@ Active priors now store:
   "path": "path/to/subfolder/",
   "priors": [
     {
-      "id": "<prior_id>",
+      "prior_id": "<prior_id>",
       "name": "<name>",
       "summary": "<summary>",
       "content": "<content>",
       "path": "path/to/subfolder/"
     }
   ],
-  "injected_context": "<sovara-priors>\n<!-- {\"priors\":[{\"id\":\"<prior_id>\"}]} -->\n## <name>\n<content>\n</sovara-priors>"
+  "injected_context": "<sovara-priors>\n<!-- {\"priors\":[{\"prior_id\":\"<prior_id>\"}]} -->\n## <name>\n<content>\n</sovara-priors>"
 }
 ```
 
@@ -629,7 +610,7 @@ Active priors now store:
   "base_path": "path/to/root/",
   "priors": [
     {
-      "id": "<prior_id>",
+      "prior_id": "<prior_id>",
       "name": "<name>",
       "summary": "<summary>",
       "content": "<content>",
@@ -658,7 +639,7 @@ Active priors now store:
   ],
   "redundant_prior_ids": [],
   "total_priors": 4,
-  "snapshot": "<snapshot>"
+  "prior_tree_hash": "<prior_tree_hash>"
 }
 ```
 
@@ -675,7 +656,7 @@ Active priors now store:
   ],
   "priors": [
     {
-      "id": "abc123",
+      "prior_id": "abc123",
       "name": "Some Prior",
       "summary": "...",
       "content": "...",

sovara-0.2.9/src/sovara/assets/web_app/assets/AttachmentPreview-C-SDQn_c.js

@@ -0,0 +1 @@
+import{r,j as e}from"./index-TU6o79pU.js";import{D as n,a as l,P as o,G as p}from"./DocumentPreviewModal-DLcTPg47.js";import{M as c,i as d,a as h,h as u,s as x,d as j}from"./RunRoute-CjnawiLF.js";import"./tiny-invariant-BCXflckp.js";import"./LayoutBreadcrumb-DrZRF2Sb.js";import"./tierState-BVmlAt4E.js";import"./api-VlLy9MpQ.js";import"./runtime-B1TGbSkq.js";import"./plus-B1NOTICQ.js";import"./value-Bqe5DuYT.js";import"./prismTheme-nMW1SONA.js";import"./useTheme-BMbBHOjM.js";p.workerSrc=new URL("/assets/pdf.worker.min-qwK7q_zL.mjs",import.meta.url).toString();function b({attachment:m,onClick:i}){const s=`data:${m.mimeType};base64,${m.data}`,t=c[m.mimeType]??m.mimeType.split("/")[1]?.toUpperCase()??"FILE";return e.jsxs("button",{className:"attachment-thumb",onClick:i,title:m.name,children:[e.jsx("div",{className:"attachment-thumb-preview",children:d(m.mimeType)?e.jsx("img",{src:s,alt:m.name,className:"attachment-thumb-img"}):h(m.mimeType)?e.jsx(l,{file:s,loading:e.jsx("div",{className:"attachment-thumb-placeholder",children:"PDF"}),children:e.jsx(o,{pageNumber:1,width:120,renderTextLayer:!1,renderAnnotationLayer:!1})}):e.jsx("div",{className:"attachment-thumb-placeholder",children:t})}),e.jsxs("div",{className:"attachment-thumb-label",children:[e.jsx("span",{className:"attachment-thumb-ext",children:t}),e.jsx("span",{className:"attachment-thumb-name",children:m.name})]})]})}function E({attachments:m}){const[i,s]=r.useState(null);if(m.length===0)return null;function t(a){u(a.mimeType)?s(a):x(j(a.data,{mime_type:a.mimeType,filename:a.name})||{data:a.data,mimeType:a.mimeType,type:"unknown",name:a.name})}return e.jsxs(e.Fragment,{children:[e.jsx("div",{className:"attachment-strip",children:m.map(a=>e.jsx(b,{attachment:a,onClick:()=>t(a)},a.id))}),i&&e.jsx(n,{attachment:i,onClose:()=>s(null)})]})}export{E as AttachmentStrip};