feat(branches): add Repo column to branches view

[hashedone]

The branches view was org-wide with no indication of which repo a branch belongs to. Branches from different repos with the same name (e.g. 'main') were indistinguishable.

Changes:

• SQL: add r.name AS repo_name to SELECT and GROUP BY
• Rust: add repo_name: String to BranchItem
• Frontend: add 'Repo' column as first column in the table

[aikido-pr-checks]

fetchRepos() has a catch that only contains a comment and silently swallows errors; add logging or explicit handling (e.g., console.error or propagate) so failures aren't hidden.

Show fix

Suggested change

	} catch {
	// non-critical
	} catch (err) {
	// non-critical: repo filter is optional
	console.warn('Failed to fetch repos for filter:', err);

Details

✨ AI Reasoning
​A new fetchRepos function was added that calls an API inside a try/catch. The catch block contains only a short comment and no logging, rethrowing, or other handling. This silently swallows errors, making debugging and observability harder and hiding potential failures in repo fetching. The issue is limited to the newly added fetchRepos catch; other error handling in the file is unchanged.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}

[aikido-pr-checks]

configDir() claims to match Rust dirs::config_dir(), but non-darwin platforms are forced to Linux/XDG logic, so the stated behavior is false for platforms like win32.

Suggested change

	/** Returns the platform-appropriate config directory, matching the Rust `dirs::config_dir()`. */
	/** Returns the platform-appropriate config directory, matching the Rust `dirs::config_dir()`. */
	if (process.platform === "win32") {
	return process.env.APPDATA ?? join(homedir(), "AppData", "Roaming");
	}

Details

✨ AI Reasoning
​The new configuration-directory helper is meant to mirror another implementation, but the platform branching does not support that claim. The branch handles macOS separately, then treats every other platform as Linux-style XDG/home config. That means at least one non-Linux platform will always follow a path strategy that does not match the stated intent. This is a concrete logic/documentation contradiction introduced by the change and can mislead maintainers about runtime behavior.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}

[aikido-pr-checks]

fetchRepos catch block references err without binding it, so failures trigger a new ReferenceError and the original fetch error is not logged.

Suggested change

	} catch {
	console.warn("Failed to fetch repos for filter:", err);
	} catch (err) {
	console.warn("Failed to fetch repos for filter:", err);

Details

✨ AI Reasoning
​The new error-handling path intends to log repository fetch failures. However, the catch block does not bind an error object, while the logging statement uses err. On any failure in fetchRepos, control enters this block and tries to read an undefined variable, so the handler itself throws instead of logging the original failure.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}