merge: AgentProject membership — the junction is now load-bearing
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
This commit is contained in:
25
.taskmaster/tasks/task_158.md
Normal file
25
.taskmaster/tasks/task_158.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Task ID: 158
|
||||
|
||||
**Title:** Deferred: Tier-2 vision critic placeholder
|
||||
|
||||
**Status:** pending
|
||||
|
||||
**Dependencies:** 131, 149
|
||||
|
||||
**Priority:** low
|
||||
|
||||
**Description:** Placeholder task for Tier-2 vision critic and Epic-comparison loop - blocked on design questions
|
||||
|
||||
**Details:**
|
||||
|
||||
DEFERRED - DO NOT IMPLEMENT YET
|
||||
|
||||
Blocked on docs/agentic-teams.md §15 Q13: does this need render/screenshot infrastructure, or can a design-aware persona judge from a structured artifact?
|
||||
|
||||
Concept: A review-only, non-executing design/product persona that judges the assembled result against the Epic in its native medium, producing reopen / new-task / exec outcomes.
|
||||
|
||||
Expand this task when the blocking design question is answered.
|
||||
|
||||
**Test Strategy:**
|
||||
|
||||
N/A - placeholder only
|
||||
Reference in New Issue
Block a user