omnius 1.0.805 → 1.0.806

package/dist/index.js

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/index.js
-size: 39577537 bytes
-sha256: 7e685cb4fe7dec48043833dea8e92cfb6ccf2d9dbe4807939838a64e294fae85
+size: 39764994 bytes
+sha256: f639831df6a48762e2ad24ab81fa24caa0275925a01d3a40b8b3742e8b9afa95

package/dist/library.js

@@ -47728,10 +47728,18 @@ var init_contextMemoryLedger = __esm({
   }
 });
 
+// packages/memory/dist/utf8PrefixIndex.js
+var init_utf8PrefixIndex = __esm({
+  "packages/memory/dist/utf8PrefixIndex.js"() {
+    "use strict";
+  }
+});
+
 // packages/memory/dist/immutableEvidenceStore.js
 var init_immutableEvidenceStore = __esm({
   "packages/memory/dist/immutableEvidenceStore.js"() {
     "use strict";
+    init_utf8PrefixIndex();
   }
 });
 
@@ -47739,6 +47747,7 @@ var init_immutableEvidenceStore = __esm({
 var init_structureAwareChunker = __esm({
   "packages/memory/dist/structureAwareChunker.js"() {
     "use strict";
+    init_utf8PrefixIndex();
   }
 });
 
@@ -300516,6 +300525,59 @@ init_dist3();
 
 // packages/orchestrator/dist/liveVirtualContext.js
 init_dist();
+
+// packages/orchestrator/dist/live-memory-passages.js
+var stopWords = new Set("a an and are as at be by can do for from has have how i in is it its me my of on or our please that the their them these they this those to us was we what when where which who will with you your".split(" "));
+
+// packages/orchestrator/dist/ste-communication-policy.js
+var STE_POLICY_MARKER = "[ASD-STE100 ISSUE 9 COMMUNICATION POLICY]";
+var STE_COMMUNICATION_POLICY = `${STE_POLICY_MARKER}
+
+Use ASD-STE100 Issue 9 only for technical, procedural, causal, safety-critical, and evidence-bearing communication.
+Apply the same technical guidance to internal agent communication.
+Do not apply controlled vocabulary or technical sentence limits to casual conversation.
+On a conversational surface, preserve the established voice, relationship, cadence, humor, contractions, punctuation, and ordinary social language.
+Do not make casual dialogue sound like technical documentation.
+When one reply mixes casual and technical content, keep the casual framing natural and apply the controlled-language rules to the factual content.
+
+- Use approved words when possible.
+- Treat necessary project and domain terms as technical terms.
+- Use one term for each concept.
+- Use American English spelling.
+- In controlled technical content, do not use contractions, slang, unexplained jargon, or idioms.
+- Use active voice.
+- Use passive voice only when the agent is unknown.
+- Use simple verb tenses.
+- Use direct verbs.
+- Avoid phrasal verbs.
+- Keep each instruction at 20 words or fewer.
+- Give one instruction in each sentence.
+- Put a condition before its instruction.
+- Keep each descriptive sentence at 25 words or fewer.
+- Keep one topic in each paragraph.
+- Keep each paragraph at six sentences or fewer.
+- Use a vertical list for complex information.
+- Use clear connecting words.
+- Do not use semicolons.
+- Identify the level of each safety risk.
+- Start each safety instruction with a clear command or condition.
+- Explain the possible result of each safety risk.
+
+Preserve exact content in these items:
+
+- Code and code blocks
+- JSON, schemas, keys, and API data
+- Commands, paths, identifiers, and formal names
+- User input and source quotations
+- Logs, tool output, and test output
+- Required machine formats
+
+Use STE for all text that explains an exact item.
+If an exact format conflicts with STE, use the exact format.
+Do not strip punctuation or rewrite generated output to simulate STE compliance.
+Do not claim certified ASD-STE100 conformance without a qualified human review.`;
+
+// packages/orchestrator/dist/liveVirtualContext.js
 var PLANNER_SYSTEM = [
   "You are the query planner for a lossless long-context virtual-memory system.",
   "Decide which historical source evidence the active request needs. Do not answer the request.",
@@ -300997,54 +301059,6 @@ var PERSONALITY_PRESETS = {
 };
 var PRESET_NAMES = Object.keys(PERSONALITY_PRESETS);
 
-// packages/orchestrator/dist/ste-communication-policy.js
-var STE_POLICY_MARKER = "[ASD-STE100 ISSUE 9 COMMUNICATION POLICY]";
-var STE_COMMUNICATION_POLICY = `${STE_POLICY_MARKER}
-
-Use ASD-STE100 Issue 9 only for technical, procedural, causal, safety-critical, and evidence-bearing communication.
-Apply the same technical guidance to internal agent communication.
-Do not apply controlled vocabulary or technical sentence limits to casual conversation.
-On a conversational surface, preserve the established voice, relationship, cadence, humor, contractions, punctuation, and ordinary social language.
-Do not make casual dialogue sound like technical documentation.
-When one reply mixes casual and technical content, keep the casual framing natural and apply the controlled-language rules to the factual content.
-
-- Use approved words when possible.
-- Treat necessary project and domain terms as technical terms.
-- Use one term for each concept.
-- Use American English spelling.
-- In controlled technical content, do not use contractions, slang, unexplained jargon, or idioms.
-- Use active voice.
-- Use passive voice only when the agent is unknown.
-- Use simple verb tenses.
-- Use direct verbs.
-- Avoid phrasal verbs.
-- Keep each instruction at 20 words or fewer.
-- Give one instruction in each sentence.
-- Put a condition before its instruction.
-- Keep each descriptive sentence at 25 words or fewer.
-- Keep one topic in each paragraph.
-- Keep each paragraph at six sentences or fewer.
-- Use a vertical list for complex information.
-- Use clear connecting words.
-- Do not use semicolons.
-- Identify the level of each safety risk.
-- Start each safety instruction with a clear command or condition.
-- Explain the possible result of each safety risk.
-
-Preserve exact content in these items:
-
-- Code and code blocks
-- JSON, schemas, keys, and API data
-- Commands, paths, identifiers, and formal names
-- User input and source quotations
-- Logs, tool output, and test output
-- Required machine formats
-
-Use STE for all text that explains an exact item.
-If an exact format conflicts with STE, use the exact format.
-Do not strip punctuation or rewrite generated output to simulate STE compliance.
-Do not claim certified ASD-STE100 conformance without a qualified human review.`;
-
 // packages/orchestrator/dist/phase-skill-guidance.js
 init_dist3();
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.805",
+  "version": "1.0.806",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.805",
+      "version": "1.0.806",
       "bundleDependencies": [
         "image-to-ascii"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnius",
-  "version": "1.0.805",
+  "version": "1.0.806",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/library.js",