Files
resolutionflow/backend
chihlasm 0f750e63e0 feat(notifications): add Phase 4 Slice 2 — multi-channel notification system
Full notification infrastructure with in-app, email, Slack, and Teams channels:

Backend:
- NotificationConfig, NotificationLog, Notification models + migration
- Notification service with event routing, channel delivery, retry logic
- 9 API endpoints (config CRUD + in-app notifications)
- APScheduler retry job with exponential backoff (30s, 2m, 10m)
- Wired into escalation, proposal approval, and knowledge flywheel
- Pydantic event key validation, cross-tenant protection on recipients

Frontend:
- TypeScript types + API client for all notification endpoints
- NotificationsPanel: bell icon with unread badge, dropdown, mark-read
- NotificationSettings: channel config, event toggles, test, delete confirm
- Notifications tab on IntegrationsPage
- ARIA attributes, Escape handler, settings link on panel

Review fixes (13 issues resolved):
- notify() no longer commits/rolls back caller's transaction (critical)
- retry_failed_notifications returns count instead of None (critical)
- NotificationSettings moved inside dedicated tab (critical)
- target_user_ids scoped by account_id (security)
- Email loop collects all failures before raising
- Slack webhook validates response body
- events_enabled rejects unknown event keys
- link column widened to String(500)
- Dead code removed from _auto_reinforce
- Delete confirmation, ARIA, Escape key support

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 12:37:54 +00:00
..

Troubleshooting Decision Tree - Backend API

FastAPI backend for the Troubleshooting Decision Tree application.

Quick Start

1. Set up Python environment

cd backend
python -m venv venv

# Windows
venv\Scripts\activate

# macOS/Linux
source venv/bin/activate

pip install -r requirements.txt

2. Start PostgreSQL database

Using Docker:

docker-compose up -d

Or install PostgreSQL locally and create a database:

CREATE DATABASE decision_tree;

3. Configure environment

Copy the example env file and update as needed:

cp .env.example .env

4. Run database migrations

alembic upgrade head

5. Start the server

uvicorn app.main:app --reload --host 0.0.0.0 --port 8000

The API will be available at:

API Endpoints

Authentication

  • POST /api/v1/auth/register - Register new user
  • POST /api/v1/auth/login - Login (form data)
  • POST /api/v1/auth/login/json - Login (JSON body)
  • POST /api/v1/auth/refresh - Refresh token
  • GET /api/v1/auth/me - Get current user
  • POST /api/v1/auth/logout - Logout

Trees

  • GET /api/v1/trees - List all trees
  • GET /api/v1/trees/categories - List categories
  • GET /api/v1/trees/search?q=query - Search trees
  • GET /api/v1/trees/{id} - Get specific tree
  • POST /api/v1/trees - Create tree (engineer/admin)
  • PUT /api/v1/trees/{id} - Update tree (engineer/admin)
  • DELETE /api/v1/trees/{id} - Delete tree (admin)

Sessions

  • GET /api/v1/sessions - List user's sessions
  • GET /api/v1/sessions/{id} - Get specific session
  • POST /api/v1/sessions - Start new session
  • PUT /api/v1/sessions/{id} - Update session
  • POST /api/v1/sessions/{id}/complete - Complete session
  • POST /api/v1/sessions/{id}/export - Export session

Development

Create new migration

alembic revision --autogenerate -m "description"

Run migrations

alembic upgrade head

Rollback migration

alembic downgrade -1

Project Structure

backend/
├── alembic/              # Database migrations
│   └── versions/
├── app/
│   ├── api/
│   │   ├── endpoints/    # API route handlers
│   │   ├── deps.py       # Dependencies (auth, etc.)
│   │   └── router.py     # Main router
│   ├── core/
│   │   ├── config.py     # Settings
│   │   ├── database.py   # DB connection
│   │   └── security.py   # JWT, password hashing
│   ├── models/           # SQLAlchemy models
│   ├── schemas/          # Pydantic schemas
│   └── main.py           # FastAPI app
├── tests/
├── alembic.ini
├── docker-compose.yml
├── requirements.txt
└── README.md