fix(foreman): multi-repo spec reading and repo validation (#254) #272
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/254-foreman-multi-repo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #254
What
Three small gaps left in the multi-repo foreman feature — the schema migration, file endpoints, and session binding were already done; these are the remaining pieces:
Backend
handleForemanBreakdownPreview— was always reading the spec from the local filesystem viaresolveAllowlistedFile. For any repo other thancharles/claude-hooks(the service cwd) the file doesn't exist locally, so "Breakdown" would always return 404. Now uses the same local/remote split the other file handlers already have: cwd repo → local FS, any other repo →getRepoFileContentvia the foreman token.handleForemanChat— accepted any validowner/namestring as a repo without checking it againstcfg.repos. Now returns400when a non-emptyctx.reposlist is configured and the requested repo isn't in it.UI
Chat panel — adds a thin
Repo: <badge>bar above the transcript whenever the active session is bound to a repo, so it's always clear which repo a session targets without having to look at the sidebar chip.