What's new in RepoCrew

GitHub App & multi-user identity

RepoCrew now installs as a first-class GitHub App instead of riding on OAuth tokens. Installations map to projects, and every actor on a repo resolves to a real RepoCrew identity — the foundation for team assignment and bidirectional sync.

Highlights

• App installation tokens replace per-user OAuth for all server-side Git calls.
• Branch-protection aware: git:merge_pr refuses cleanly when required reviews aren't met — we surface the rule, we don't replicate it.
• Identity mapping connects GitHub actors to workspace members in settings.

Stabilization track complete

A nine-layer review turned into a guardrail program. The product's substance was already there — this release made the structure survive the next phase of growth.

• CI & pre-commit — typecheck, lint, vitest, deno check and smoke tests gate every merge. Red build blocks.
• Contract layer — every edge-function response is Zod-parsed at the hook boundary. Zero unchecked casts in hooks.
• Migration policy — monotonic timestamps, one change per file, documented in MIGRATIONS.md.
• Honest onboarding — the GitHub step no longer fakes a connection; deferral is explicit.

Copy · Compose · Adapt bootstrap

The "template-driven" claim is now real. Frameworks, scaffolds and deploy configs moved into the database, and bundle generation became a three-stage pipeline with a deterministic floor.

• Copy — tooling floor, scaffold and configs, identical per framework.
• Compose — a rule-based selector picks tested blocks from plan signals.
• Adapt — one structured LLM pass personalizes the bundle. If it fails, Copy + Compose is still a shippable floor.

Every generated file carries a version stamp so telemetry can attribute downstream edits back to the prompt that produced them.

Deep GitHub: Issues, Actions & Releases

Beyond commits and PRs — RepoCrew now mirrors GitHub Issues bidirectionally, surfaces CI status on task links, and exposes releases to agents.

• Issues mirror into project_issues; push a task to GitHub as an issue in one click.
• CI status renders inline next to PR links — green check, red X, running spinner.
• GitHub-native syntax: Closes #7 works exactly as it has since 2013 — zero migration friction.

Provider-neutral git:* namespace

The GitHub-specific github:* tool namespace became git:*, backed by a provider router. GitLab and Bitbucket are now a class-file drop-in rather than a separate product.

• Webhook router normalizes every provider to a neutral event shape.
• Task-link keys neutralized: github_commit → commit with a provider column.

The in-app Planner

A project-scoped assistant in every project, opened from the sparkle button or ⌘J. It reads and edits that project's tasks, milestones, decisions and memory — and shares the exact tool registry your local Claude Code calls over MCP.

• Strategic actions — milestones, plan refinements, code & infra — are approval-gated.
• Bounded to 8 tool-call rounds per turn. Reactive only — no background nagging.
• Entity references like [task:1A4F] render as live chips with title and status.