@wrongstack/core 0.303.0 → 0.305.1

package/dist/core/system-prompt-builder.d.ts

@@ -115,6 +115,18 @@ export interface DefaultSystemPromptBuilderOptions {
      * tests, embedders, and plugin-provided prompt experiments.
      */
     instructionBundle?: InstructionBundle | undefined;
+    /**
+     * Project jargon dictionary source. When set, the builder appends a
+     * compact `[Project Jargon Dictionary]` block to the prompt, sourced
+     * from SAGE-tagged `domain-term` memories. The host CLI/TUI/WebUI is
+     * responsible for handing the *same* `ProjectSageMemoryPort` it uses
+     * for memory injection into this slot — see
+     * `packages/core/src/core/system-prompt-glossary.ts` for the wiring
+     * contract and the SAGE architectural-rule cross-reference.
+     *
+     * omit → no glossary block (default).
+     */
+    domainGlossary?: MemoryStore | undefined;
 }
 export declare class DefaultSystemPromptBuilder implements SystemPromptBuilder {
     private readonly opts;
@@ -165,7 +177,7 @@ export declare class DefaultSystemPromptBuilder implements SystemPromptBuilder {
     private get tier();
     /**
      * Returns the max tool description length for the current tier.
-     * Per the design doc: off=80, minimal=40, light=50, medium=60, aggressive=70.
+     * The aggressive tier has the shortest descriptions; off keeps the most detail.
      */
     private toolDescLimit;
     build(ctx: BuildContext): Promise<TextBlock[]>;

package/dist/core/system-prompt-glossary.d.ts

@@ -0,0 +1,73 @@
+/**
+ * `[Project Jargon Dictionary]` block for the agent system prompt.
+ *
+ * The block is rendered FROM the same SAGE port the agent uses for
+ * all other memory context — never from `@wrongstack/sage-mcp`.
+ * Per the SAGE architectural rule (see `packages/sage/docs/direct-icp-usage.md`
+ * §1, "The architectural rule"), in-process consumers like the system-prompt
+ * builder must consume SAGE through `ProjectSageMemoryPort`/`SqliteMemoryPort`
+ * only. MCP is for external consumers; reading the glossary through MCP would
+ * open a second writer to the same SQLite file.
+ *
+ * This module is therefore intentionally `MemoryStore`-shaped rather than
+ * typed against the SAGE surface directly, so the prompt-builder stays
+ * core-level (no `@wrongstack/sage` import — `core` does not depend on
+ * `sage`). The host (CLI/TUI/WebUI) constructs the `SageDomainTermExtractor`
+ * against its own SAGE port and stitches it onto the builder via the
+ * `injectDomainGlossary` helper.
+ *
+ * Implementation note — the minimal-dictionary format:
+ *   We render at most `maxEntries` bullets (default 12, configurable per
+ *   token-saving tier) of `**Term** — short definition`. Definitions are
+ *   capped at `maxEntryChars` chars per bullet (default 80) so the block
+ *   always fits inside ~1k tokens. The format mirrors what the agent would
+ *   otherwise have to re-derive by reading every recalled SAGE memory, which
+ *   is the exact token-cost the design reduces.
+ */
+import type { MemoryStore } from '../types/memory.js';
+import type { BuildContext } from '../types/system-prompt.js';
+export interface DomainGlossaryOptions {
+    /** Max number of bullets. Default 12. */
+    maxEntries?: number | undefined;
+    /** Max chars per bullet line (after the **Term** header). Default 80. */
+    maxEntryChars?: number | undefined;
+}
+export interface DomainGlossary {
+    /** The extractor port shape we depend on. */
+    readonly memory: MemoryStore;
+    /** Render the block, or `null` when no glossary entries exist. */
+    readonly formatGlossaryBlock: () => Promise<string | null>;
+}
+/**
+ * Build the minimal `[Project Jargon Dictionary]` block.
+ *
+ * Returns:
+ *   - `null` when the memory store is missing or doesn't expose the glossary
+ *     shape — never throw; the prompt builder logs and continues.
+ *   - an empty string when the memory store has no glossary entries.
+ *   - a markdown block capped at `maxEntries` × `maxEntryChars` otherwise.
+ *
+ * The block is prefixed with a clear provenance heading so the agent
+ * understands the source and can override / refresh at runtime via
+ * the SAGE tooling. The trailing line lists the lookup tag for grep
+ * parity (`domain-term`).
+ */
+export declare function renderDomainGlossary(ctx: BuildContext, memory: MemoryStore | undefined, options?: DomainGlossaryOptions): Promise<string | null>;
+/**
+ * Wire a glossary block into a `DefaultSystemPromptBuilder` via the
+ * existing `contributors` channel (see `system-prompt-contributor.ts`).
+ *
+ * Use from the host (CLI/TUI/WebUI) like this:
+ *
+ *   const builder = new DefaultSystemPromptBuilder({
+ *     ...other opts,
+ *     contributors: [
+ *       ...DefaultSystemPromptBuilder.defaultContributors({ projectRoot }),
+ *       makeDomainGlossaryContributor({ memory: sagePort }),
+ *     ],
+ *   });
+ *
+ * The contributor returns `[]` for non-SAGE stores so the prompt stays clean.
+ */
+export declare function makeDomainGlossaryContributor(glossary: DomainGlossary): (ctx: BuildContext) => Promise<import('../types/blocks.js').TextBlock[]>;
+//# sourceMappingURL=system-prompt-glossary.d.ts.map

package/dist/core/system-prompt-memory-skills.d.ts

@@ -26,8 +26,8 @@ export interface OnlineAgentsCache {
  * a fresh object on every status check, so reference equality always misses.
  *
  * Tier behaviour:
- * - 'off' / 'medium' / 'aggressive' → full list with names, sessions, sources
- * - 'minimal' / 'light' → count only (no list)
+ * - 'off' / 'medium' → full list with names, sessions, sources
+ * - 'minimal' / 'light' / 'aggressive' → count only (no list)
  *
  * Returns the (possibly updated) cache alongside the text; the caller stores it.
  */