pluribus-context v0.3.52 — context sync effective-load demo

A distribution release for the new browser-only 30-second context sync demo.

• Edit one canonical rule and preview CLAUDE.md, AGENTS.md, or .cursorrules.
• Inspect source/output hashes without uploading content.
• Run an effective-load A/B that distinguishes configured_but_ignored from loaded_and_task_outcome_accepted.
• Report the exact source edit and target tried.

Try the demo: https://caioribeiroclw-pixel.github.io/pluribus/context-sync-demo.html

Pinned CLI smoke (npm latest is still v0.3.46):

npm exec --yes --package github:caioribeiroclw-pixel/pluribus#v0.3.52 -- pluribus --version

pluribus-context v0.3.51

Try the core workflow first

Open the 30-second browser demo: edit one canonical rule, preview native CLAUDE.md, AGENTS.md, or .cursorrules output, and inspect a privacy-safe source/output receipt. Nothing is uploaded or written, and runtime load remains explicitly unknown.

v0.3.51

Adapter expansion release, driven by an external contribution from AZERDSQ131.

Added

• Cline adapter: .clinerules
• Roo Code adapter: .roo/rules/pluribus.md
• Amazon Q Developer adapter: .amazonq/rules/pluribus.md
• JetBrains Junie adapter: .junie/AGENTS.md
• Warp adapter: WARP.md
• Gemini CLI adapter: GEMINI.md

Verification

• npm run release:verify passed on 3aaa99d.
• GitHub Actions CI passed on 3aaa99d.
• Pages deployment passed on 3aaa99d.

npm status

npm publish for pluribus-context@0.3.51 was attempted with the private publish-token runbook and failed with registry/auth-style E404 during npm publish. Until npm auth/token rotation is completed, install directly from GitHub:

npm exec --yes --package github:caioribeiroclw-pixel/pluribus#v0.3.51 -- pluribus help

pluribus-context v0.3.50

Highlights

• Fixes sync --source and audit --source so generated files and comparisons are anchored to the source context directory instead of the shell current working directory. This preserves project-local authority in nested repos and monorepos.
• Includes the recent public receipt artifacts: archived agent chat recovery card, config treatment receipts, agent change manifest, evidence-attestation Skill, and related examples/checkers.

Thanks @fengjikui for the external bug-fix PR that drove this patch release.

Verification

• npm test — 93/93 passing
• git diff --check
• npm pack --dry-run
• npm run release:verify

Install from source tag

Until npm latest is advanced, use the immutable GitHub tag for this patch:

npm exec --yes --package github:caioribeiroclw-pixel/pluribus#v0.3.50 -- pluribus --version

v0.3.49

Pluribus 0.3.49

This release packages the current boundary-receipt work for GitHub/npm tarball users while npm latest waits for token rotation.

Highlights:

• public boundary receipt gallery for reviewers and cold visitors: https://caioribeiroclw-pixel.github.io/pluribus/boundary-receipt-gallery.html
• context-boundary receipt taxonomy docs covering MCP action preflight, memory/RAG authority, rendered-output provenance, context-input evidence, stale-rule authority, tool identity mapping, and instruction load-boundary safety
• pluribus demo cross-client-token-ledger
• package metadata now points homepage/discovery at the gallery and project-memory lane

Validation:

• npm run release:verify passed
• npm test passed: 79/79
• npm pack --dry-run includes the gallery and latest boundary examples

Note: npm pluribus-context@latest is still 0.3.46 until the npm publish token is rotated/revalidated. Install from the GitHub tag if you need this exact snapshot before the npm catch-up.

v0.3.48 — shared-state write preflight

Shared-state write preflight

This release makes the shared-state write preflight demo stable from a GitHub tag.

Try it directly:

npx -y --package github:caioribeiroclw-pixel/pluribus#v0.3.48 pluribus demo shared-state-write-preflight --json

Expected result: ok: true with a pre-write receipt for an agent-writable/shared MCP database update. The receipt proves actor/client scope, target store/workspace, collection and operation, authorization policy decision, idempotency/concurrency controls, prompt-injection/secret/migration/trigger controls, redacted field shapes, source refs, omitted private fields, and the audit event expected after the write.

Why this exists

Shared state tools are moving from agent-readable memory toward agent-writable systems of record. Attribution/event logs after mutation are useful, but too late for over-broad writes or prompt-injected changes. The useful boundary is a small preflight before durable mutation.

Added

• pluribus demo shared-state-write-preflight
• Packaged fixture: examples/shared-state-write-preflight/shared-state-write-preflight-receipt.json
• Docs: docs/shared-state-write-preflight.md
• Changelog/version bump to 0.3.48

Verification

• npm test: 73/73 passing
• git diff --check: clean
• npm run release:verify: passed

Distribution note

The npm package has not moved yet: pluribus-context latest is still 0.3.46. The saved npm publish token is expired/invalid and needs rotation before the next npm publish, so use the GitHub tag install command above for this release.

v0.3.47 — company memory export test

Company memory export test

This release adds a runnable demo for testing whether operational/company memory can move between agents or vendors without depending on hidden model memory or private chat history.

Try it directly from the GitHub tag:

npx -y --package github:caioribeiroclw-pixel/pluribus#v0.3.47 pluribus demo company-memory-export-test --json

Expected result: ok: true with a review-required export receipt that includes decisions, active constraints, exceptions, owners, source freshness, stale sources, and explicit omitted gaps.

Why this exists

Claude Tag, self-authored skills, MCP memory servers, and company-agent workflows are making persistent operational memory a real lock-in surface. The useful export test is intentionally boring: can another vendor/agent reconstruct enough from a neutral receipt to continue safely, while still seeing what was not exported?

Added

• pluribus demo company-memory-export-test
• Packaged fixture: examples/company-memory-export-test/company-memory-export-receipt.json
• Docs: docs/company-memory-export-test.md
• Tests and CLI wiring for the demo command

Verification

• npm test: 71/71 passing
• git diff --check: clean
• GitHub-tag smoke passed with the command above

Distribution note

The npm package has not moved yet: pluribus-context latest is still 0.3.46. Use the GitHub tag install command above for this release until npm publishing is repaired.

v0.3.46

Adds pluribus demo context-budget-receipt, a tiny npm-runnable demo for measuring what entered context, what was suppressed as duplicate/stale/deferred, how much tool-schema budget loaded, and whether sources reloaded after /clear or compaction without logging raw prompts, paths, memory, or schemas.

v0.3.45

Adds pluribus demo style-rules-sync, a tiny npm-runnable demo for turning one canonical pluribus.md style-rules file into Claude Code, Cursor, Copilot, and OpenClaw target files without copy-paste drift.\n\nSmoke:\n- npm test\n- npm run release:verify\n- pluribus demo style-rules-sync\n- pluribus demo style-rules-sync --json

pluribus-context v0.3.44

Adds pluribus demo instruction-context-audit, a tiny npm-runnable receipt demo for hashing active AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions, and Skills while flagging stale, dirty, external, or unreviewed instruction authority surfaces before an agent writes.\n\nSmoke:\n- npm test (65/65)\n- npm run release:verify\n- npm view pluribus-context version => 0.3.44\n- fresh-cache npm exec --package pluribus-context@0.3.44 -- pluribus demo instruction-context-audit --json

v0.3.42

Adds an npm-runnable context sufficiency trace demo for testing whether a compressed context bundle preserved task-required files before editing begins.\n\nTry:\n\nbash\nnpx --yes pluribus-context@latest demo context-sufficiency-trace --pass --json\n\n\nThe default bundled trace intentionally fails to show the missed required file case.