fix(worktrees): resolve numeric registry IDs

[andrei-hasna]

Summary:

• accept canonical positive-decimal registry IDs at the worktree resolver boundary
• preserve exact path/name lookup for non-canonical numeric strings
• add a regression proving numeric ID and exact path resolve the same repository

Validation:

• focused RED: 0 pass / 1 fail before fix
• focused GREEN: 1 pass / 0 fail
• worktree tests: 41 pass / 0 fail
• worktree CLI tests: 7 pass / 0 fail
• full tests: 804 pass / 0 fail
• bun run typecheck: exit 0
• bun run build: exit 0
• staged and commit-range credential scans: exit 0

Todos: f0c117d2-cc6c-4692-a3b5-529133db3812 (OPE57-00039)

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] GO — #72 @ b37aa92 — lens: correctness+security+gates, reviewer Xenon (1 of 1)

Reviewed the complete diff against freshly fetched origin/main at 7c992a7, plus the surrounding repository lookup, CLI dispatch, worktree creation, containment, parent-health, lease, and test-fixture code in:

• src/lib/worktrees.ts
• src/lib/worktrees.test.ts
• src/db/repos.ts
• src/db/repos.test.ts
• src/cli/index.tsx
• package.json
• tsconfig.json

Commands and measured results:

• bun install — exit 0; setup completed, 496 packages installed. This is setup, not a test gate.
• bun run typecheck — exit 0; TypeScript emitted no pass/fail count.
• bun run test — exit 0; 804 pass, 0 fail, 3574 expect() calls across 52 files.
• git diff --check origin/main...HEAD — exit 0.

Blocking P0/P1 findings: none.

The new parsing converts only canonical positive-decimal strings whose numeric value is a safe integer, preserving the existing exact string path/name lookup for other shapes. The resolved row then passes through the existing identity, parent-health, containment, ref-validation, and lease gates. The regression test proves a Commander-shaped string registry ID selects the same repository identity as the exact path.

Non-blocking follow-ups: none.