@functional-systems/srcx 0.1.0-dev.31 → 0.1.0-dev.32

package/README.md

@@ -453,6 +453,12 @@ The subsequent [exact-Collection lookup replay](https://github.com/lambdadb/srcx
 removes 22 requests per command in that project, with identical source results
 and lower observed read/search latency. It does not measure complete-agent cost.
 
+In the subsequent [agent choice comparison](https://github.com/lambdadb/srcx/blob/develop/eval/VERSION-AGENT-RESULTS.md),
+all three agents offered srcx read its installed skill but used local tools only
+to investigate the prepared CLI/SDK versions. No srcx retrieval benefit was
+established; multiple repositories and historical versions alone did not lead to
+tool adoption when their source trees were already available locally.
+
 The internal [lexical chunking pilot](https://github.com/lambdadb/srcx/blob/develop/eval/README.md) compares syntax-aware and
 window chunks on a fixed public corpus and 16 pinned investigation queries.
 `npm run eval:prepare` builds and validates the comparison offline. Live evaluation

package/VALIDATION.md

@@ -1,5 +1,25 @@
 # Validation record
 
+## Agent choice across repositories and versions
+
+The [six-session comparison](eval/VERSION-AGENT-RESULTS.md) offers the installed
+srcx skill alongside identical local CLI/SDK source trees for three fresh
+maintenance questions. All three srcx-condition agents read the skill but make
+zero srcx calls. Both conditions meet 14 frozen facts and partially meet one;
+no material answer errors were found under assistant source review. All 82 linked
+citation ranges were opened and checked. Tests cited by agents were not executed.
+
+Mean total input is 11.0% lower and time 8.1% lower with srcx offered, but uncached
+input is 6.1% higher. With no retrieval calls, these are session differences, not
+evidence of srcx search efficiency or cost savings. Stop tuning this prepared-local
+workflow; any team pilot needs an actual recurring source-access need.
+
+All six sessions finish within budget, all 18 source checkouts stay clean at their
+pins, and all 31 frozen inputs match. Six before/after resolution checks confirm
+unchanged commit/Tag/Snapshot identities. No imports, task searches, embeddings or
+remote writes occur. The protocol, rubric and runtime hashes were committed before
+execution; raw sessions and source evidence remain in the local evaluation archive.
+
 ## Direct Collection lookup
 
 Exact generated Collection selectors now fetch only the selected metadata and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/srcx",
-  "version": "0.1.0-dev.31",
+  "version": "0.1.0-dev.32",
   "private": false,
   "description": "Version-aware code search on LambdaDB",
   "type": "module",
@@ -66,5 +66,5 @@
     "url": "https://github.com/lambdadb/srcx/issues"
   },
   "license": "Apache-2.0",
-  "gitHead": "642169ee7abdc8fc71508418f43a52ca863dce5f"
+  "gitHead": "88abc665f4f436c045d79870eeb7cf0eac8ac814"
 }