@codyswann/lisa 2.220.1 → 2.221.1

package/plugins/lisa/.codex-plugin/skills/lisa-github-read-issue/SKILL.md

@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
 
 If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
 
-## Phase 6 — Fetch Linked PRs (Native `Resolves` / Cross-references)
+## Phase 6 — Fetch Linked PRs and Label-Event History
 
-GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship:
+GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
 
 ```bash
-gh api graphql -f query='query($org:String!,$repo:String!,$number:Int!){repository(owner:$org,name:$repo){issue(number:$number){closedByPullRequestsReferences(first:50){nodes{number title state merged mergedAt url repository{nameWithOwner}}}timelineItems(first:100,itemTypes:[CROSS_REFERENCED_EVENT]){nodes{...on CrossReferencedEvent{source{...on PullRequest{number title state url repository{nameWithOwner}}}}}}}}}' -F org=<org> -F repo=<repo> -F number=<number>
+query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
+  repository(owner:$org,name:$repo){
+    issue(number:$number){
+      closedByPullRequestsReferences(first:50){
+        nodes{number title state merged mergedAt url repository{nameWithOwner}}
+      }
+      timelineItems(
+        first:100
+        after:$cursor
+        itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
+      ){
+        pageInfo{hasNextPage endCursor}
+        nodes{
+          ...on CrossReferencedEvent{
+            createdAt
+            actor{login}
+            source{...on PullRequest{number title state url repository{nameWithOwner}}}
+          }
+          ...on LabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+          ...on UnlabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+        }
+      }
+    }
+  }
+}'
+
+cursor=null
+while :; do
+  if [ "$cursor" = null ]; then
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
+  else
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
+  fi
+  printf '%s\n' "$page"
+  has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
+  cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
+  [ "$has_next" = true ] || break
+done
 ```
 
-Capture: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4.
+Capture:
+- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
+- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
+
+Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
 
 For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
 
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
 ### Body-referenced (`Resolves #<n>`)
 <per-PR block>
 
+## Label-Event History
+- Status: <known|unknown>
+- Events:
+  - <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
+  - ...
+
 ## Sibling Sub-issues (other children of the same parent, <count>)
 - <ref> — <type> — <status> — <assignee> — <title>  **[FLAG: in progress by other assignee]**
 

package/plugins/lisa/rules/eager/project-learnings.md

@@ -0,0 +1,15 @@
+# Project Learnings (load-bearing)
+
+Before normal task work, resolve this repository's committed `.lisa.config.json`
+and derive the canonical learnings file as the sibling of `projectRulesFile`
+(default: `.claude/rules/PROJECT_LEARNINGS.md`). If that file exists, consume it
+through the executable Lisa learnings contract exported by
+`@codyswann/lisa/learnings` before relying on ad-hoc memory or prior-session
+notes.
+
+Missing learnings are a silent no-op. Malformed, non-canonical, unsafe, or
+over-budget learnings produce one readable warning, apply no entry, and must not
+block unrelated task work. Never append automated learnings to
+`PROJECT_RULES.md`; project learnings are a separate machine-managed document.
+
+Full prose: [reference/project-learnings.md](../reference/project-learnings.md).

package/plugins/lisa/rules/reference/project-learnings.md

@@ -0,0 +1,37 @@
+# Project Learnings
+
+Project learnings are Lisa's bounded, repo-local memory surface. They are stored
+in `PROJECT_LEARNINGS.md`, derived as the sibling of the configured
+`.lisa.config.json` `projectRulesFile` value. With no config override, the path
+is `.claude/rules/PROJECT_LEARNINGS.md`.
+
+Consume learnings before normal task work whenever the file exists. Use the
+executable contract from `@codyswann/lisa/learnings` to parse, validate, and
+budget-check the document. Do not duplicate numeric caps in rules or prompts;
+the exported contract is the source of truth.
+
+Each persisted entry has seven fields:
+
+- `id`
+- `rule`
+- `why`
+- `provenance`
+- `first_learned`
+- `last_confirmed`
+- `confidence`
+
+Only entries accepted by the executable contract may influence the session. A
+missing file is expected and silent. Malformed Markdown, invalid JSONL, unsafe
+paths, non-canonical content, or over-budget documents produce one readable
+warning, apply no entry, and do not block unrelated work.
+
+Precedence:
+
+1. System, developer, user, and repo instructions still outrank learnings.
+2. Committed project rules remain durable human-authored guidance.
+3. Project learnings add recent operational knowledge, but never rewrite or
+   append to `PROJECT_RULES.md`.
+
+Antigravity note: agy does not receive the plugin `rules/` tree. Lisa reconciles
+a bounded `AGENTS.md` bridge that points agy at this same file without copying
+learning bodies or restoring the retired full rules bake.

