feat(settings): support worktree layout mappings (#582)

[rodboev]

Worktree mappings currently preserve project names only when each repository has its own explicit path-prefix row. That works for a few deleted worktrees, but it does not scale for layouts such as {repo}.worktrees/{branch} where the canonical project is already present in the path segment.

This adds a layout mode to the existing worktree mapping row instead of creating a separate template system. Existing rows stay explicit and keep their current behavior. A new {repo}.worktrees/{branch} layout lets one parent-directory mapping derive the project from service.worktrees style directories, while the existing longest-prefix precedence still lets a more specific explicit mapping override the generic layout.

The resolver stays in the worktree mapping layer, and the settings API and UI only adapt that row shape. Scope is limited to the local worktree mapping path; parser behavior, backend sync semantics, and unrelated project inference remain unchanged.

Fixes #582

[roborev-ci]

roborev: Combined Review (54f232e)

No Medium, High, or Critical findings were reported.

Review 1 reported only a Low-severity resolver fallback issue, which is omitted per instructions. Review 2 found no issues.

---

Reviewers: 2 done | Synthesis: codex, 6s | Total: 7m36s

[roborev-ci]

roborev: Combined Review (989c1f0)

Medium findings need attention before merge.

Medium

• internal/db/worktree_mappings.go:417 - A repo_dot_worktrees mapping can shadow broader valid mappings even when the cwd is not inside a {repo}.worktrees/{branch} directory. bestWorktreeProjectMapping stops on the first path-prefix match, then resolveRepoDotWorktreesProject returns false, so resolution never falls through to a less-specific explicit mapping such as the supported root-prefix mapping.

  Fix: Resolve mappings in order and continue to the next mapping when the selected layout cannot resolve for that cwd, or make the “best mapping” predicate layout-aware.

---

Reviewers: 2 done | Synthesis: codex, 6s | Total: 6m7s

[roborev-ci]

roborev: Combined Review (6d8026f)

No issues found.

---

Reviewers: 2 done | Synthesis: codex | Total: 6m3s

[roborev-ci]

roborev: Combined Review (646770c)

Medium issue found; no High or Critical findings.

Medium

• internal/db/project_identity.go:567
  Repo-dot-worktrees mappings are ignored by the legacy project identity fallback because layout rows persist Project as empty, but this code only accepts mappings where mapping.Project == project. Sessions whose project was derived from /parent/repo.worktrees/branch can fall back to per-branch cwd identities, making the same repo ambiguous across branches.

  Fix: Use the layout-aware resolver here and, for repo_dot_worktrees, derive the identity root from the matched repo.worktrees directory rather than mapping.Project.

---

Reviewers: 2 done | Synthesis: codex, 7s | Total: 6m41s

[roborev-ci]

roborev: Combined Review (a984bfe)

No issues found.

---

Reviewers: 2 done | Synthesis: codex | Total: 12m25s