Repository navigation
chore: promote the runtime surface at 1.0.12 - #14
Merged
Merged
Conversation
The 1.0.12 surface adds mcp_config.json, kimi.plugin.json, .antigravity-plugin/plugin.json and rules/deriv-api-conventions.md, which the previous checker rejects as outside the allowlist. The checker now allows those paths, requires the two new MCP declarations and the Antigravity manifest, pins both declarations to the hosted MCP URL, rejects mcpServers on the Antigravity manifest, and holds the Kimi and Antigravity manifests in version lockstep. A malformed manifest is now reported once, under its own host's label. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
sparsh-deriv
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR promotes the runtime surface from the private working repo by copying files in. It was raised after a human approved the reviewed manifest (publication gate 2).
build-promotion-bundle.mjsbuilds the tree from the allowlist into an empty directory, so a path that is not on the allowlist never reaches the build. Every file in this branch is byte-identical to its source: 121 allowlisted paths and 4.github/scaffold files.Version 1.0.10 → 1.0.12, lockstep across all six manifests. 1.0.11 was never released on its own, so its changes ship here.
What changes
mcp_config.json(new): the Antigravity MCP declaration, withmcpServers.deriv.serverUrlset tohttps://mcp-api-v2.deriv.com/mcp..antigravity-plugin/plugin.json(new): the Antigravity manifest, with:displayNameDeriv;logo./assets/logo.png;suggestedPrompts;rules/deriv-api-conventions.md(new): the conventions rule for Antigravity, withtrigger: always_onfrontmatter. Its body is identical torules/deriv-api-conventions.mdc.kimi.plugin.json(new): the Kimi manifest, with:interfacelisting fields;skills./skills/;systemPromptholding the rule body without its frontmatter;mcpServers.deriv{url}, because Kimi has no MCP file discovery.README.md: new Antigravity and Kimi install sections, and the MCP section names the two new declarations.SECURITY.md: two wording fixes. The server "is declared" at the plugin root instead of "its URL is declared". Only OpenAI, not Codex, discovers the rootmcp.json..codex-plugin/plugin.json: theauthorizenegative review case now says the Deriv API reference has noauthorizeendpoint or request schema. This change is from 1.0.11.versionis 1.0.12, and the Claude Code and Codex cataloguesource.refmove tov1.0.12. Cursor keepssource: "./".PRIVACY.md,.mcp.json,mcp.json, the bundled skills,rules/deriv-api-conventions.mdc, and the assets.Surface checker
The first commit updates
.github/workflows/verify-surface.mjs. The previous version rejects the four new paths asunexpected path outside the allowlist, so the checker has to land with the surface. The new version:ALLOW;mcp_config.json,kimi.plugin.json, and.antigravity-plugin/plugin.jsonto be present;serverUrlinmcp_config.jsonandurlinkimi.plugin.jsonto the hosted MCP URL (MCP Antigravity pin,MCP Kimi pin);mcpServerson the Antigravity manifest, which would overridemcp_config.json;kimi.plugin.jsonand.antigravity-plugin/plugin.jsonin version lockstep;Because of that presence check, the new checker can't merge ahead of these files: on its own it would fail its CI with
required file missing.Manifest
125 paths = 121 allowlisted + 4 scaffold. 13 files change: 4 added, 9 modified, none deleted.
verify-surface.mjspasses locally on this branch:OK — 125 path(s). The hosted MCP build pin check (mcp-build-pin.mjs) printsOKagainst a captured productioninitialize(serverInfo.name: deriv-api).Before merge: Antigravity and Kimi acceptance
Neither host has been install-tested. Every shape here comes from the hosts' published docs. Run these checks against this branch, and record each result in a comment here before merging:
agy plugin validate --strictpasses.agy plugin install <path>shows:derivtools;skills/;Deriv, the logo, and the suggested prompts).Record which manifest Antigravity read: the root
plugin.jsonor.antigravity-plugin/plugin.json.In the Antigravity App and the Antigravity IDE, not only the
agyCLI, the installed plugin shows the hostedderivtools, every skill underskills/, and the conventions rule.Kimi Code CLI's
/plugins installshows thederivMCP server and the bundled skills, and a new session has the conventionssystemPromptloaded.Record whether Kimi strips YAML frontmatter from a
systemPromptPathfile. To check, point a scratch copy'ssystemPromptPathatrules/deriv-api-conventions.mdand see whether the session prompt shows itstrigger: always_onblock.On a Cursor-only machine, run
Developer: Reload Windowand confirm Cursor loads the conventions rule once as always-apply. Record whether the.mdcopy also appears.After merge
In the same session, create the annotated tag
v1.0.12on the merge commit and the GitHub Release, so both catalogue refs resolve.🤖 Generated with Claude Code