Parent: #4. Wire the smallest authenticated path from a coherent project-scoped Signal or explicit chat request to projectIssues.create and projectIssues.begin, then dispatch project-manager. Reuse existing Signal and issue tables. Restore secure request-scoped Signal tools only as needed. Keep idempotency and organization/project authorization. Do not introduce Candidate or WorkUnit tables.
Parent: #4. Wire the smallest authenticated path from a coherent project-scoped Signal or explicit chat request to projectIssues.create and projectIssues.begin, then dispatch project-manager. Reuse existing Signal and issue tables. Restore secure request-scoped Signal tools only as needed. Keep idempotency and organization/project authorization. Do not introduce Candidate or WorkUnit tables.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #4. Wire the smallest authenticated path from a coherent project-scoped Signal or explicit chat request to projectIssues.create and projectIssues.begin, then dispatch project-manager. Reuse existing Signal and issue tables. Restore secure request-scoped Signal tools only as needed. Keep idempotency and organization/project authorization. Do not introduce Candidate or WorkUnit tables.