pluribus-context 0.3.6 → 0.3.8

package/CHANGELOG.md

@@ -4,6 +4,18 @@
 
 All notable changes to Pluribus are documented here.
 
+## 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
+
+- Add structured directory-submission fields to the community review packet so small distribution/review forms can reuse one safe, consistent Pluribus listing without rewriting install or safety copy.
+
 ## 0.3.6 — community review packet package-page 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

@@ -14,6 +14,21 @@ Pluribus is an open-source CLI for teams and solo developers who use multiple AI
 npx --yes pluribus-context@latest audit
 ```
 
+## Directory submission fields
+
+Use these fields for directories, awesome lists, or review forms that ask for a concise tool entry. Prefer this over inventing new copy per channel.
+
+| Field | Copy |
+| --- | --- |
+| Name | Pluribus |
+| URL | https://github.com/caioribeiroclw-pixel/pluribus |
+| npm | https://www.npmjs.com/package/pluribus-context |
+| Category | AI coding tools / context management |
+| Tags | `claude-code`, `cursor`, `copilot`, `openclaw`, `windsurf`, `continue`, `zed`, `context-drift` |
+| One sentence | Keep one versioned AI coding context in `pluribus.md`, then audit or sync the generated files used by Claude Code, Cursor, Copilot, OpenClaw, Windsurf, Continue, and Zed. |
+| 280-char blurb | Pluribus is an open-source CLI for intentional AI coding context. It keeps project guidance in one `pluribus.md`, then audits or syncs `CLAUDE.md`, Cursor rules, Copilot instructions, `AGENTS.md`, Windsurf/Continue rules, and Zed rules. |
+| Safe first command | `npx --yes pluribus-context@latest audit` |
+
 ## Why it may be useful
 
 - Reduces copy-paste drift between AI tool instruction files.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pluribus-context",
-  "version": "0.3.6",
+  "version": "0.3.8",
   "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",

package/src/utils/version.js

@@ -1 +1 @@
-export const VERSION = '0.3.6'
+export const VERSION = '0.3.8'