package/plugins/lisa/skills/lisa-github-read-issue/SKILL.md

@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
 
 If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
 
-## Phase 6 — Fetch Linked PRs (Native `Resolves` / Cross-references)
+## Phase 6 — Fetch Linked PRs and Label-Event History
 
-GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship:
+GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
 
 ```bash
-gh api graphql -f query='query($org:String!,$repo:String!,$number:Int!){repository(owner:$org,name:$repo){issue(number:$number){closedByPullRequestsReferences(first:50){nodes{number title state merged mergedAt url repository{nameWithOwner}}}timelineItems(first:100,itemTypes:[CROSS_REFERENCED_EVENT]){nodes{...on CrossReferencedEvent{source{...on PullRequest{number title state url repository{nameWithOwner}}}}}}}}}' -F org=<org> -F repo=<repo> -F number=<number>
+query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
+  repository(owner:$org,name:$repo){
+    issue(number:$number){
+      closedByPullRequestsReferences(first:50){
+        nodes{number title state merged mergedAt url repository{nameWithOwner}}
+      }
+      timelineItems(
+        first:100
+        after:$cursor
+        itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
+      ){
+        pageInfo{hasNextPage endCursor}
+        nodes{
+          ...on CrossReferencedEvent{
+            createdAt
+            actor{login}
+            source{...on PullRequest{number title state url repository{nameWithOwner}}}
+          }
+          ...on LabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+          ...on UnlabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+        }
+      }
+    }
+  }
+}'
+
+cursor=null
+while :; do
+  if [ "$cursor" = null ]; then
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
+  else
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
+  fi
+  printf '%s\n' "$page"
+  has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
+  cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
+  [ "$has_next" = true ] || break
+done
 ```
 
-Capture: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4.
+Capture:
+- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
+- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
+
+Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
 
 For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
 
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
 ### Body-referenced (`Resolves #<n>`)
 <per-PR block>
 
+## Label-Event History
+- Status: <known|unknown>
+- Events:
+  - <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
+  - ...
+
 ## Sibling Sub-issues (other children of the same parent, <count>)
 - <ref> — <type> — <status> — <assignee> — <title>  **[FLAG: in progress by other assignee]**
 

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-agy/skills/lisa-github-read-issue/SKILL.md

@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
 
 If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
 
-## Phase 6 — Fetch Linked PRs (Native `Resolves` / Cross-references)
+## Phase 6 — Fetch Linked PRs and Label-Event History
 
-GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship:
+GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
 
 ```bash
-gh api graphql -f query='query($org:String!,$repo:String!,$number:Int!){repository(owner:$org,name:$repo){issue(number:$number){closedByPullRequestsReferences(first:50){nodes{number title state merged mergedAt url repository{nameWithOwner}}}timelineItems(first:100,itemTypes:[CROSS_REFERENCED_EVENT]){nodes{...on CrossReferencedEvent{source{...on PullRequest{number title state url repository{nameWithOwner}}}}}}}}}' -F org=<org> -F repo=<repo> -F number=<number>
+query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
+  repository(owner:$org,name:$repo){
+    issue(number:$number){
+      closedByPullRequestsReferences(first:50){
+        nodes{number title state merged mergedAt url repository{nameWithOwner}}
+      }
+      timelineItems(
+        first:100
+        after:$cursor
+        itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
+      ){
+        pageInfo{hasNextPage endCursor}
+        nodes{
+          ...on CrossReferencedEvent{
+            createdAt
+            actor{login}
+            source{...on PullRequest{number title state url repository{nameWithOwner}}}
+          }
+          ...on LabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+          ...on UnlabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+        }
+      }
+    }
+  }
+}'
+
+cursor=null
+while :; do
+  if [ "$cursor" = null ]; then
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
+  else
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
+  fi
+  printf '%s\n' "$page"
+  has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
+  cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
+  [ "$has_next" = true ] || break
+done
 ```
 
