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
977 B
977 B
Task ID: 113
Title: Write Documentation for Model Studio
Status: done
Dependencies: 105 ✓, 106 ✓, 107 ✓, 108 ✓, 109 ✓
Priority: low
Description: Create documentation for using model studio for live proxymodel development and debugging.
Details:
Create docs/proxymodels/model-studio.md covering:
- Overview: Three-window setup (Claude Client, Model Studio, Claude Monitor)
- Starting Model Studio:
mcpctl console --model-studio <project> - Keyboard shortcuts reference
- Viewing original vs transformed content
- Pause mode: when and why to use it
- Editing paused responses
- Switching proxymodels mid-session
- Using Claude Monitor to observe and modify stages
- The correction workflow: edit → observe → adjust stage → verify
- MCP tools available to Claude Monitor
- Troubleshooting common issues
Test Strategy:
Review documentation for completeness, verify all described features work as documented.