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
843 B
843 B
Task ID: 154
Title: Documentation for new resources
Status: pending
Dependencies: 126, 128, 131, 133, 144, 152
Priority: low
Description: Create docs for epics, tasks, repos, sessions and update README and CLAUDE.md
Details:
Create documentation files:
- docs/epics.md - Epic/EpicTask concepts, CLI usage, API reference
- docs/tasks.md - Task lifecycle, states, transitions, verdicts
- docs/repos.md - CodeRepo configuration, credential setup
- docs/sessions.md - AgentSession lifecycle, exec usage
- docs/inference-tasks.md - document the rename from 'tasks' RBAC resource
- Update README.md resources table with new resources
- Update CLAUDE.md resource cheatsheet with new resources
Test Strategy:
Manual review: verify docs are accurate, CLI examples work, API endpoints match implementation.