v0.7.2-beta

Changed

• remagraph init without --project now derives the project name from the current project folder instead of silently falling back to default (field feedback: running a bare remagraph init inside a freshly cloned repo created a default project that the post-commit hook and prompt-hook could never match). The derivation mirrors the hook's rules exactly — inside a git repo it uses the repo root directory name (worktree-safe, so running from a subdirectory still resolves correctly), otherwise the current directory name, slugified with the same slugify the write side (post-commit hook) and read side (prompt-hook) already share. An explicit --project still wins, and the output states the auto-derived name with a hint to override.

v0.7.1-beta

Fixed

• doctor no longer prints the "using the default shared state dir" warning when run in a shared-state-dir context (field feedback from a downstream project on 0.7.0 launch day). The top-level guard warning carries no actionable meaning for a read-only health check — doctor's own state_dir check surface already covers state-dir health — and it polluted stderr for --json pipeline consumers. Covered by a regression test asserting doctor's stderr stays clean.

v0.7.0-beta

Scope agreed through a two-round external architecture review (all five items unanimously approved on round two), implemented TDD-first, then adversarially reviewed by two independent agents whose 12 findings were all fixed before this release. Test suite: 565 → 613.

Added

• remagraph doctor — read-only health check. Six check surfaces: CLI version vs PyPI (3s timeout; offline/5xx → skip), post-commit hook (managed marker, fields-schema-version, execute bit — skipped on Windows), conventional state dir & project.json identity, registry health (current project by default; --all-projects scans the full local registry for poisoned entries, capped at 50 shown with total_count/truncated), stray records in the shared default DB (with the exact migrate-project recovery command), and database status (openability, three-tier schema compatibility, WAL mode read from the file header, stale -wal/-shm detection that never false-positives on an actively used database). Strictly read-only — hardened by adversarial review: all SQLite access is mode=ro&immutable=1 + query_only, and the registry is read directly rather than through the auto-creating internal API, so doctor can never create a database, a directory, or a side file; a filesystem-snapshot test enforces this. Output: human text or --json (schema_version 1, append-only); exit 0=ok, 1=fail, 2=warn (remagraph-specific semantics).
• Release process documentation (docs/release-process.md): doctor as the opening go/no-go gate, the whole-codebase diagnostic + adversarial review methodology from the 0.6.x cycle, and the real-environment verification principle. DESIGN.md gains a section documenting that memory ids are a per-database daily sequence (not globally unique), with the cross-database reference boundaries and migrate re-numbering behavior.

Changed

• Concurrent store handling: connections now set a fixed 150ms SQLite busy timeout at creation (previously the 5s default), and process_store retries BEGIN IMMEDIATE up to 3 times with exponential backoff (0.1/0.2/0.4s ± 50ms jitter) on lock contention — worst-case budget ≈1.45s, bounded and documented. The cross-project migration path uses the same retry (its lock tolerance would otherwise have shrunk 33×). Retry exhaustion still returns a structured error (retried 3 times in the detail). The never-raised MemoryIDGenerationError class was removed.
• Mutation testing restored and expanded: mutmut scope grows from 2 to 6 modules (store, search, prompt_hook, audit added; db/maintenance/hooks_installer documented as 0.8.0 debt), weekly CI runs with --use-coverage (with an explicit .coverage presence guard — a missing file silently yields zero mutants), and a per-module surviving-mutant baseline with delta annotations; a failed run can no longer silently wipe the baseline, and zero-survivor modules stay pinned at 0 so later regressions are caught.
• GitHub Release notes are now extracted from the matching CHANGELOG section (with a visible warning and automatic fallback to generated notes if the section is missing or empty — and a parser that stops at the bilingual section boundary).

Fixed

• Removed the dead invalidates_not_active literal left over from the 0.6.x review cycle.

v0.6.4-beta

Full Changelog: v0.6.3-beta...v0.6.4-beta

v0.6.3-beta

Full Changelog: v0.6.2-beta...v0.6.3-beta

v0.6.2-beta

Full Changelog: v0.6.1-beta...v0.6.2-beta

v0.6.1-beta

Full Changelog: v0.6.0-beta...v0.6.1-beta

v0.6.0-beta

Full Changelog: v0.5.0-beta...v0.6.0-beta

v0.5.0-beta

Full Changelog: v0.4.0-beta...v0.5.0-beta

v0.4.0-beta — First Public Release

RemaGraph enters beta — and goes public for the first time

RemaGraph is a lightweight MCP (Model Context Protocol) tool that captures the trail an AI coding agent leaves behind while working — task handoffs, status updates, discovered constraints — so the next agent (or the same one, later) can pick up where it left off.

This release marks two things at once:

• First time this repository is public. Until now RemaGraph only ran internally inside Herdr Bridge.
• Alpha → beta. This is not a 1.0 release — per BOUNDARIES.md, RemaGraph is still pre-1.0 with no frozen public API. "Beta" means the feature set has stabilized enough for wider use, not that MCP tool parameters or CLI subcommands are locked yet.

What changed this cycle

• Filled in missing documentation for all 5 MCP tools in README/DESIGN (some had gaps in parameter tables and response fields).
• remagraph_migrate_project was a stub that didn't actually migrate anything — it now performs a real migration, sharing the same core implementation as the CLI's migrate-project subcommand, with a follow-up fix for a per-record atomicity edge case.
• All user-facing runtime strings (CLI, MCP tool responses, safety-valve errors, example scripts) now default to English; bilingual (English + Traditional Chinese) formatting is reserved for project documentation.
• A full pre-publication review pass across all docs caught and fixed 28 issues, including stale version numbers, an undocumented tool-count mismatch, and personal machine-specific paths that had no business shipping publicly.
• Adopted REUSE/SPDX licensing metadata and added governance documentation (GOVERNANCE.md, MAINTAINERS.md, BOUNDARIES.md, RELEASE.md, ADOPTERS.md).

See CHANGELOG.md for the full history.

Installing

The PyPI package is not published yet. Install via the git tag:

uv tool install git+https://github.com/aiken884/RemaGraph.git@v0.4.0-beta

License

Apache-2.0

Full Changelog: v0.2.0-alpha...v0.4.0-beta