Pin T-1001's pending-directory path resolution to git rev-parse --git-path

[MongLong0214]

ADR-0021 claims .git/commitlore/pending/ is "per-worktree and per-clone", but T-1001 never specified how the path is resolved. A linked worktree's .git is a file, not a directory — naive path.join(cwd, '.git', ...) breaks there.

This codebase already has the fix as an established, working pattern: src/core/index-db.ts:325 ("--git-path is what makes this correct") and src/hooks/prepare-commit-msg.ts:27,75 both use git rev-parse --git-path already. The ticket for the new transaction store just never pointed at it.

npx tsc -p tsconfig.json --noEmit exits 0.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/dev..233a891a87a4389b3aea8c9408f4f68c26126586
Active constraints: 1 limits · 3 ruled-out · 0 warnings — from 2 records over 1 changed path

Limits (1)

• r-gateaacc 45a8f2b — nothing enforces the src/mcp/server.ts merge-sequencing rule automatically — it is a process constraint the next PR author has to read and follow

Ruled out (3)

• r-pendpath 233a891 — leaving this to the implementer's judgment | the precedent already exists in this codebase and the failure mode (silently wrong location in a worktree) would not surface as a test failure unless someone specifically writes a worktree test -- worth pinning explicitly rather than hoping it's noticed
• r-gateaacc 45a8f2b — rewriting ADR-0020/0021/0022 or the existing T-1001 · Pending transaction store #193-213 issue bodies | they already meet or exceed the source review's own requirements (exact ownership, forbidden scope, RED/GREEN, AC-to-test, four-tier verification, evidence invalidation, stop conditions); rewriting working documents to match a stale review would be pure churn
• r-gateaacc 45a8f2b — inventing content for a hypothetical P0-7 original definition | none exists in history (verified); asserting one would be the exact failure this document exists to prevent

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}