Skip to content

Releases: xiaojiou176-open/OpenVibeCoding

OpenVibeCoding v0.1.0-alpha.3 - storefront sync baseline

08 Apr 05:48
4cdc0b5

Choose a tag to compare

CortexPilot v0.1.0-alpha.3 - storefront sync baseline

This file is the tracked source for the current published GitHub Release notes.

This release realigns the published prerelease with main@4cdc0b5 after the
adoption-router packaging work landed and the public storefront copy was
compressed into a stronger showcase shape.

Why this release matters

CortexPilot now presents a tighter public first screen without loosening the
truth boundary:

  • the public README and Pages landing source now sell one inspectable product
    loop instead of reading like a documentation directory
  • the release track catches back up to the current released main snapshot
  • the repo now pins the Node baseline through a root .nvmrc

What changed

  • added a root .nvmrc pinned to the same Node baseline used by the CI core
    image
  • added a new storefront showcase card at
    docs/assets/storefront/command-tower-showcase-card.svg
  • promoted the storyboard GIF into the first public landing story instead of
    leaving it buried in supplemental storefront assets
  • synced README, docs/index.html, DISTRIBUTION.md, docs/distribution/,
    and storefront runbooks around the current release baseline
  • kept the public boundary honest:
    • read-only MCP only
    • no hosted operator
    • no public Docker image
    • no public package release or marketplace listing claim

What to open first

  1. README.md
  2. docs/index.html
  3. DISTRIBUTION.md
  4. docs/distribution/index.html
  5. docs/use-cases/index.html

Current truthful boundary

  • the public repo and GitHub Pages site are official front doors
  • the shipped MCP surface is still read-only, stdio, and repo-local
  • starter kits and coding-agent bundles remain local-adoption material, not
    published marketplace listings
  • hosted operator service, write-capable MCP, Docker distribution, and
    registry submissions remain deferred

Historical note

  • v0.1.0-alpha.1 remains the first public prerelease baseline
  • v0.1.0-alpha.2 remains the earlier distribution-readiness baseline
  • this file is the current repo-side source for the latest published release
    notes

Verification

PYTHONDONTWRITEBYTECODE=1 bash scripts/run_readonly_mcp.sh </dev/null
npm run docs:check
bash scripts/check_repo_hygiene.sh
npm pack --json --dry-run ./packages/frontend-api-client
npm pack --json --dry-run ./packages/frontend-api-contract

OpenVibeCoding v0.1.0-alpha.2

08 Apr 02:07
14ec12b

Choose a tag to compare

Pre-release

CortexPilot v0.1.0-alpha.2 - distribution readiness baseline

This file is the tracked source for the current published GitHub Release notes.

This release aligns the latest published prerelease with the current released
main snapshot after the distribution-readiness closeout landed.

Why this release matters

CortexPilot is no longer only a truthful-ready public repo. With this release,
the public release/tag now catches up to the current distribution contract,
starter boundaries, package stance, and read-only MCP artifact story.

What changed

  • added a canonical repo-side distribution contract in DISTRIBUTION.md
  • added a public Pages mirror at docs/distribution/index.html
  • artifactized the shipped read-only MCP surface through
    configs/mcp_public_manifest.json
  • standardized the official MCP startup story around
    scripts/run_readonly_mcp.sh
  • tightened Codex / Claude Code / OpenClaw starter and bundle wording so local
    adoption materials are not misread as published listings
  • promoted @cortexpilot/frontend-api-client and
    @cortexpilot/frontend-api-contract to publish-ready-but-deferred package
    posture, while keeping @cortexpilot/frontend-shared workspace-only
  • synced README, Pages, release-truth wording, and storefront docs around the
    new latest published prerelease baseline

What to open first

  1. README.md
  2. DISTRIBUTION.md
  3. docs/distribution/index.html
  4. docs/mcp/index.html
  5. docs/builders/index.html