-Capture: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4.
+Capture:
+- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
+- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
+
+Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
 
 For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
 
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
 ### Body-referenced (`Resolves #<n>`)
 <per-PR block>
 
+## Label-Event History
+- Status: <known|unknown>
+- Events:
+  - <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
+  - ...
+
 ## Sibling Sub-issues (other children of the same parent, <count>)
 - <ref> — <type> — <status> — <assignee> — <title>  **[FLAG: in progress by other assignee]**
 

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/rules/eager/project-learnings.md

@@ -0,0 +1,15 @@
+# Project Learnings (load-bearing)
+
+Before normal task work, resolve this repository's committed `.lisa.config.json`
+and derive the canonical learnings file as the sibling of `projectRulesFile`
+(default: `.claude/rules/PROJECT_LEARNINGS.md`). If that file exists, consume it
+through the executable Lisa learnings contract exported by
+`@codyswann/lisa/learnings` before relying on ad-hoc memory or prior-session
+notes.
+
+Missing learnings are a silent no-op. Malformed, non-canonical, unsafe, or
+over-budget learnings produce one readable warning, apply no entry, and must not
+block unrelated task work. Never append automated learnings to
+`PROJECT_RULES.md`; project learnings are a separate machine-managed document.
+
+Full prose: [reference/project-learnings.md](../reference/project-learnings.md).

package/plugins/lisa-copilot/rules/reference/project-learnings.md

@@ -0,0 +1,37 @@
+# Project Learnings
+
+Project learnings are Lisa's bounded, repo-local memory surface. They are stored
+in `PROJECT_LEARNINGS.md`, derived as the sibling of the configured
+`.lisa.config.json` `projectRulesFile` value. With no config override, the path
+is `.claude/rules/PROJECT_LEARNINGS.md`.
+
+Consume learnings before normal task work whenever the file exists. Use the
+executable contract from `@codyswann/lisa/learnings` to parse, validate, and
+budget-check the document. Do not duplicate numeric caps in rules or prompts;
+the exported contract is the source of truth.
+
+Each persisted entry has seven fields:
+
+- `id`
+- `rule`
+- `why`
+- `provenance`
+- `first_learned`
+- `last_confirmed`
+- `confidence`
+
+Only entries accepted by the executable contract may influence the session. A
+missing file is expected and silent. Malformed Markdown, invalid JSONL, unsafe
+paths, non-canonical content, or over-budget documents produce one readable
+warning, apply no entry, and do not block unrelated work.
+
+Precedence:
+
+1. System, developer, user, and repo instructions still outrank learnings.
+2. Committed project rules remain durable human-authored guidance.
+3. Project learnings add recent operational knowledge, but never rewrite or
+   append to `PROJECT_RULES.md`.
+
+Antigravity note: agy does not receive the plugin `rules/` tree. Lisa reconciles
+a bounded `AGENTS.md` bridge that points agy at this same file without copying
+learning bodies or restoring the retired full rules bake.

package/plugins/lisa-copilot/skills/lisa-github-read-issue/SKILL.md

@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
 
 If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
 
-## Phase 6 — Fetch Linked PRs (Native `Resolves` / Cross-references)
+## Phase 6 — Fetch Linked PRs and Label-Event History
 
-GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship:
+GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
 
 ```bash
-gh api graphql -f query='query($org:String!,$repo:String!,$number:Int!){repository(owner:$org,name:$repo){issue(number:$number){closedByPullRequestsReferences(first:50){nodes{number title state merged mergedAt url repository{nameWithOwner}}}timelineItems(first:100,itemTypes:[CROSS_REFERENCED_EVENT]){nodes{...on CrossReferencedEvent{source{...on PullRequest{number title state url repository{nameWithOwner}}}}}}}}}' -F org=<org> -F repo=<repo> -F number=<number>
+query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
+  repository(owner:$org,name:$repo){
+    issue(number:$number){
+      closedByPullRequestsReferences(first:50){
+        nodes{number title state merged mergedAt url repository{nameWithOwner}}
+      }
+      timelineItems(
+        first:100
+        after:$cursor
+        itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
+      ){
+        pageInfo{hasNextPage endCursor}
+        nodes{
+          ...on CrossReferencedEvent{
+            createdAt
+            actor{login}
+            source{...on PullRequest{number title state url repository{nameWithOwner}}}
+          }
+          ...on LabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+          ...on UnlabeledEvent{
+            createdAt
+            actor{login}
+            label{name}
+          }
+        }
+      }
+    }
+  }
+}'
+
+cursor=null
+while :; do
+  if [ "$cursor" = null ]; then
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
+  else
+    page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
+  fi
+  printf '%s\n' "$page"
+  has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
+  cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
+  [ "$has_next" = true ] || break
+done
 ```
 
-Capture: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4.
+Capture:
+- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
+- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
+
+Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
 
 For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
 
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
 ### Body-referenced (`Resolves #<n>`)
 <per-PR block>
 
+## Label-Event History
+- Status: <known|unknown>
+- Events:
+  - <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
+  - ...
+
 ## Sibling Sub-issues (other children of the same parent, <count>)
 - <ref> — <type> — <status> — <assignee> — <title>  **[FLAG: in progress by other assignee]**
 

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.220.1",
+  "version": "2.221.1",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/rules/project-learnings-reference.mdc

@@ -0,0 +1,42 @@
+---
+description: "Project Learnings"
+alwaysApply: false
+---
+
+# Project Learnings
+
+Project learnings are Lisa's bounded, repo-local memory surface. They are stored
+in `PROJECT_LEARNINGS.md`, derived as the sibling of the configured
+`.lisa.config.json` `projectRulesFile` value. With no config override, the path
+is `.claude/rules/PROJECT_LEARNINGS.md`.
+
+Consume learnings before normal task work whenever the file exists. Use the
+executable contract from `@codyswann/lisa/learnings` to parse, validate, and
+budget-check the document. Do not duplicate numeric caps in rules or prompts;
+the exported contract is the source of truth.
+
+Each persisted entry has seven fields:
+
+- `id`
+- `rule`
+- `why`
+- `provenance`
+- `first_learned`
+- `last_confirmed`
+- `confidence`
+
+Only entries accepted by the executable contract may influence the session. A
+missing file is expected and silent. Malformed Markdown, invalid JSONL, unsafe
+paths, non-canonical content, or over-budget documents produce one readable
+warning, apply no entry, and do not block unrelated work.
+
+Precedence:
+
+1. System, developer, user, and repo instructions still outrank learnings.
+2. Committed project rules remain durable human-authored guidance.
+3. Project learnings add recent operational knowledge, but never rewrite or
+   append to `PROJECT_RULES.md`.
+
+Antigravity note: agy does not receive the plugin `rules/` tree. Lisa reconciles
+a bounded `AGENTS.md` bridge that points agy at this same file without copying
+learning bodies or restoring the retired full rules bake.

package/plugins/lisa-cursor/rules/project-learnings.mdc

@@ -0,0 +1,20 @@
+---
+description: "Project Learnings (load-bearing)"
+alwaysApply: true
+---
+
+# Project Learnings (load-bearing)
+
+Before normal task work, resolve this repository's committed `.lisa.config.json`
+and derive the canonical learnings file as the sibling of `projectRulesFile`
+(default: `.claude/rules/PROJECT_LEARNINGS.md`). If that file exists, consume it
+through the executable Lisa learnings contract exported by
+`@codyswann/lisa/learnings` before relying on ad-hoc memory or prior-session
+notes.
+
+Missing learnings are a silent no-op. Malformed, non-canonical, unsafe, or
+over-budget learnings produce one readable warning, apply no entry, and must not
+block unrelated task work. Never append automated learnings to
+`PROJECT_RULES.md`; project learnings are a separate machine-managed document.
+
+Full prose: [reference/project-learnings.md](project-learnings-reference.mdc).