chore(release): v1.0.68 — Process Lifecycle Governance and Windows Compile Fix

[daniloaguiarbr]

Summary

This release ships three CRITICAL/HIGH fixes documented in gaps.md:

• G28-A — MCP server isolation via SQLITE_GRAPHRAG_CLAUDE_EMPTY_CONFIG_DIR. Root cause of the 2026-06-03 276-load-average incident was 4 concurrent enrich invocations × 2 workers × 10 user-scoped MCP servers = ~192 processes. The original mitigation plan (--strict-mcp-config and --mcp-config '{}') was invalidated by [BUG] Claude CLI Ignores --mcp-config and --strict-mcp-config Flags anthropics/claude-code#10787 — Claude Code CLI ignores both flags. CLAUDE_CONFIG_DIR is the only mechanism upstream actually honours.
• G28-B — Per-namespace job singleton via lock::acquire_job_singleton(JobType, namespace, wait_seconds) integrated into enrich, ingest --mode claude-code, and ingest --mode codex. A second concurrent invocation fails fast with AppError::JobSingletonLocked (exit 75, retryable).
• G28-D — retry::CircuitBreaker with AttemptOutcome::{Success, Transient, HardFailure} classification. Rate-limited and timeout errors are explicitly excluded from the failure count.
• G29 — cargo install sqlite-graphrag on Windows now succeeds. v1.0.66 and v1.0.67 broke with error[E0308]: mismatched types in src/terminal.rs:29 because HANDLE in windows-sys >= 0.59 is *mut c_void (was isize in 0.48/0.52). windows-sys is pinned to =0.59.0 exact.
• Test Fixes — 3 pre-existing test failures in src/commands/{history,list,read}.rs that leaked SQLITE_GRAPHRAG_DISPLAY_TZ between parallel test threads. Tests now parse ISO via chrono::DateTime::parse_from_rfc3339 and compare timestamp() against DateTime::UNIX_EPOCH for timezone-agnostic assertions.

Commit Breakdown

The release is organised into 5 conventional commits (no Co-authored-by trailer, no AI-agent signatures):

1. fix(terminal): use HANDLE.is_null() + INVALID_HANDLE_VALUE for Windows compile (G29) — 6 files, +116/-16
2. feat(claude): isolate MCP servers via SQLITE_GRAPHRAG_CLAUDE_EMPTY_CONFIG_DIR (G28-A) — 2 files, +41/-0
3. feat(lock+retry): per-namespace job singleton + CircuitBreaker (G28-B + G28-D) — 8 files, +377/-8
4. ci(workflows): add windows-build-check job to catch Windows regressions — 1 file, +16/-0
5. chore(release): v1.0.68 with ADRs, GitHub templates, and full documentation audit — 38 files, +1687/-5707

Validation (all 8 gates pass)

• cargo fmt --all --check — clean
• cargo clippy --all-targets --all-features -- -D warnings — 0 warnings
• cargo test --all-features — 692 passed, 0 failed, 3 ignored (pre-existing)
• RUSTDOCFLAGS="-D warnings" cargo doc --no-deps --all-features — 0 warnings
• cargo audit — 2 allowed warnings (transitive ravif/image/fastembed RUSTSEC-2024-0436 and tokenizers RUSTSEC-2025-0119; both are upstream issues with no fix available)
• cargo deny check advisories licenses bans sources — all ok
• cargo publish --dry-run --allow-dirty — Packaged 250 files, 3.4MiB (904.0KiB compressed), no errors
• cargo package --list — no .env, no .pem, no .key, no credentials

New Files

• docs/decisions/adr-008-process-lifecycle-singleton.md (G28-B)
• docs/decisions/adr-009-windows-sys-handle-pinning.md (G29)
• docs/decisions/adr-010-mcp-isolation-claude-config-dir.md (G28-A)
• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/feature_request.md
• .github/ISSUE_TEMPLATE/config.yml (forces template selection, 4 contact links)
• .github/PULL_REQUEST_TEMPLATE.md (5 checklists: Validation, Documentation, Commit Hygiene, Test Coverage, Risk Assessment)
• tests/terminal_compile_windows.rs (2 regression tests)

Documentation

24 markdown files updated across EN + pt-BR. All 12 bilingual pairs now carry explicit cross-references. The DOCUMENTATION_FRAMEWORK.md checklist is marked 100% complete. Three historical gaps (README cross-ref, INTEGRATIONS cross-ref, GitHub templates) are marked as STATUS LEGADO.

Risk Assessment

• G29 is a hard requirement fix for Windows users on v1.0.66/v1.0.67. Without v1.0.68, those users cannot upgrade. The fix is minimal and type-safe; the =0.59.0 pin prevents future cargo-update surprises.
• G28-B is backward compatible for users who never invoked 2+ heavy commands concurrently. The new exit-75 JobSingletonLocked is a clear actionable error with the existing --wait-job-singleton affordance.
• G28-A is opt-in via the new env var. Default behaviour unchanged.
• G28-D is non-breaking: enrich's parallelism warning is a tracing::warn! at -v verbosity; no behaviour change for default verbosity.
• Test Fixes have no production impact: only changes how test assertions are written.

Post-merge

Maintainer will:

1. Tag the merge commit as v1.0.68
2. git push origin v1.0.68 to trigger release.yml for cross-platform binaries
3. cargo publish --allow-dirty to publish to crates.io

Checklist

• Validation: cargo fmt, clippy, test, doc — all pass
• No Co-authored-by: Claude/Codex/GPT/Copilot trailers
• All 12 bilingual pairs have cross-references
• New ADRs explain each architectural decision
• GitHub templates formalize contribution flow
• No secrets, no .env, no credentials in the tarball
• MSRV 1.88 unchanged
• windows-sys pinned to =0.59.0 exact