Fix: forgejo remote detection + add mcd-tracker board #148

New issue

Closed

opened 2026-03-22 09:45:29 +00:00 by forgejo_admin · 1 comment

forgejo_admin commented

2026-03-22 09:45:29 +00:00

Contributor

Type

Feature

Lineage

plan-pal-e-agency → Phase 20 validation → nit-bundle #147

Repo

forgejo_admin/claude-custom

User Story

As the superuser, when I open Claude Code in ~/pal-e-platform, the session detects pal-e-platform project even though the remote is named forgejo not origin. And board-mcd-tracker syncs at startup. story:superuser-manage

Context

Validation testing of Phase 20 found two gaps. pal-e-platform is the only repo using forgejo as the remote name (per convention: "Platform: forgejo remote. Apps: origin remote"). The hook only checks origin.

File Targets

Files the agent should modify:

hooks/session-start-context.sh — line 68: change git remote get-url origin to try origin first, then fall back to first available remote
hooks/boards-config.sh — add "board-mcd-tracker" to BOARDS array

Files the agent should NOT touch:

Any other hooks or files

Acceptance Criteria

~/pal-e-platform detects as pal-e-platform project (remote named forgejo)
~/basketball-api still detects as westside-basketball (remote named origin)
board-mcd-tracker in BOARDS array
No regression

Test Expectations

bash -n passes on both files
Manual: simulate CWD as pal-e-platform, verify detection

Constraints

2 one-line changes total
Clone to temp: git clone ~/claude-custom /tmp/claude-custom-{branch}

Checklist

PR opened
Tests pass
No unrelated changes

plan-pal-e-agency — parent plan
Closes #147

### Type Feature ### Lineage `plan-pal-e-agency` → Phase 20 validation → nit-bundle #147 ### Repo `forgejo_admin/claude-custom` ### User Story As the superuser, when I open Claude Code in `~/pal-e-platform`, the session detects `pal-e-platform` project even though the remote is named `forgejo` not `origin`. And `board-mcd-tracker` syncs at startup. `story:superuser-manage` ### Context Validation testing of Phase 20 found two gaps. pal-e-platform is the only repo using `forgejo` as the remote name (per convention: "Platform: `forgejo` remote. Apps: `origin` remote"). The hook only checks `origin`. ### File Targets Files the agent should modify: - `hooks/session-start-context.sh` — line 68: change `git remote get-url origin` to try `origin` first, then fall back to first available remote - `hooks/boards-config.sh` — add `"board-mcd-tracker"` to BOARDS array Files the agent should NOT touch: - Any other hooks or files ### Acceptance Criteria - [ ] `~/pal-e-platform` detects as `pal-e-platform` project (remote named `forgejo`) - [ ] `~/basketball-api` still detects as `westside-basketball` (remote named `origin`) - [ ] `board-mcd-tracker` in BOARDS array - [ ] No regression ### Test Expectations - [ ] `bash -n` passes on both files - [ ] Manual: simulate CWD as pal-e-platform, verify detection ### Constraints - 2 one-line changes total - Clone to temp: `git clone ~/claude-custom /tmp/claude-custom-{branch}` ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `plan-pal-e-agency` — parent plan - Closes #147