Initial public release.
Added
- MCP server (
dist/server.js, wired via.mcp.json) and CLI (ovb3) exposing the same tools through both interfaces. - Artifact read/write for VB Studio git-based project checkouts — pages, flows, chains, service (
openapi3.json) definitions — across a whole VBS instance (VBS_WORKSPACE_DIRholds multiple project repos, each repo can hold multiple VBCS web apps underwebApps/). - Git helpers: status, commit, pull, push, clone against a VB Studio-backed git remote.
- Build/audit wrapper shelling out to Oracle's
grunt-vb-build/grunt-vb-audittasks. - Standalone VBCS instance support (VBCS apps with no VB Studio project behind them): list applications, lock/unlock, export business-object data, against a real REST API confirmed live.
ovb3 init— interactive CLI setup wizard for linking a VB Studio project or a standalone VBCS instance./link— the Claude Code slash-command equivalent ofovb3 init./vbs-*slash commands (git-based VB Studio tools) and/vbcs-*slash commands (standalone VBCS REST tools), each with a self-documenting-helpcommand.- MIT license.
Known limitations
- VB Studio's own REST API (CI/CD build/deploy, environment management — a separate product/integration from standalone VBCS) is stubbed, not implemented — no live VB Studio instance access has been confirmed for it yet.
importBusinessObjectData(standalone VBCS) is stubbed — Oracle's docs don't publish the request body/content-type for that endpoint.grunt-vb-build/grunt-vb-audittask flags are unconfirmed against a real Gruntfile.
Full changelog: https://github.com/vanamthrishul/ovb3-bridge/blob/master/CHANGELOG.md