paragma 0.3.0 → 0.3.1

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.
Files changed (3) hide show
  1. package/README.md +2 -1
  2. package/SHA256SUMS +6 -6
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -142,6 +142,7 @@ pg write --decision "..." --why "..." --alternatives "..."
142
142
  pg write --error "<error line>" --cause "..." --fix "..."
143
143
  pg write payments/provider --file notes.md # a note; long text from a file or stdin (-)
144
144
  pg finish --done 1 "what changed, what is next" # tick off steps, leave the handoff
145
+ pg steps # the steps with their numbers (--drop 4, --edit 4 "text")
145
146
  pg ripple # what a change reaches: callers left as they were, tests to run
146
147
  pg tree # the code: files and symbols, with the notes about them marked
147
148
  pg ls # projects, or the notes of one; also pg mv, pg rm, pg doctor
@@ -166,7 +167,7 @@ pg run -- npm publish --token '$NPM_PUBLISH_TOKEN'
166
167
  pg git
167
168
  ```
168
169
 
169
- Opens a small screen: sign in to GitHub (with the GitHub CLI or the sign-in git already has, else in the browser with a code), then choose where the memory goes: a new private repository (`paragma-memory`), or one you have, in a `Paragma/` folder on its own branch or on its main branch. Choosing a public repository asks first. The `.env` files go only if you say so, and never to a public repository.
170
+ Opens a small screen: sign in to GitHub (with the GitHub CLI or the sign-in git already has, else in the browser with a code), then choose where the memory goes: a new private repository (`paragma-memory`, of your account or of one of its organizations), or one you have, in a `Paragma/` folder on its own branch or on its main branch. Choosing a public repository asks first. The `.env` files go only if you say so, and never to a public repository.
170
171
 
171
172
  From then on every change goes there by itself, a few seconds after it is made, in the background: the agent never waits for it. What other computers sent comes in the same way. On a new computer, `pg git` finds the memory in your repositories (your own and your organizations') and restores it, joined with whatever is already there. The indexes and the short-lived state in `.pg/` never go; they are rebuilt.
172
173
 
package/SHA256SUMS CHANGED
@@ -1,6 +1,6 @@
1
- 5fb0e7851a5b463d64c949ae9e940927eb86dd35c5466bbb4a73af20d471a140 pg-darwin-arm64
2
- d20bf0257481faa4385235bc53fc5669a1945de8342adf0b34ce1fc0c1c06a6f pg-darwin-x64
3
- a73eb5cca079271642fdbaa4c90594ed5857cc0a05a650b7b1b568007b451042 pg-linux-arm64
4
- 950eecf79c46163635bec0436efa551c242380b8ae23939c7f09362ced4c431f pg-linux-x64
5
- 2a523e3622166699e657e0f0597265569325a634e65ca28ccb00cc427300bd5e pg-windows-arm64.exe
6
- 8682f8501c0d8d9098daa6574d979c7392201028ccc0c48293c15a52a0dc8bfd pg-windows-x64.exe
1
+ 6579a0c8dc1eb5230c554f8172c15d32df4c40a6abe7456f1de867cda47f9615 pg-darwin-arm64
2
+ 6a35f09f8ccab9425e255b46166e57f4d3e10f8334d510ef78167f6054de9ca9 pg-darwin-x64
3
+ ecbb038504922ae7b1b0890faeedaf59e150906f1a797b560f792bbcfbd9b311 pg-linux-arm64
4
+ 506e76072ccb6bb1917aea6a2fca9a9653062e718040dc0a739c1e1fcbb37c64 pg-linux-x64
5
+ a5ed42cc2708f62ea067aadf05eca04035cc32df1849d3d2e89a1bca53b388e6 pg-windows-arm64.exe
6
+ e28cc72aea793b6b87063c36eb352882f0147323705ba19052f3910f9c42f5e8 pg-windows-x64.exe
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "paragma",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "Project memory for AI coding agents: rules, decisions, past errors with their fixes, and handoffs between conversations, found by hybrid search.",
5
5
  "keywords": [
6
6
  "ai",