repowise-dev
diff --git a/‎.gitignore‎
Lines changed: 10 additions & 0 deletions b/‎.gitignore‎
Lines changed: 10 additions & 0 deletions
diff --git a/‎README.md‎
Lines changed: 165 additions & 30 deletions b/‎README.md‎
Lines changed: 165 additions & 30 deletions
diff --git a/‎docs/AUTO_SYNC.md‎
Lines changed: 62 additions & 32 deletions b/‎docs/AUTO_SYNC.md‎
Lines changed: 62 additions & 32 deletions
diff --git a/‎docs/CHANGELOG.md‎
Lines changed: 54 additions & 0 deletions b/‎docs/CHANGELOG.md‎
Lines changed: 54 additions & 0 deletions
@@ -80,6 +80,8 @@ next-env.d.ts
 # repowise runtime data
 .repowise/
 !.repowise/mcp.json.example
+.repowise-workspace/
+.repowise-workspace.yaml
 
 # Database
 *.db
@@ -111,3 +113,11 @@ ehthumbs.db
 
 # Claude Code
 .claude/
+
+# repowise API keys (local)
+.repowise/.env
+
+# Internal docs (not for distribution)
+docs/COMPETITIVE_ANALYSIS.md
+docs/GRAPH_INTELLIGENCE_UPGRADE.md
+docs/multi-repo/
@@ -13,50 +13,47 @@ method that fits your setup.
 
 ---
 
-## 1. Post-Commit Git Hook
+## 1. Post-Commit Git Hook (Recommended)
 
 Runs `repowise update` in the background after every local commit. Your
-terminal is never blocked.
+terminal is never blocked. This is the recommended auto-sync method for
+local development.
 
 ### Setup
 
+`repowise init` will offer to install the hook automatically at the end
+of the setup wizard. You can also install or manage it manually:
+
 ```bash
-cat > .git/hooks/post-commit << 'EOF'
-#!/bin/sh
-echo "[repowise] Triggering wiki update..."
-(
-  cd "$(git rev-parse --show-toplevel)" || exit 1
-  repowise update > /tmp/repowise-update.log 2>&1
-) &
-exit 0
-EOF
-chmod +x .git/hooks/post-commit
+repowise hook install              # install for current repo
+repowise hook install --workspace  # install for all workspace repos
+repowise hook status               # check if installed
+repowise hook uninstall            # remove the hook
 ```
 
-> **Windows (Git Bash):** If `repowise` isn't on your bash PATH (e.g. installed
-> via `uv`), replace the `repowise update` line with:
-> ```bash
-> powershell.exe -Command "uv run repowise update" > /tmp/repowise-update.log 2>&1
-> ```
+The hook is marker-delimited, so it safely coexists with other tools'
+hooks (linters, formatters, etc.) in the same `post-commit` file.
 
 ### What happens
 
 1. You run `git commit`
-2. The hook fires in the background
+2. The hook fires in the background (non-blocking)
 3. `repowise update` diffs the new commit against the last synced commit
 4. Only affected pages are regenerated (typically 3-10 for a small commit)
-5. Output is logged to `/tmp/repowise-update.log`
+5. Graph, git stats, dead code, and decisions are also refreshed
 
-### Check the last run
+### Check hook status
 
 ```bash
-cat /tmp/repowise-update.log
+repowise hook status
+repowise hook status --workspace   # check all repos in workspace
 ```
 
 ### Remove the hook
 
 ```bash
-rm .git/hooks/post-commit
+repowise hook uninstall
+repowise hook uninstall --workspace
 ```
 
 ---
@@ -170,20 +167,50 @@ with `repowise serve`.
 
 ---
 
-## How Incremental Updates Work
+## How Updates Work
+
+There are two update paths, depending on the trigger:
 
-Regardless of which trigger method you use, the update process is the same:
+### CLI incremental update (`repowise update`)
 
 1. **Diff** -- compare the new HEAD against the last synced commit
