Add plugin-octav to registry

[wpoulin]

Registry todo

• add to index.json - alphabetical order

repo todo

• Images/brand (logo + banner)
• main is the default branch

Summary by CodeRabbit

• New Features

  • Added the Octav plugin to the public plugin index, enabling easy discovery and installation through the standard plugin mechanism.
  • Users can now reference “plugin-octav” alongside existing plugins without additional configuration.

• Chores

  • Minor index formatting adjustments to accommodate the new entry with no impact on functionality.

[coderabbitai]

Walkthrough

Added a new export mapping entry "plugin-octav": "github:wpoulin/plugin-octav" to the root index.json; the existing "plugin-connections" entry remains and was left with a trailing comma to accommodate the addition.

Changes

Cohort / File(s)	Summary
Export map update index.json	Added public mapping entry "plugin-octav": "github:wpoulin/plugin-octav"; retained "plugin-connections" value and adjusted trailing comma to allow the new entry.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I twitch my nose at maps that grow,
A tiny key in JSON's row—
plugin-octav hops into place,
A trailing comma saves the space.
Thump-thump, I nibble, then I cheer.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 3c9f129 and 1f52b8d.

📒 Files selected for processing (1)

• index.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• index.json

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description provides a short "Registry todo" and "repo todo" checklist with two items checked, but it does not fully follow the repository's required Registry Update Checklist. Key required confirmations are missing, including explicit verification that the index.json key matches the intended NPM-style package name, that the entry uses the exact "github:owner/repo" format (no github.com or .git), that the JSON commas were validated, and that the plugin repository is publicly accessible, includes the elizaos-plugins topic, exposes a package.json with the required agentConfig, and follows the prescribed file/image conventions with alt text and size constraints. Because multiple required checklist items and evidentiary details are absent, the description is insufficient to approve the change.	Please update the PR description to fully complete the Registry Update Checklist: state the exact index.json entry (show the key and value using "github:owner/repo"), confirm alphabetical placement and that the JSON is valid, and confirm the left-side name matches the intended NPM package name. Also explicitly confirm the plugin repo is public, that "main" is the default branch (if different state it), that the repo topics include "elizaos-plugins" (and AI/crypto if relevant), provide the package.json agentConfig snippet or a link to package.json, and list image filenames with alt text and approximate file sizes. After those details are added I will re-evaluate the description and confirm whether the check can pass.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Add plugin-octav to registry" succinctly and accurately reflects the primary change in this PR — adding the plugin-octav entry to the registry — and is concise, specific, and free of extraneous information. It clearly communicates the main intent for a reviewer scanning the history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.