a869f77070
Merges feat/agent-project-membership (task 166/152). An agent can finally join many projects: membership routes, per-membership role and optional brain override, chat resolving context from the membership, and CLI attach-agent / detach-agent / get memberships. The legacy Agent.projectId fallback is kept for this release as the schema comment promises. Conflict resolved in main.ts: that branch added its RBAC case to mapUrlToPermission inline, while this branch had extracted the function to middleware/url-permission.ts so it could be tested. Kept the extraction and ported the case into it — joining a team is `edit:agents:<name>`, not `create:agents`, which is the authority to mint a whole agent. Also fixes something the extraction makes possible. security.test.ts contained a hand-copied reproduction of mapUrlToPermission, because main.ts self-invokes main() and nothing in it was importable. A security test asserting against a copy stops testing the system the moment the real one changes, and this copy had already drifted. It now imports the real function; all 18 assertions still pass, against the code that actually runs. Local: build clean, workspace 2550 passed, lint unchanged at 794 errors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N4wNHWf7xSwnZCWpJcyv9p
26 lines
809 B
Markdown
26 lines
809 B
Markdown
# Task ID: 152
|
|
|
|
**Title:** Agent membership routes
|
|
|
|
**Status:** pending
|
|
|
|
**Dependencies:** 120
|
|
|
|
**Priority:** medium
|
|
|
|
**Description:** Create API endpoints for managing agent-project memberships
|
|
|
|
**Details:**
|
|
|
|
Add to existing agent routes or create new file:
|
|
1. GET /api/v1/agents/:name/projects - list projects agent belongs to
|
|
2. POST /api/v1/agents/:name/projects/:project - add membership { role?, llm? }
|
|
3. DELETE /api/v1/agents/:name/projects/:project - remove membership
|
|
4. GET /api/v1/projects/:name/agents - list agents in project
|
|
5. Keep Agent.projectId in sync when membership added/removed (backward compat for one release)
|
|
6. Follow existing route patterns
|
|
|
|
**Test Strategy:**
|
|
|
|
Route tests: test add membership creates junction row, test remove deletes it, test list returns correct memberships.
|