jonah-fleet 1.36.0 → 1.37.0

package/CHANGELOG.md

@@ -5,6 +5,13 @@ All notable changes to `jonah-fleet` will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.37.0](https://github.com/Jonah-Projects/jonah-fleet/compare/v1.36.0...v1.37.0) (2026-10-11)
+
+
+### Features
+
+* **prompts,memory:** partition LESSONS.md ingestion by routine role ([#700](https://github.com/Jonah-Projects/jonah-fleet/issues/700)) ([21fe1b2](https://github.com/Jonah-Projects/jonah-fleet/commit/21fe1b21669ee0d7dc470c601732fb395efa0126))
+
 ## [1.36.0](https://github.com/Jonah-Projects/jonah-fleet/compare/v1.35.2...v1.36.0) (2026-10-11)
 
 
@@ -23,8 +30,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- **memory:** partition `LESSONS.md` operational memory ingestion by routine role (`[autowork]`, `[peer-review]`, `[general]`) to prevent unbounded prompt token bloat while maintaining high-signal operational memory
 - **runner:** add head-tail streaming truncation circuit breaker (`DEFAULT_MAX_LINES = 500`, `DEFAULT_MAX_BYTES = 64KB`) for command execution and large tool outputs to prevent context overflow and worker stalls
 
+
 ### Fixed
 
 - **terminal-card:** refine backlog triage hints to provide targeted unblock advice for radar digests and `needs-attention` issues instead of generic `needs-human` prompts

package/dist/lib/memory.d.ts

@@ -0,0 +1,61 @@
+/**
+ * Operational Memory (LESSONS.md) Partitioning and Filtering
+ *
+ * Implements role-filtered memory recall inspired by huggingface/funes v1.6.0 (PR #214),
+ * allowing autonomous routines (autowork, peer-review, optimizer, etc.) to ingest
+ * only role-relevant and general lessons rather than the unbounded file.
+ */
+export declare const KNOWN_ROUTINE_ROLES: Set<string>;
+export interface LessonEntry {
+    raw: string;
+    role: string;
+    tag: string;
+    title: string;
+    symptom?: string;
+    rootCause?: string;
+    rule?: string;
+}
+export interface LessonEntryInput {
+    role?: string;
+    tag?: string;
+    title: string;
+    symptom: string;
+    rootCause: string;
+    rule: string;
+}
+/**
+ * Parses raw LESSONS.md content into header preamble and array of structured entries.
+ */
+export declare function parseLessonsFile(content: string): {
+    preamble: string;
+    entries: LessonEntry[];
+};
+/**
+ * Parses structured lesson entries from LESSONS.md body or full file content.
+ */
+export declare function parseLessonEntries(content: string): LessonEntry[];
+/**
+ * Checks whether a lesson entry matches a given routine role.
+ * Includes:
+ * - Direct matches (e.g. entry tagged 'autowork' when role is 'autowork')
+ * - Composite matches (e.g. entry tagged 'autowork:git')
+ * - 'general' entries
+ * - General/legacy subsystem entries not claimed by another known routine role
+ */
+export declare function isLessonRelevantForRole(entry: LessonEntry, role: string): boolean;
+/**
+ * Filters LESSONS.md content to only entries relevant for the active routine role.
+ */
+export declare function filterLessonsByRole(content: string, role: string): string;
+/**
+ * Formats a structured 3-line lesson entry under the active routine tag.
+ */
+export declare function formatLessonEntry(input: LessonEntryInput): string;
+/**
+ * Appends a new structured lesson entry to LESSONS.md, enforcing the 25-entry hard cap.
+ * If adding the entry exceeds maxEntries, the oldest entries are evicted.
+ */
+export declare function appendLessonEntry(content: string, input: LessonEntryInput, options?: {
+    maxEntries?: number;
+}): string;
+//# sourceMappingURL=memory.d.ts.map

package/dist/lib/memory.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"memory.d.ts","sourceRoot":"","sources":["../../src/lib/memory.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,mBAAmB,aAS9B,CAAC;AAEH,MAAM,WAAW,WAAW;IAC1B,GAAG,EAAE,MAAM,CAAC;IACZ,IAAI,EAAE,MAAM,CAAC;IACb,GAAG,EAAE,MAAM,CAAC;IACZ,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAED,MAAM,WAAW,gBAAgB;IAC/B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;IAClB,IAAI,EAAE,MAAM,CAAC;CACd;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,GAAG;IAAE,QAAQ,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,WAAW,EAAE,CAAA;CAAE,CAc9F;AAED;;GAEG;AACH,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,MAAM,GAAG,WAAW,EAAE,CA4DjE;AAED;;;;;;;GAOG;AACH,wBAAgB,uBAAuB,CAAC,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAuBjF;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,MAAM,CAczE;AAED;;GAEG;AACH,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,gBAAgB,GAAG,MAAM,CAGjE;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,CAC/B,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,gBAAgB,EACvB,OAAO,GAAE;IAAE,UAAU,CAAC,EAAE,MAAM,CAAA;CAAO,GACpC,MAAM,CAoBR"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jonah-fleet",
-  "version": "1.36.0",
+  "version": "1.37.0",
   "description": "Standalone autonomous agent fleet with Symphony orchestration, claim protocols, and continuous improvement loops",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/templates/docs/AGENTS.template.md

@@ -98,3 +98,10 @@ To trigger the Autowork routine manually on any specific issue, use the GitHub A
 - Auth boundaries required for all sensitive mutations.
 - Never commit credentials, tokens, or secret keys to version control.
 - Validate request inputs and sanitize outputs.
+
+## Operational Memory (LESSONS.md)
+
+- **Role-Partitioned Memory**: Standardize lesson entries in `LESSONS.md` using routine role tags: `[autowork]`, `[peer-review]`, `[optimizer]`, or `[general]` (e.g. `### [autowork] Title`, `### [peer-review] Title`, `### [general] Title`). Subsystem composite tags are also supported (e.g. `### [autowork:subsystem] Title`).
+- **Targeted Routine Ingestion**: Autonomous routines ingest general lessons plus routine-specific lessons, omitting unrelated entries to prevent unbounded token expansion while maintaining high-signal operational memory.
+- **Post-Run Recording**: When capturing new non-obvious gotchas or quirks on PR branches, always tag the entry with the active routine's role (or `[general]`) and adhere strictly to the 25-entry hard cap.
+

package/templates/docs/LESSONS.template.md

@@ -1,7 +1,9 @@
 # Operational Lessons & Repository Heuristics
 <!-- Invariants: Max 25 entries. Hard cap. Older entries graduate or demote to LESSONS_ARCHIVE.md -->
+<!-- Tagging Syntax: Standardize entries with routine role tags [autowork], [peer-review], [optimizer], or [general] (e.g. ### [autowork] Title, ### [peer-review] Title, ### [general] Title). Subsystem suffixes are supported: ### [autowork:subsystem] Title. Each routine ingests only its own role-tagged entries plus [general] and legacy entries. -->
 
 ### [subsystem] Title
+<!-- Example role-tagged entry: ### [general] Title or ### [autowork] Title -->
 - **Symptom:** <Symptom description or error message>
 - **Root Cause:** <Brief explanation of the underlying cause>
 - **Rule:** <Actionable rule or constraint to follow>

package/templates/prompts/autowork.md

@@ -220,7 +220,7 @@ _Generated by [Antigravity](${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/ru
         `- **Prior Failure Context**: <summary of past error/crash and strategy to avoid repeating it>`
     - If bug: use `/diagnosing-bugs` to establish reproduction test before fixing.
     - If large/complex: use `/domain-modeling` and `/codebase-design`.
-    - **Pre-Flight Memory Scan**: If `LESSONS.md` exists, grep matching subsystem tags (`grep -E "^### \[(subsystem)\]" LESSONS.md -A 4`) to incorporate known landmines into implementation plans before writing code.
+    - **Pre-Flight Memory Scan**: If `LESSONS.md` exists, grep matching subsystem tags (`grep -E "^### \[(subsystem)\]" LESSONS.md -A 4`) or filter entries tagged for `[autowork]` or `[general]` (e.g. `grep -E "^### \[(autowork|general)\]" LESSONS.md -A 4`), omitting unrelated routine roles to incorporate known landmines into implementation plans before writing code without token bloat.
     - **The Red Gate Protocol (Pre-Implementation Verifier Check)**: Before writing ANY production implementation code, define the verifier or write a reproduction test, and execute it:
       - **The check MUST fail** (red). If the verifier passes before you touch production code, the subsequent work proves nothing.
       - **Already Green Check**: If the verifier passes *before* code changes, stop immediately and evaluate:
@@ -268,7 +268,7 @@ _Generated by [Antigravity](${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/ru
     - **Diagnostic Reflex**: On unexpected test/build failure during TDD, grep symptom text in `LESSONS.md` before making speculative code edits.
     - Run repository tests and verification.
     - **Disk Read-Back Verification**: Verify written configs, schemas, and generated files by reading values directly back from disk files (`cat`, `jq`, test assertions), never from shell variables or memory.
-    - **Pre-PR Lessons Capture Gate**: If solving the issue required overcoming a non-obvious quirk not caught by tests/linters, append a 3-line structured entry on the active PR branch adhering to the 25-entry hard cap. Never write to `LESSONS.md` directly on `main`.
+    - **Pre-PR Lessons Capture Gate**: If solving the issue required overcoming a non-obvious quirk not caught by tests/linters, append a 3-line structured entry tagged under the active routine role (`### [autowork] <Title>` or `### [general] <Title>`) on the active PR branch adhering to the 25-entry hard cap. Never write to `LESSONS.md` directly on `main`.
     - **Milestone 2 (Verification & Tests)**: Once implementation passes tests and type checks, emit milestone card if `$ROUTINE_ISSUE_NUMBER` is set:
       ```bash
       gh issue comment "$ROUTINE_ISSUE_NUMBER" --body "### 🧪 Milestone: Verification & Tests
@@ -365,7 +365,7 @@ Cacheable across consecutive runs within the same repository.
 In this tier, Autowork ingests semi-stable repository conventions, operational memory, and configuration rules that change infrequently across consecutive runs in the same repository:
 
 1. **Repository Conventions (`AGENTS.md`)**: Read `AGENTS.md` (or `CLAUDE.md` / `GEMINI.md`) for build/test/lint commands, code formatting rules, architectural guidelines, and design system tokens.
-2. **Operational Memory (`LESSONS.md`)**: If `LESSONS.md` exists, ingest active operational gotchas (`grep -E "^### \[(subsystem)\]" LESSONS.md -A 4`) to avoid known pitfalls and regression patterns (enforcing the 25-entry hard cap).
+2. **Operational Memory (`LESSONS.md`)**: If `LESSONS.md` exists, ingest role-relevant operational gotchas (`grep -E "^### \[(subsystem)\]" LESSONS.md -A 4`) filtered for the active routine role (`[autowork]` or `[general]`), omitting entries from other routine roles to avoid known pitfalls and regression patterns while minimizing token consumption (enforcing the 25-entry hard cap).
 3. **Fleet Manifest (`agents-manifest.json`)**: Ingest configured presets, model family assignments, and timeout/iteration ceilings.
 4. **Engineering Skills (`.agents/skills/`)**: Leverage domain skills (`code-review`, `codebase-design`, `diagnosing-bugs`, `domain-modeling`, `grill-me`, `resolving-merge-conflicts`, `tdd`, `triage`, `writing-for-agents`).
 

package/templates/prompts/peer-review.md

@@ -142,7 +142,7 @@ Check if `$PR_NUMBER` is set:
 1. Run `/code-review` over the diff (or delta commits if re-review) evaluating:
    - **Standards**: Conformance to `AGENTS.md` (or `CLAUDE.md`/`GEMINI.md`), conventions, and architecture.
    - **Spec Compliance**: Verification against the linked issue's deliverables (`## Tasks`), or against the PR description's summary/changes if no tracking issue is linked.
-   - **Operational Memory & Lessons Invariant**: Inspect `LESSONS.md` diffs in PRs to verify the lesson is accurate, non-trivial, follows the 3-line structured schema, and the file adheres to the 25-entry hard cap.
+   - **Operational Memory & Lessons Invariant**: Inspect `LESSONS.md` diffs in PRs to verify the lesson is accurate, non-trivial, follows the 3-line structured schema, tags the originating routine role (e.g. `### [autowork] ...`, `### [peer-review] ...`, or `### [general] ...`), and the file adheres to the 25-entry hard cap. If reviewing code that solves a non-obvious gotcha or recurring architectural trap, ensure a structured 3-line entry tagged with the originating routine role (`### [peer-review] ...` or `### [general] ...`) is appended to `LESSONS.md`.
 2. Run Security Pass: auth gates, permission checks, injection risks, sensitive credentials.
 3. **Design System & Viewport Density Pass** (if PR modifies frontend/rendered UI):
    - **Token Purity**: Check for arbitrary CSS/Tailwind sizing overrides (e.g. `text-[...px]`, `w-[...px]`) or bespoke button styling bypassing standard design system tokens.
@@ -298,7 +298,7 @@ Cacheable across consecutive runs within the same repository.
 In this tier, Peer Review ingests semi-stable repository conventions, operational memory, and configuration rules that change infrequently across consecutive runs in the same repository:
 
 1. **Repository Conventions (`AGENTS.md`)**: Read `AGENTS.md` (or `CLAUDE.md` / `GEMINI.md`) for coding standards, architectural patterns, design system token purity, and required CI / test commands.
-2. **Operational Memory (`LESSONS.md`)**: Verify that any non-obvious quirks or gotchas captured on the active PR branch adhere to the 25-entry hard cap.
+2. **Operational Memory (`LESSONS.md`)**: If `LESSONS.md` exists, ingest role-relevant operational gotchas filtered for the active routine role (`grep -E "^### \[(peer-review|general)\]" LESSONS.md -A 4`), omitting unrelated routine roles, and verify that any non-obvious quirks or gotchas captured on the active PR branch adhere to the 25-entry hard cap.
 3. **Fleet Manifest (`agents-manifest.json`)**: Ingest configured review models, round caps, and iteration ceilings.
 4. **Engineering Skills (`.agents/skills/`)**: Leverage `code-review`, `design-critique`, and `writing-for-agents` for structured evaluation.