Bizcom Worktree Map

Updated: 2026-04-10

Purpose

Record the current branch → worktree mapping used by Bizcom development so validation and automation do not assume a single checkout.

Rule

Do not assume the main repo checkout contains every active Bizcom branch. Verify with:

git worktree list --porcelain

Or use the helper:

scripts/resolve-worktree.sh <branch>

Verified mapping — 2026-03-25

Branch	Worktree path	Notes
bizcom/manage-clients-feedback-fixes	/home/alex/.openclaw/workspace/Bizcom-Web-Portal	main checkout currently on this branch
bizcom/global-timer-shell	/tmp/bizcom-global-timer	staging-merged PR #142
bizcom/notification-routing-audit	/tmp/bizcom-notification-routing-fix	staging-merged PR #143
feat/task-query-architecture-impl	/tmp/bizcom-task-query	active implementation lane
fix/task-bulk-route-order	/tmp/bizcom-triage-7AEACh/repo	older triage worktree

Automation guidance

Nightly Bizcom flows should:

1. verify GitHub state first
2. resolve the branch worktree path explicitly
3. run validation in the resolved path
4. only fall back to the main repo root when no dedicated worktree exists

Why this matters

Previous dry-run logic failed because it tried to git checkout branches that were already locked to other worktrees. Worktree-aware execution is required for reliable unattended validation.

Dry-run result after worktree hardening

• bizcom/global-timer-shell resolved cleanly to /tmp/bizcom-global-timer and validated without the earlier checkout failure.
• bizcom/notification-routing-audit resolved cleanly to /tmp/bizcom-notification-routing-fix; the remaining issue is branch hygiene/doc drift, not worktree resolution.
• feat/task-query-architecture-impl resolved cleanly to /tmp/bizcom-task-query; it remains mid-implementation with uncommitted changes and is not validation-ready.