pluribus-context 0.3.7 → 0.3.9

package/CHANGELOG.md

@@ -4,6 +4,23 @@
 
 All notable changes to Pluribus are documented here.
 
+## 0.3.9 — npm discovery metadata refresh
+
+### Added
+
+- Add exact npm discovery keywords for adjacent searches such as `context-sync`, `claude-md`, `ai-rules`, `rules-sync`, `context-files`, and `ai-agents`.
+- Add a release-verification guard for the community review packet so directory submission fields, safe first command, privacy guardrails, uninstall/network copy, and the <=280-character blurb cannot silently drift before distribution pushes.
+
+### Changed
+
+- Refresh the context-drift audit example with current published-package commands and generated fixtures so reviewers can reproduce the intended one-file drift signal from `pluribus-context@latest`.
+
+## 0.3.8 — package-page directory field visibility
+
+### Changed
+
+- Make the README/npm package page explicitly mention the community review packet's directory submission fields, so curators can find the structured listing copy without opening the packet first.
+
 ## 0.3.7 — directory submission packet refresh
 
 ### Added

package/README.md

@@ -148,7 +148,7 @@ npx --yes pluribus-context@latest sync --dry-run
 
 If the preview looks right, run `npx --yes pluribus-context@latest sync` to write the tool-specific files.
 
-For a fuller walkthrough, see the [Quickstart](docs/quickstart.md). To enforce generated context files in pull requests, use the [CI audit example](docs/ci-audit-example.md); to catch drift before commits leave your machine, use the [Pre-commit Audit Hook](docs/pre-commit-audit.md). If your repo already has `CLAUDE.md`, `.cursorrules`, Copilot instructions, or `AGENTS.md`, run a [Context Drift Audit](docs/context-drift-audit.md) first, try the intentionally drifted [audit example](examples/context-drift-audit/), then follow [Migrate Existing AI Context Files](docs/migrate-existing-context.md). Before committing shared or generated AI instructions, use the [Context File Review Checklist](docs/context-file-review.md). If you're deciding between Pluribus and a one-way rules converter, see [When to use Pluribus](docs/when-to-use-pluribus.md). If you are debugging "context drift" after compaction or long sessions, start with the [Context Drift Taxonomy](docs/context-drift-taxonomy.md) to separate file drift from runtime precedence drift. If you are reviewing Pluribus for a list, newsletter, or tool directory, use the [Community Review Packet](docs/community-review-packet.md) for a one-line description, safety notes, and a disposable 60-second smoke test.
+For a fuller walkthrough, see the [Quickstart](docs/quickstart.md). To enforce generated context files in pull requests, use the [CI audit example](docs/ci-audit-example.md); to catch drift before commits leave your machine, use the [Pre-commit Audit Hook](docs/pre-commit-audit.md). If your repo already has `CLAUDE.md`, `.cursorrules`, Copilot instructions, or `AGENTS.md`, run a [Context Drift Audit](docs/context-drift-audit.md) first, try the intentionally drifted [audit example](examples/context-drift-audit/), then follow [Migrate Existing AI Context Files](docs/migrate-existing-context.md). Before committing shared or generated AI instructions, use the [Context File Review Checklist](docs/context-file-review.md). If you're deciding between Pluribus and a one-way rules converter, see [When to use Pluribus](docs/when-to-use-pluribus.md). If you are debugging "context drift" after compaction or long sessions, start with the [Context Drift Taxonomy](docs/context-drift-taxonomy.md) to separate file drift from runtime precedence drift. If you are reviewing Pluribus for a list, newsletter, or tool directory, use the [Community Review Packet](docs/community-review-packet.md) for directory submission fields, a one-line description, safety notes, and a disposable 60-second smoke test.
 
 ### Usage
 

package/docs/community-review-packet.md

@@ -79,7 +79,7 @@ Expected result:
 
 ## Feedback requested
 
-If you try it on a real repo, please avoid pasting private context or full audit JSON from non-public projects. The most useful report is:
+If you try it on a real repo, please do not paste secrets, private source code, credentials, customer data, or internal instructions that should not be public. Avoid pasting private context or full audit JSON from non-public projects. The most useful report is:
 
 1. OS/shell and exact Pluribus version.
 2. Which context files already existed (`CLAUDE.md`, `.cursorrules`, Copilot instructions, `AGENTS.md`, etc.).

package/examples/context-drift-audit/.cursorrules

@@ -1,4 +1,4 @@
-# Cursor Rules — generated by Pluribus 0.3.3 on 2026-05-13
+# Cursor Rules — generated by Pluribus 0.3.8 on 2026-05-15
 # Source: pluribus.md
 # Do not edit manually.
 

package/examples/context-drift-audit/.github/copilot-instructions.md

@@ -1,4 +1,4 @@
-<!-- Generated by Pluribus 0.3.3 on 2026-05-13 — do not edit manually -->
+<!-- Generated by Pluribus 0.3.8 on 2026-05-15 — do not edit manually -->
 <!-- Source: pluribus.md -->
 
 

package/examples/context-drift-audit/CLAUDE.md

@@ -1,4 +1,4 @@
-<!-- Generated by Pluribus 0.3.3 on 2026-05-13 — do not edit manually -->
+<!-- Generated by Pluribus 0.3.8 on 2026-05-15 — do not edit manually -->
 <!-- Source: pluribus.md -->
 
 # Project Context for Claude

package/examples/context-drift-audit/README.md

@@ -4,10 +4,10 @@ This fixture shows the safest first Pluribus workflow for an existing repo: audi
 
 `pluribus.md` is the source of truth. `CLAUDE.md` is intentionally drifted: it says `Node.js 20 LTS` while `pluribus.md` says `Node.js 22 LTS`. Cursor and Copilot outputs are current.
 
-Run from this directory:
+Run from this directory with the published package:
 
 ```bash
-npx --yes --package ../.. pluribus audit --strict
+npx --yes pluribus-context@latest audit --strict
 ```
 
 Expected result:
@@ -21,11 +21,11 @@ Expected result:
 Preview the fix without writing files:
 
 ```bash
-npx --yes --package ../.. pluribus sync --dry-run
+npx --yes pluribus-context@latest sync --dry-run
 ```
 
 Then apply it when the diff is acceptable:
 
 ```bash
-npx --yes --package ../.. pluribus sync
+npx --yes pluribus-context@latest sync
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pluribus-context",
-  "version": "0.3.7",
+  "version": "0.3.9",
   "description": "Sync intentional AI context and rules across Claude Code, Cursor, Copilot, OpenClaw, Windsurf, Continue, and Zed.",
   "type": "module",
   "homepage": "https://github.com/caioribeiroclw-pixel/pluribus#readme",
@@ -37,17 +37,22 @@
     "agents",
     "agents-md",
     "ai",
+    "ai-agents",
     "ai-coding-agents",
     "ai-context",
+    "ai-rules",
     "ai-tools",
     "aider",
     "claude",
     "claude-code",
+    "claude-md",
     "cli",
     "codex",
     "context",
     "context-drift",
     "context-engineering",
+    "context-files",
+    "context-sync",
     "continue",
     "copilot",
     "cursor",
@@ -56,6 +61,7 @@
     "drift-detection",
     "openclaw",
     "rules",
+    "rules-sync",
     "windsurf",
     "zed"
   ],

package/src/utils/version.js

@@ -1 +1 @@
-export const VERSION = '0.3.7'
+export const VERSION = '0.3.9'