Add GitForge README, .gitignore and initial Tauri + MCP/UI skeleton

[nanocubit]

Motivation

• Prepare the repository for publication on GitHub with a concise description and public-facing README.md.
• Provide repository hygiene via a practical .gitignore tailored for a Tauri + Rust + Node workspace.
• Bootstrap an MVP application skeleton (Tauri + Rust backend + Vue UI) including an MCP JSON-RPC server and a local agent to enable iterative development.

Description

• Add repository metadata and docs: gitforge/REPOSITORY_DESCRIPTION.md, a GitHub-ready gitforge/README.md, and gitforge/.gitignore to cover Rust/Tauri, Node, local DB/logs, and editor artifacts.
• Add workspace/development config including gitforge/.devcontainer/devcontainer.json and Tauri config gitforge/tauri.conf.json and package manifests gitforge/Cargo.toml and gitforge/package.json.
• Implement Tauri app skeleton and backend: src-tauri/src/main.rs, a local agent in src-tauri/src/agent/mod.rs, and an MCP JSON-RPC server with core methods and DB-backed PR/worktree support in src-tauri/src/mcp/server.rs.
• Add frontend MVP UI components and styles under gitforge/src/components and gitforge/src/style, plus a simple CLI entry in gitforge/src/bin/gitforge.rs.

Testing

• Performed repository-level validations by running git status --short and file inspections with nl -ba for gitforge/REPOSITORY_DESCRIPTION.md, gitforge/.gitignore, and gitforge/README.md, which all succeeded.
• Committed the changes with git commit which completed successfully.
• Added Rust unit/integration tests inside gitforge/src-tauri/src/mcp/server.rs::tests for MCP methods, though those Rust tests were not executed in this rollout.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 834894690e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add src-tauri main binary to Cargo targets

The manifest declares only one binary target (src/bin/gitforge.rs), so Cargo will not build src-tauri/src/main.rs where mcp_call, voice_process, and the MCP backend wiring live. In this state, the shipped binary cannot run the Tauri/MCP backend code from this commit, and the src-tauri tests are also excluded from normal cargo test runs.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Pass requested branch into worktree creation

git_worktree_create parses and even creates the requested branch, but the actual worktree call uses repo.worktree(name, path, None), so the branch parameter is not applied when creating the worktree. When callers request a branch different from current HEAD, the created worktree can point at the wrong ref while the response/SQLite metadata reports the requested branch, which breaks branch-scoped workflows.

Useful? React with 👍 / 👎.