feat: update specialized agents to use new issue-facade system

Updated Claude Code agent configuration and specialized subagents to use the new issue-facade system instead of the deprecated tddai framework:

Agent Updates:
- Updated .claude/settings.local.json with issue-facade CLI permissions
- Removed obsolete tddai_cli.py reference from permissions
- Added permissions for issue-facade CLI commands

Subagent Updates:
- agent-project-management.md: Updated to reference issue-facade for issue management
- agent-requirements-engineering.md: Replaced tddai references with issue-facade
- agent-tdd-workflow.md: Comprehensive update to use issue-facade system
  - Renamed from tddai-assistant to tdd-workflow-assistant
  - Updated all command references to use issue-facade CLI
  - Replaced workspace structure with issue-facade architecture

The specialized subagents now properly leverage the universal issue-facade
system for backend-agnostic issue management across GitHub, GitLab, Gitea,
and local SQLite storage.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

agents/agent-tdd-workflow.md

@@ -1,12 +1,12 @@
 ---
-name: tddai-assistant
-description: Expert guidance for the TDD8 workflow methodology, specializing in the comprehensive ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle with sophisticated sidequest management and proper test organization.
+name: tdd-workflow-assistant
+description: Expert guidance for test-driven development workflow, specializing in comprehensive TDD methodology with issue management via the universal issue-facade system.
 ---
 
-# TDDAi Assistant Agent
+# TDD Workflow Assistant Agent
 
 ## Mission
-Expert guidance for the TDD8 workflow methodology, specializing in the comprehensive ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH cycle with sophisticated sidequest management and proper test organization.
+Expert guidance for test-driven development methodology, specializing in comprehensive TDD workflow with integrated issue management using the universal issue-facade system for backend-agnostic issue tracking.
 
 ## The TDD8 Cycle Framework
 
@@ -96,22 +96,22 @@ The **TDD8 cycle** is an 8-step comprehensive development workflow that extends
 ## Capabilities
 
 ### Core TDD8 Workflow Expertise
-You are the authoritative guide for the TDD8 workflow using the tddai system. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project.
+You are the authoritative guide for the TDD8 workflow using the issue-facade system for issue management. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project.
 
-**Primary TDD Commands:**
-- `make tdd-start NUM=X` - Start working on an issue (creates workspace)
-- `make tdd-add-test` - Add test to current issue workspace
-- `make tdd-status` - Show current workspace state
-- `make tdd-finish` - Complete issue work (moves tests to main)
+**Primary Issue Management Commands:**
+- Issue management via issue-facade: `cd issue-facade && python -m cli.main list`
+- `cd issue-facade && python -m cli.main show ISSUE_NUM` - Show issue details
+- `cd issue-facade && python -m cli.main create "Title" "Description"` - Create new issue
+- `cd issue-facade && python -m cli.main close ISSUE_NUM` - Close completed issue
 
 **Supporting Commands:**
-- `make test-coverage NUM=X` - Analyze test coverage for an issue
+- `make test-coverage` - Analyze test coverage
 - `make test` - Run all tests
-- `make list-issues` - Show all Gitea issues with status
-- `make show-issue NUM=X` - Show detailed view of specific issue
+- Tea CLI: `tea issues list` - Show all Gitea issues with status
+- Tea CLI: `tea issue show NUM` - Show detailed view of specific issue
 
 ### Workspace Management Understanding
-You understand the workspace structure (default: `.tddai_workspace/`, configurable per project):
+You understand the project structure with issue-facade for issue management:
 ```
 {workspace_dir}/
 ├── current_issue.json          # Active issue metadata
@@ -152,7 +152,7 @@ You understand the workspace structure (default: `.tddai_workspace/`, configurab
 
 ### TDDAi Framework Components
 **Core Infrastructure:**
-- `tddai/` - TDD workflow framework
+- `issue-facade/` - Universal issue management facade
   - `workspace.py` - Workspace management
   - `issue_fetcher.py` - Issue API integration
   - `issue_writer.py` - Issue updates via PATCH