Vibecheck v1.0.1

Vibecheck 1.0.1

This release fixes historical actor attribution for rapid updates. In v1.0.0, a coordinator correcting another root session's work twice within one millisecond could be absent from the second event's captured session records. The event identified the actor, but could omit the actor's model and effort at that time.

Each new change batch now captures the reporting actor and its session ancestry independently of heartbeat timing. Unchanged sessions use context:true and retain their existing revision. Empty transactions create no event. Existing historical records remain unchanged.

Vibecheck remains a passive ledger with nine MCP tools, atomic plan and work updates, compact keyed status, historical plan comparisons, and shared SQLite storage. It runs directly as TypeScript with Bun or as compiled JavaScript with Node.js 24 or later. Both native plugins include the bundled JavaScript runtime and start without installing dependencies.

Install the patch through the Codex or Claude instructions. The release includes both plugin archives, the standalone runtime archive, and SHA256SUMS.

Verification covers 127 tests on Bun 1.3.14, Node.js 24.0.0, and Node.js 26.1.0, including 995 frozen Python validation cases. Both new actor-context regressions failed before the fix. Independent testing captured the actor in all 150 rapid corrections and confirmed that later model changes do not alter the captured historical identity. Both native plugins pass installation and MCP checks from read-only paths containing spaces.

Run bun install --frozen-lockfile and bun run verify for source checks. Run bun run build:release and bun run verify:release --native to rebuild and verify the archives and native plugin installations.

Vibecheck v1.0.0

Vibecheck 1.0.0

Vibecheck 1.0.0 implements the passive MCP work ledger in strict TypeScript. This repository is mgd34msu/vibecheck. The Python implementation is archived at mgd34msu/vibecheck-python.

The release scope includes:

• Nine tools for session registration, root-owned plans, atomic plan edits, historical definitions and diffs, acknowledgments, claims, updates, current status, and work history.
• Revision-checked ownership, nested delegation, explicit handoffs and recovery, full commit references, and persistent integration requirements.
• Compact keyed current status with a 64 KiB structured JSON budget, complete-map recovery, explicit counts, and full:true for all current records.
• Retained task lineage, earlier plan definitions, work attempts, and historical session attribution.
• Shared local SQLite storage through stdio and authenticated Streamable HTTP for remote clients.
• Native Codex and Claude Code plugins with a shared server and skill.

Bun 1.3.14 or later runs src/cli.ts directly. Node.js 24 or later runs the compiled dist/cli.js. The implementation uses schema-derived types and built-in SQLite adapters, without a Python runtime or build dependency.

Plugin bundles include runtime/vibecheck.mjs and start without installing dependencies. Their Bash launcher selects Bun when available, otherwise Node.js. VIBECHECK_RUNTIME=bun or VIBECHECK_RUNTIME=node overrides that choice.

bun run build:release generates vibecheck-codex-plugin-1.0.0.zip, vibecheck-claude-plugin-1.0.0.zip, vibecheck-runtime-1.0.0.tar.gz, and SHA256SUMS in artifacts/. bun run verify:release checks the archives and exercises their MCP servers with both runtimes.

The package is named @mgd34msu/vibecheck and is not published to the npm registry. Follow the README installation commands for native plugins, or run from source.

The default database remains $XDG_DATA_HOME/project-board/board.sqlite3, falling back to $HOME/.local/share/project-board/board.sqlite3. Existing PROJECT_BOARD_* configuration names remain unchanged. Keep ledger data outside plugin caches. Removing the plugin retains that external database.

All 125 tests pass on Bun 1.3.14, Node.js 24.0.0, and Node.js 26.1.0. Verification covers strict TypeScript, forbidden type escapes, bundled runtime freshness, 995 frozen Python validation cases, imported SQLite history and retry responses, concurrent Bun/Node writers, and real stdio and HTTP clients. Both native plugins pass installation and MCP checks from read-only directories and paths containing spaces.

Independent reviews found and confirmed fixes for recovery after an initial database-open failure, malformed HTTP Host ports, and JSON response compatibility with older MCP clients. Both 2025 and 2026 HTTP protocols return JSON. No outstanding findings remain in the reviewed core and transport.

Run bun install --frozen-lockfile and bun run verify to check the checkout. Run bun run build:release and bun run verify:release --native to rebuild and check the release assets. The optional native check requires the Codex and Claude Code CLIs, Bubblewrap, and the archive utilities on Linux.

The ledger records agent reports and references. It does not launch agents, schedule work, mutate Git, discover projects, scan repositories, create backups, or store conversations. The skill applies when selected or invoked and does not force registration through first-turn hooks.