v0.3.2

@evidoc/repo@0.3.2 release:notes
node scripts/release-notes.mjs

Evidoc 0.3.2 - 2026-07-11

• Added conventional evidoc --version and evidoc -v output backed by the shared runtime version.
• Hardened Trusted Publishing recovery against npm registry propagation races after a publish response fails.
• Made GitHub Release assets byte-identical to npm by downloading and integrity-checking the published registry tarballs before attachment.

Evidoc 0.3.1

@evidoc/repo@0.3.1 release:notes
node scripts/release-notes.mjs

Evidoc 0.3.1 - 2026-07-11

• Replaced the registry-blocked unscoped launcher with the umbrella package @evidoc/evidoc, while keeping the installed executable named evidoc and @evidoc/cli as an implementation module.
• Updated generated commands, onboarding, reports, MCP guidance, Local App copy, GitHub Action feedback, release verification, and tarball smoke tests to use npx @evidoc/evidoc as one shared public entrypoint.
• Bumped the lockstep workspace release because npm package versions are immutable, and prepared the verified v0.3.1 plus floating Action v0 release path.

v0.2.1

@handong66/evidoc-repo@0.2.1 release:notes
node scripts/release-notes.mjs

Evidoc 0.2.1 - 2026-07-10

• Upgraded every bundled and generated GitHub Action dependency to an immutable Node 24 release, eliminating GitHub's Node 20 runtime deprecation warning for CI, releases, and the packaged Evidoc Action.

v0.2.0

@handong66/evidoc-repo@0.2.0 release:notes
node scripts/release-notes.mjs

Evidoc 0.2.0 - 2026-07-10

• Fixed false-green gates for invalid fail policies/config files, changed-source coverage in the GitHub Action, nested Markdown links, and generated pre-push baselines.
• Hardened the Local App against DNS rebinding and cross-origin writes, added explicit deterministic safe-fix application with rescan, and exposed the shared Agent Runtime Contract in Local App and GitHub Action results.
• Consolidated configuration, fail policy, changed-impact, frontmatter, review-log, MCP tool, and safe-fix contracts into shared implementations instead of entrypoint-specific truth.
• Prepared synchronized 0.2.0 release artifacts with exact Action tags, version/tag verification, package README/LICENSE files, tarball identity checks, and fail-before-publish registry preflight.
• Renamed the project from DriftGuard to Evidoc across the CLI, npm package names, .evidoc configuration directory, MCP tools, GitHub Action examples, Local App, and public documentation.
• Added compatibility detection for pre-rename handong66/DriftGuard/packages/github-action@... workflows so existing GitHub redirect users are still recognized by doctor, setup warnings, and Local App checks instead of getting duplicate Evidoc gates.
• Redesigned the local Web app as the bilingual Evidoc Command Center with a system folder picker, fleet health, repository cockpit, triage queue, repair console, and copyable agent prompts.
• Fixed doctor readiness detection so source-checkout GitHub Actions workflows that run Evidoc through npm, pnpm, Yarn, Bun, or direct CLI commands count as valid Evidoc gates, without emitting packaged-action PR comment warnings or comment-only advisory fail-on warnings.
• Hardened the release workflow so npm pack/publish steps use explicit local package paths and public tarballs include runtime dist/src plus package README/LICENSE files, but not source tests or build metadata.
• Synchronized onboarding, architecture, and planning docs with the published npx repo-evidoc package path and current local GUI behavior.

v0.1.0

@handong66/evidoc-repo@0.1.0 release:notes
node scripts/release-notes.mjs

Evidoc Unreleased

• Renamed the project from DriftGuard to Evidoc across the CLI, npm package names, .evidoc configuration directory, MCP tools, GitHub Action examples, Local App, and public documentation.
• Added compatibility detection for pre-rename handong66/DriftGuard/packages/github-action@... workflows so existing GitHub redirect users are still recognized by doctor, setup warnings, and Local App checks instead of getting duplicate Evidoc gates.
• Redesigned the local Web app as the bilingual Evidoc Command Center with a system folder picker, fleet health, repository cockpit, triage queue, repair console, and copyable agent prompts.
• Fixed doctor readiness detection so source-checkout GitHub Actions workflows that run Evidoc through npm, pnpm, Yarn, Bun, or direct CLI commands count as valid Evidoc gates, without emitting packaged-action PR comment warnings or comment-only advisory fail-on warnings.
• Hardened the release workflow so npm pack/publish steps use explicit local package paths and public package tarballs only include runtime dist/src output.
• Synchronized onboarding, architecture, and planning docs with the scoped npx evidoc package path and current local GUI behavior.