-2. **Detect affected pages** -- find directly changed files, then cascade to
-   files that import them (1-hop), capped at 30 pages per run
-3. **Regenerate** -- call the LLM only for affected pages
-4. **Persist** -- update the database and search index
-5. **Save state** -- record the new HEAD as the last synced commit
+2. **Full graph rebuild** -- re-traverse and re-parse all files to rebuild
+   the dependency graph (needed for cascade analysis)
+3. **Incremental git re-index** -- re-index git metadata only for changed files,
+   then recompute percentiles across the whole repo
+4. **Dead code analysis** -- run partial dead code detection on changed files
+   and their graph neighbors
+5. **Decision re-scan** -- re-scan changed files for inline decision markers
+6. **Detect affected pages** -- find directly changed files, cascade to 1-hop
+   importers, capped by an adaptive budget (auto-scaled based on change size)
+7. **Regenerate** -- call the LLM only for affected pages
+8. **Cross-repo hooks** -- if the repo is part of a workspace, re-run cross-repo
+   co-change and contract analysis
+9. **Persist** -- update the database, search index, and record a GenerationJob
+10. **Save state** -- record the new HEAD as the last synced commit
 
 A typical single-commit update touches 3-10 pages and completes in under a
 minute.
 
+### Server sync (`POST /api/repos/{id}/sync`)
+
+1. **Full re-traverse** -- re-parse all files and rebuild the dependency graph
+2. **Full git re-index** -- re-index git metadata for all files
+3. **Dead code analysis** -- full dead code scan
+4. **Decision extraction** -- full decision marker scan
+5. **Persist** -- update the database
+6. **Save state** -- record the new HEAD
+
+Server sync does **not** regenerate wiki pages (no LLM cost). Use
+**Full Re-index** (`POST /api/repos/{id}/full-resync`) to also regenerate
+all wiki pages.
+
+### Workspace updates (`repowise update --workspace`)
+
+Updates all stale repos in parallel (up to 4 concurrent), then re-runs
+cross-repo analysis (co-changes, package dependencies, API contracts).
+Use `--repo <alias>` to target a single repo within the workspace.
+
 ### Dry run
 
 To see what would be updated without actually regenerating:
@@ -195,9 +222,12 @@ repowise update --dry-run
 ### Manual update
 
 ```bash
-repowise update                    # diff since last sync
-repowise update --since abc123     # diff from a specific commit
-repowise update --cascade-budget 50  # allow more cascade pages (default: 30)
+repowise update                        # diff since last sync
+repowise update --since abc123         # diff from a specific commit
+repowise update --cascade-budget 50    # allow more cascade pages (default: auto)
+repowise update --workspace            # update all stale workspace repos
+repowise update --repo backend         # update a specific workspace repo
+repowise watch --workspace             # auto-update all workspace repos on file change
 ```
 
 ---
 