Current truthful boundary

  • the public repo and GitHub Pages site are official front doors
  • the shipped MCP surface is still read-only, stdio, and repo-local
  • starter kits and the coding-agent bundle remain local-adoption material, not
    published marketplace listings
  • hosted operator service, write-capable MCP, Docker distribution, and
    registry submissions remain deferred

Historical note

  • v0.1.0-alpha.1 remains the first public prerelease baseline
  • this file supersedes docs/releases/first-public-release-draft.md as the
    source for the latest published release notes

Verification

PYTHONDONTWRITEBYTECODE=1 bash scripts/run_readonly_mcp.sh </dev/null
npm run docs:check
bash scripts/check_repo_hygiene.sh
npm pack --json --dry-run ./packages/frontend-api-client
npm pack --json --dry-run ./packages/frontend-api-contract

OpenVibeCoding v0.1.0-alpha.1

06 Apr 20:38
7fbc491

Choose a tag to compare

Pre-release

CortexPilot v0.1.0-alpha.1 - first public release baseline

This file is the tracked source for the first public GitHub Release notes.

This release is the first public storefront baseline for CortexPilot.

Why this release matters

CortexPilot is not just an agent demo repository. It is a command tower for
Codex and Claude Code workflows with evidence, replay, Workflow Cases, and
operator visibility.

This release makes that story much clearer on the public surface.

What changed

  • rewrote the root README around the PM -> Command Tower -> Runs loop
  • added tracked storefront assets for hero art and social preview
  • added a Pages-ready landing source with title and description metadata
  • split the first-success quickstart from contributor onboarding
  • added release and storefront runbooks for future maintenance
  • clarified the repo-side proof contract for the first public release bundle
  • added a repo-local read-only MCP server entry for control-plane reads
  • added an explain-only operator brief on dashboard Run Detail and Run Compare
  • added dedicated public Pages entrypoints for ecosystem, builder, use-case, and AI/MCP/API discovery

What to look at first

  1. README.md
  2. docs/index.html
  3. docs/runbooks/public-release-checklist.md
  4. docs/runbooks/storefront-share-kit.md

Official First Public Path

The first public release contract treats news_digest as the only official
happy-path baseline for proof-oriented copy and future benchmark publication.

Present Repo-Side Proof

  • release notes source exists in this file
  • README and storefront docs exist and are aligned to the current public story
  • tracked explainer assets and limited-scope captures exist in
    docs/assets/storefront/
  • a tracked healthy news_digest proof summary now exists in
    docs/releases/assets/news-digest-healthy-proof-2026-03-27.md
  • a tracked single-run public baseline now exists in
    docs/releases/assets/news-digest-benchmark-summary-2026-03-27.md
  • repo-side Prompt 4 now also includes read-only MCP and operator-brief docs in
    docs/architecture/mcp-and-operator-copilot-v1.md

Live Publication Checks Still Require Fresh Verification

  • confirm the GitHub social preview in repository settings before calling the
    release live-public complete
  • verify the current GitHub Release page at
    https://github.com/xiaojiou176-open/CortexPilot-public/releases/tag/v0.1.0-alpha.1
    still matches this repo-side draft instead of assuming it does
  • verify the live GitHub Pages site at
    https://xiaojiou176-open.github.io/CortexPilot-public/ is serving the
    current landing copy instead of inferring that from git alone
  • verify whether GitHub Discussions, release visibility, and subscriber flows
    are currently enabled in the live repository settings
  • keep the “no broader multi-round benchmark artifact is published yet” note as
    a release-time check until a fresh live/public proof bundle says otherwise

Verification

CORTEXPILOT_HOST_COMPAT=1 bash scripts/test_quick.sh --no-related
TMPDIR=/path/to/tmpdir bash scripts/check_repo_hygiene.sh

Release Note Guardrails

  • do not describe storyboard assets as healthy proof
  • do not describe degraded local captures as healthy end-to-end evidence
  • do not quote benchmark numbers outside the tracked artifact or without keeping
    the current single-run scope explicit
  • do not turn last-known live repository settings into repo-side current truth;
    live/public checks must be re-verified at release time