@vib795/agent-memory 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,6 +1,9 @@
1
1
  # agent-memory
2
2
 
3
+ [![npm](https://img.shields.io/npm/v/@vib795/agent-memory)](https://www.npmjs.com/package/@vib795/agent-memory)
3
4
  [![test](https://github.com/vib795/agent-memory/actions/workflows/test.yml/badge.svg)](https://github.com/vib795/agent-memory/actions/workflows/test.yml)
5
+ [![release](https://github.com/vib795/agent-memory/actions/workflows/release.yml/badge.svg)](https://github.com/vib795/agent-memory/actions/workflows/release.yml)
6
+ [![provenance](https://img.shields.io/badge/provenance-attested-brightgreen)](https://www.npmjs.com/package/@vib795/agent-memory)
4
7
  [![node](https://img.shields.io/badge/node-%3E%3D22.5-brightgreen)](https://nodejs.org)
5
8
  [![dependencies](https://img.shields.io/badge/runtime%20dependencies-0-brightgreen)](package.json)
6
9
  [![license](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
@@ -115,6 +118,22 @@ npm install -g https://github.com/vib795/agent-memory.git
115
118
  agent-memory setup
116
119
  ```
117
120
 
121
+ Every release is mirrored to **GitHub Packages**. Treat that as redundancy rather
122
+ than a second front door: GitHub Packages requires authentication even for public
123
+ packages, so installing from it costs you a token that npmjs does not ask for.
124
+
125
+ ```bash
126
+ npm config set @vib795:registry https://npm.pkg.github.com
127
+ npm config set //npm.pkg.github.com/:_authToken <a PAT with read:packages>
128
+ npm install -g @vib795/agent-memory
129
+ agent-memory setup
130
+ ```
131
+
132
+ Prefer npmjs unless you have a specific reason not to. Releases there are published
133
+ by CI from a tag and carry a [provenance attestation](https://docs.npmjs.com/generating-provenance-statements),
134
+ so `npm audit signatures` will tell you the tarball you installed was built from the
135
+ commit it claims. Neither the git nor the GitHub Packages path gives you that.
136
+
118
137
  `setup` probes for every agent on the machine and installs into each one it finds,
119
138
  in whatever format that tool reads. It then creates the store and generates the
120
139
  routing digest.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vib795/agent-memory",
3
- "version": "0.1.2",
3
+ "version": "0.1.4",
4
4
  "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
5
5
  "keywords": [
6
6
  "github-copilot",
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: recall
3
3
  version: 0.1.0
4
- description: "Durable project knowledge store. This line is regenerated by `agent-memory compact`. Use when you need to know how a system works, why a decision was made, what convention applies, or what the environment forbids."
4
+ description: "Durable project knowledge: 5 notes, 1 constraint across agent-memory. Topics: memory store is markdown with a disposable sqlite cache, chose node:sqlite over better-sqlite3, sqlite recursive cte is the graph engine. Use when you need to know how a system works, why a decision was made, what convention applies, or what the environment forbids."
5
5
  allowed-tools:
6
6
  - Bash
7
7
  - Read