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
1009 B
1009 B
Task ID: 137
Title: CLI create subcommands for new resources
Status: pending
Dependencies: 136
Priority: medium
Description: Add create subcommands for epic, epictask, task, repo with all settable fields as flags
Details:
In src/cli/src/commands/create.ts:
- Add 'epic' subcommand: --name, --project, --content, --done-criteria (JSON), --description
- Add 'epictask' subcommand: --name, --epic, --project, --done-criteria, --description, --depends-on (comma-separated names)
- Add 'task' subcommand: --name, --title, --epictask, --epic, --project, --description, --risk, --repo
- Add 'repo' subcommand: --name, --project, --url, --default-branch, --path, --provider, --cred-secret, --cred-key
- Every field settable in apply must have a corresponding flag
- Follow existing create subcommand patterns
Test Strategy:
Unit tests: test each create subcommand parses all flags correctly, test required flags are enforced, test API calls are made with correct payload.