ci: add Codex CLI plugin manifest

[internet-dot]

This adds a small metadata pass so the repo is easier to wire into Codex without touching runtime code.

I targeted this repo because it already exposes:

It adds .codex-plugin/plugin.json, a starter .mcp.json, and the scanner workflow.
Permissions: read-only. No secrets. No publish. No runtime changes.
If you want different command wiring or metadata values, I can adjust the branch.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[gitar-bot]

⚠️ Bug: plugin.json references non-existent .mcp.json file

The mcpServers field in plugin.json (line 15) points to ./.mcp.json, but this file does not exist anywhere in the repository. The Codex plugin scanner CI job will either fail or produce misleading results when it tries to resolve this reference.

Either add the .mcp.json file to the repository, or remove the mcpServers field from plugin.json until MCP server configuration is ready.

_{Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion}

[gitar-bot]

💡 Quality: plugin.json description is truncated mid-word

The description field (line 4) ends with "...seamless team colla" — it appears to be cut off mid-word (should be "collaboration"). This truncated text will appear in any plugin registry or listing that consumes this manifest.

Suggested fix:

"description": "OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration."

_{Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion}

[gitar-bot]

💡 Quality: plugin.json missing trailing newline

The file ends without a newline character (the diff shows \ No newline at end of file). Most linting tools and POSIX conventions expect a trailing newline.

_{Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion}

[gitar-bot]

Code Review ⚠️ Changes requested 0 resolved / 3 findings

Adds Codex CLI plugin manifest and scanner CI, but plugin.json references a non-existent .mcp.json file and the description field is truncated mid-word. Also missing a trailing newline.

⚠️ Bug: plugin.json references non-existent .mcp.json file

📄 .codex-plugin/plugin.json:15

The mcpServers field in plugin.json (line 15) points to ./.mcp.json, but this file does not exist anywhere in the repository. The Codex plugin scanner CI job will either fail or produce misleading results when it tries to resolve this reference.

Either add the .mcp.json file to the repository, or remove the mcpServers field from plugin.json until MCP server configuration is ready.

💡 Quality: plugin.json description is truncated mid-word

📄 .codex-plugin/plugin.json:4

The description field (line 4) ends with "...seamless team colla" — it appears to be cut off mid-word (should be "collaboration"). This truncated text will appear in any plugin registry or listing that consumes this manifest.

Suggested fix

"description": "OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration."

💡 Quality: plugin.json missing trailing newline

📄 .codex-plugin/plugin.json:16

The file ends without a newline character (the diff shows \ No newline at end of file). Most linting tools and POSIX conventions expect a trailing newline.

🤖 Prompt for agents

Code Review: Adds Codex CLI plugin manifest and scanner CI, but plugin.json references a non-existent .mcp.json file and the description field is truncated mid-word. Also missing a trailing newline.

1. ⚠️ Bug: plugin.json references non-existent .mcp.json file
   Files: .codex-plugin/plugin.json:15

   The `mcpServers` field in `plugin.json` (line 15) points to `./.mcp.json`, but this file does not exist anywhere in the repository. The Codex plugin scanner CI job will either fail or produce misleading results when it tries to resolve this reference.
   
   Either add the `.mcp.json` file to the repository, or remove the `mcpServers` field from `plugin.json` until MCP server configuration is ready.

2. 💡 Quality: plugin.json description is truncated mid-word
   Files: .codex-plugin/plugin.json:4

   The `description` field (line 4) ends with `"...seamless team colla"` — it appears to be cut off mid-word (should be "collaboration"). This truncated text will appear in any plugin registry or listing that consumes this manifest.

   Suggested fix:
   "description": "OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration."

3. 💡 Quality: plugin.json missing trailing newline
   Files: .codex-plugin/plugin.json:16

   The file ends without a newline character (the diff shows `\ No newline at end of file`). Most linting tools and POSIX conventions expect a trailing newline.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}