@@ -9,6 +9,58 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [0.3.0] — 2026-04-13
+
+### Added
+
+#### Multi-repo workspaces
+- **Workspace support** — `repowise init .` from a parent directory scans for git repos (up to 3 levels deep), prompts for selection, and indexes each repo with cross-repo analysis. Config stored in `.repowise-workspace.yaml`.
+- **Workspace CLI commands** — `repowise workspace list`, `workspace add <path>`, `workspace remove <alias>`, `workspace scan`, `workspace set-default <alias>` for managing repos in a workspace.
+- **Workspace-aware MCP server** — a single MCP server instance serves all workspace repos. Tools accept an optional `repo` parameter to target a specific repo or `"all"` to query across the workspace. Lazy-loading with LRU eviction (max 5 repos loaded simultaneously).
+- **Cross-repo co-change detection** — analyzes git history across repos to find files that frequently change in the same time window.
+- **API contract extraction** — scans for HTTP route handlers (Express, FastAPI, Spring, Go), gRPC service definitions, and message topic publishers/subscribers. Matches providers with consumers across repos.
+- **Package dependency scanning** — reads package manifests (`package.json`, `pyproject.toml`, `go.mod`, `pom.xml`) to detect inter-repo package dependencies.
+- **Workspace CLAUDE.md** — auto-generated context file at the workspace root covering all repos, their relationships, cross-repo signals, and contract links.
+- **Workspace web UI** — workspace dashboard (`/workspace`) with aggregate stats and repo cards, contracts view (`/workspace/contracts`) with provider/consumer matching, and co-changes view (`/workspace/co-changes`) with cross-repo file pairs ranked by strength.
+- **Workspace update** — `repowise update --workspace` updates all stale repos in parallel (up to 4 concurrent) then re-runs cross-repo analysis. `--repo <alias>` targets a single repo.
+- **Workspace watch** — `repowise watch --workspace` auto-updates all workspace repos on file change.
+
+#### Auto-sync hooks
+- **`repowise hook` CLI** — `repowise hook install` installs a marker-delimited post-commit git hook that runs `repowise update` in the background after every commit. `hook install --workspace` installs for all workspace repos. `hook status` and `hook uninstall` for management.
+- **Proactive context enrichment via Claude Code hooks** — `repowise init` registers PreToolUse and PostToolUse hooks in `~/.claude/settings.json`. PreToolUse enriches every `Grep`/`Glob` call with graph context (importers, dependencies, symbols, git signals) at ~24ms latency. PostToolUse detects git commits and notifies the agent when the wiki is stale.
+- **Polling scheduler** — when the server is running, a background job polls registered repositories every 15 minutes and triggers updates for new commits missed by webhooks.
+
+#### Graph intelligence
+- **Symbol-level dependency graph** — the dependency graph is now two-tier: file nodes for module-level relationships and symbol nodes (functions, classes, methods) for fine-grained call resolution. Call edges carry confidence scores (0.0–1.0).
+- **3-tier call resolution** — Tier 1: same-file targets (confidence 0.95). Tier 2: import-scoped targets via named bindings (0.85–0.93). Tier 3: global unique match (0.50). Extracted by tree-sitter for Python, TypeScript, JavaScript, Go, Rust, Java, and C++.
+- **Named binding resolution** — tracks import aliases, barrel re-exports (`__init__.py`, `index.ts`), and namespace imports across all 7 full-tier languages.
+- **Heritage extraction** — class inheritance and interface implementation for 11 languages (Python, TypeScript, JavaScript, Java, Go, Rust, C++, Kotlin, Ruby, C#, C) with `extends`/`implements` graph edges.
+- **Leiden community detection** — two-level community detection (file communities from import edges, symbol communities from call/heritage edges) with cohesion scoring and heuristic labeling. Falls back to NetworkX Louvain when graspologic is unavailable.
+- **Execution flow tracing** — 5-signal entry point scoring (fan-out ratio, in-degree, visibility, name pattern, framework hint) with BFS call-path discovery and cross-community classification.
+- **Graph query indexes** (migration `0017`) — composite indexes for sub-millisecond graph queries.
+
+#### Web UI
+- **Graph Intelligence on Overview** — expandable community list (labels, cohesion, member counts) and execution flows panel with call-path traces on the overview dashboard.
+- **Wiki sidebar** — new collapsible section showing PageRank and betweenness percentile bars, community label, and in/out degree for the current file.
+- **Symbols drawer** — right panel with graph metrics, callers/callees (with confidence scores), and heritage (extends/implements) for class nodes.
+- **Graph page** — community color mode uses real community labels from Leiden detection. Clicking a node opens a community detail panel. Active color mode preserved as a URL parameter.
+- **Contributor network, hotspot, and ownership pages** — new dedicated pages for git intelligence.
+- **Docs viewer** — enriched with graph intelligence sidebar, version history, and improved markdown rendering.
+- **5 new graph REST API endpoints** — communities list, community detail, node metrics, callers/callees, and execution flows.
+
+#### Other
+- **Improved init UX** — pre-scan phase shows repo size and language breakdown before confirming. Advanced config options grouped logically with live insights during indexing.
+- **Doc generation enriched with graph intelligence** — wiki page generation prompts now include community context, caller/callee information, and heritage relationships.
+
+### Changed
+- **`get_overview`** now includes `community_summary` — top communities by size with labels and cohesion scores.
+- **`get_context`** now includes `community` block per file target with community ID and label (when `compact=False`). In workspace mode, enriched with cross-repo co-change and contract data.
+- **`get_risk`** enriched with cross-repo signals in workspace mode — co-change partners from other repos and contract dependencies.
+- **`search_codebase`** in workspace mode searches across all repos and merges results.
+- **Job executor** — improved progress tracking, concurrent run detection (HTTP 409), and crash recovery for stale running jobs on server startup.
+
+---
+
 ## [0.2.3] — 2026-04-11
 
 ### Added
@@ -234,6 +286,8 @@ See git history for releases prior to 0.2.0.
 
 ---
 
+[0.3.0]: https://github.com/repowise-dev/repowise/compare/v0.2.3...HEAD
+[0.2.3]: https://github.com/repowise-dev/repowise/compare/v0.2.2...v0.2.3
 [0.2.2]: https://github.com/repowise-dev/repowise/compare/v0.2.1...v0.2.2
 [0.2.1]: https://github.com/repowise-dev/repowise/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/repowise-dev/repowise/compare/v0.1.31...v0.2.0