NeuroBoost

https://github.com/zemdenalex/neuroboost
Admin
A complete project skeleton for NeuroBoost v0.4.0, featuring a Go backend, React frontend, database...
Tokens:30,530
Snippets:72
Trust Score:4.5
Update:11 months ago
Show doc for...
Tokens:
Raw
### Router Setup and API Endpoints

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Details the configuration of the Chi router, including middleware like logging, recovery, and CORS, and lists the public and protected API endpoints for authentication, events, and tasks.

```APIDOC
## Router Setup and API Endpoints

### Description
This section outlines the setup of the Chi router, including the application of essential middleware such as logging, recovery, and CORS. It also details the available API endpoints, categorized into public routes (accessible without authentication) and protected routes (requiring JWT authentication).

### Middleware Applied:

*   **Logger**: Logs incoming requests.
*   **Recoverer**: Recovers from panics.
*   **CORS**: Configured to allow all origins, common methods (GET, POST, PATCH, DELETE, OPTIONS), all headers, allow credentials, and a max age of 300 seconds.
*   **JWTMiddleware**: Protects specific routes by validating JWTs.

### Public Routes:

#### GET /api/health

*   **Description**: Health check endpoint.
*   **Method**: GET
*   **Endpoint**: `/api/health`
*   **Parameters**: None
*   **Request Body**: None
*   **Success Response (200)**: `{"status":"ok","service":"neuroboost-api","version":"0.4.0-skeleton"}`

#### POST /api/auth/telegram

*   **Description**: Handles Telegram authentication.
*   **Method**: POST
*   **Endpoint**: `/api/auth/telegram`
*   **Parameters**: None
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### GET /api/auth/me

*   **Description**: Retrieves current authenticated user information.
*   **Method**: GET
*   **Endpoint**: `/api/auth/me`
*   **Parameters**: None
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### POST /api/auth/logout

*   **Description**: Handles user logout.
*   **Method**: POST
*   **Endpoint**: `/api/auth/logout`
*   **Parameters**: None
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

### Protected Routes (Requires JWT Authentication):

#### GET /api/events

*   **Description**: Lists all events.
*   **Method**: GET
*   **Endpoint**: `/api/events`
*   **Parameters**: None
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### POST /api/events

*   **Description**: Creates a new event.
*   **Method**: POST
*   **Endpoint**: `/api/events`
*   **Parameters**: None
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### GET /api/events/{id}

*   **Description**: Retrieves a specific event by its ID.
*   **Method**: GET
*   **Endpoint**: `/api/events/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### PATCH /api/events/{id}

*   **Description**: Updates an existing event by its ID.
*   **Method**: PATCH
*   **Endpoint**: `/api/events/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### DELETE /api/events/{id}

*   **Description**: Deletes an event by its ID.
*   **Method**: DELETE
*   **Endpoint**: `/api/events/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### PATCH /api/events/{id}/move

*   **Description**: Moves an event.
*   **Method**: PATCH
*   **Endpoint**: `/api/events/{id}/move`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### PATCH /api/events/{id}/resize

*   **Description**: Resizes an event.
*   **Method**: PATCH
*   **Endpoint**: `/api/events/{id}/resize`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### POST /api/events/{id}/exceptions

*   **Description**: Adds an exception to an event.
*   **Method**: POST
*   **Endpoint**: `/api/events/{id}/exceptions`
*   **Path Parameters**: `id` (uuid) - The ID of the event.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### GET /api/tasks

*   **Description**: Lists all tasks.
*   **Method**: GET
*   **Endpoint**: `/api/tasks`
*   **Parameters**: None
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### POST /api/tasks

*   **Description**: Creates a new task.
*   **Method**: POST
*   **Endpoint**: `/api/tasks`
*   **Parameters**: None
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### GET /api/tasks/{id}

*   **Description**: Retrieves a specific task by its ID.
*   **Method**: GET
*   **Endpoint**: `/api/tasks/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the task.
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### PATCH /api/tasks/{id}

*   **Description**: Updates an existing task by its ID.
*   **Method**: PATCH
*   **Endpoint**: `/api/tasks/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the task.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

#### DELETE /api/tasks/{id}

*   **Description**: Deletes a task by its ID.
*   **Method**: DELETE
*   **Endpoint**: `/api/tasks/{id}`
*   **Path Parameters**: `id` (uuid) - The ID of the task.
*   **Request Body**: None
*   **Success Response (200)**: Details not provided in source.

#### POST /api/tasks/{id}/schedule

*   **Description**: Schedules a task.
*   **Method**: POST
*   **Endpoint**: `/api/tasks/{id}/schedule`
*   **Path Parameters**: `id` (uuid) - The ID of the task.
*   **Request Body**: Details not provided in source.
*   **Success Response (200)**: Details not provided in source.

### Server Configuration:
*   **Host**: `localhost`
*   **Port**: `8080`
```

--------------------------------

### Deployment Commands and Health Checks

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Complete deployment workflow with environment setup, service orchestration, health monitoring, and troubleshooting commands. Includes JWT generation, service health verification, and data persistence management.

```Bash
# Copy environment template
cp .env.example .env

# Edit .env with your configuration
nano .env

# Generate JWT secret
openssl rand -hex 32

# Start all services
docker-compose up -d

# View logs
docker-compose logs -f api
docker-compose logs -f web
docker-compose logs -f db

# Check health
curl http://localhost:8080/api/health

# Access application
# Frontend: http://localhost:5173
# API: http://localhost:8080/api/*
# Database: localhost:5432

# Stop services
docker-compose down

# Stop and remove volumes
docker-compose down -v
```

--------------------------------

### Multi-Container Deployment Configuration

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Docker Compose setup orchestrating database, API, and web services. Includes health checks, volume management, and network isolation. Handles PostgreSQL initialization, API backend build, and frontend deployment with proper service dependencies.

```YAML
version: '3.8'

services:
  db:
    image: postgres:16-alpine
    container_name: neuroboost-db
    environment:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_DB: ${POSTGRES_DB}
    ports:
      - "127.0.0.1:5432:5432"
    volumes:
      - db-data:/var/lib/postgresql/data
      - ./neuroboost-api-go/migrations:/docker-entrypoint-initdb.d:ro
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER}"]
      interval: 10s
      timeout: 5s
      retries: 5
    restart: unless-stopped
    networks:
      - neuroboost_network

  api:
    build:
      context: ./neuroboost-api-go
      dockerfile: Dockerfile
    container_name: neuroboost-api
    environment:
      DATABASE_URL: postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}?sslmode=disable
      JWT_SECRET: ${JWT_SECRET}
      API_PORT: "8080"
    depends_on:
      db:
        condition: service_healthy
    ports:
      - "127.0.0.1:8080:8080"
    restart: unless-stopped
    networks:
      - neuroboost_network

  web:
    build:
      context: ./neuroboost-web
      dockerfile: Dockerfile
      args:
        VITE_API_URL: ${FRONTEND_URL}/api
    container_name: neuroboost-web
    ports:
      - "127.0.0.1:5173:80"
    restart: unless-stopped
    networks:
      - neuroboost_network

networks:
  neuroboost_network:
    driver: bridge

volumes:
  db-data:
    name: neuroboost_db_data
```

--------------------------------

### Router Setup with Middleware (Go)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Configures the Chi router for the API, including essential middleware like logging, recovery, and CORS. It defines public routes for health checks and authentication, and sets up a protected group using the JWT middleware for API endpoints.

```Go
// File: neuroboost-api-go/cmd/api/main.go

package main

import (
    "log"
    "net/http"

    "github.com/go-chi/chi/v5"
    "github.com/go-chi/chi/v5/middleware"
    "github.com/go-chi/cors"

    "neuroboost-api/internal/auth"
    "neuroboost-api/internal/events"
    "neuroboost-api/internal/tasks"
    mw "neuroboost-api/internal/middleware"
)

func main() {
    r := chi.NewRouter()

    // Middleware
    r.Use(middleware.Logger)
    r.Use(middleware.Recoverer)
    r.Use(cors.Handler(cors.Options{
        AllowedOrigins:   []string{"*"},
        AllowedMethods:   []string{"GET", "POST", "PATCH", "DELETE", "OPTIONS"},
        AllowedHeaders:   []string{"*"},
        AllowCredentials: true,
        MaxAge:           300,
    }))

    // Public routes
    r.Get("/api/health", HealthHandler)
    r.Post("/api/auth/telegram", auth.LoginHandler)
    r.Get("/api/auth/me", auth.MeHandler)
    r.Post("/api/auth/logout", auth.LogoutHandler)

    // Protected routes
    r.Group(func(r chi.Router) {
        r.Use(mw.JWTMiddleware)

        // Events
        r.Get("/api/events", events.ListHandler)
        r.Post("/api/events", events.CreateHandler)
        r.Get("/api/events/{id}", events.GetHandler)
        r.Patch("/api/events/{id}", events.UpdateHandler)
        r.Delete("/api/events/{id}", events.DeleteHandler)
        r.Patch("/api/events/{id}/move", events.MoveHandler)
        r.Patch("/api/events/{id}/resize", events.ResizeHandler)
        r.Post("/api/events/{id}/exceptions", events.AddExceptionHandler)

        // Tasks
        r.Get("/api/tasks", tasks.ListHandler)
        r.Post("/api/tasks", tasks.CreateHandler)
        r.Get("/api/tasks/{id}", tasks.GetHandler)
        r.Patch("/api/tasks/{id}", tasks.UpdateHandler)
        r.Delete("/api/tasks/{id}", tasks.DeleteHandler)
        r.Post("/api/tasks/{id}/schedule", tasks.ScheduleHandler)
    })

    log.Println("Server starting on :8080")
    if err := http.ListenAndServe(":8080", r); err != nil {
        log.Fatal(err)
    }
}

func HealthHandler(w http.ResponseWriter, r *http.Request) {
    w.Header().Set("Content-Type", "application/json")
    w.WriteHeader(http.StatusOK)
    w.Write([]byte(`{"status":"ok","service":"neuroboost-api","version":"0.4.0-skeleton"}`))
}
```

--------------------------------

### GET /api/opportunities

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves a list of all opportunities for the authenticated user. This endpoint helps in reviewing tracked opportunities with their statuses and tags. Authentication via Bearer token is required.

```APIDOC
## GET /api/opportunities

### Description
Lists all opportunities associated with the authenticated user for overview and management.

### Method
GET

### Endpoint
/api/opportunities

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
None

### Request Example
None

### Response
#### Success Response (200)
- **opportunities** (array) - List of opportunity objects with id, user_id, title, description, status, tags, created_at, updated_at

#### Response Example
```json
{
  "opportunities": [
    {
      "id": "f6a7b8c9-d0e1-9234-5f01-267890123456",
      "user_id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Speaking at PyCon 2026",
      "description": "Invited to give 30-minute talk on async patterns",
      "status": "ACTIVE",
      "tags": ["speaking", "python", "conference"],
      "created_at": "2025-11-10T17:00:00Z",
      "updated_at": "2025-11-10T17:00:00Z"
    }
  ]
}
```
```

--------------------------------

### Create Planning Graph Node using cURL

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Demonstrates how to create new nodes (e.g., DREAM, GOAL) in the planning graph using cURL POST requests. It shows example payloads for different node types and the expected response structure.

```bash
# Create dream node
curl -X POST http://localhost:8080/api/planning/nodes \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "DREAM",
    "title": "Build successful tech startup",
    "description": "Create profitable SaaS product helping developers",
    "metadata": {
      "timeframe": "10 years",
      "estimated_revenue": "1M ARR"
    }
  }'

# Create goal node
curl -X POST http://localhost:8080/api/planning/nodes \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "GOAL",
    "title": "Launch MVP product",
    "description": "Build and ship first version with 3 core features",
    "metadata": {
      "timeframe": "3 months",
      "deadline": "2026-02-01"
    }
  }'
```

--------------------------------

### Create Planning Graph Edge using cURL

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Illustrates how to establish relationships (edges) between planning graph nodes using cURL POST requests. Examples include 'DERIVES' and 'BLOCKED_BY' relationships with specified source, destination, and weight.

```bash
# Create "derives from" edge (goal derives from dream)
curl -X POST http://localhost:8080/api/planning/edges \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{
    "src": "c5d6e7f8-a9b0-8123-4890-156789012345",
    "dst": "f2a3b4c5-d6e7-5890-1567-823456789012",
    "kind": "DERIVES",
    "weight": 1
  }'

# Create "blocked by" edge (task blocked by another)
curl -X POST http://localhost:8080/api/planning/edges \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{
    "src": "b4c5d6e7-f8a9-7012-3789-045678901234",
    "dst": "a3b4c5d6-e7f8-6901-2678-934567890123",
    "kind": "BLOCKED_BY",
    "weight": 2
  }'
```

--------------------------------

### Retrieve Planning Graph DAG (GET API)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Fetches the complete directed acyclic graph (DAG) representing the planning structure. This endpoint provides nodes and edges necessary for visualizing or processing the planning graph.

```bash
curl http://localhost:8080/api/planning/graph \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### GET /api/planning/graph

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves the complete planning directed acyclic graph (DAG), including all nodes and edges.

```APIDOC
## GET /api/planning/graph

### Description
Retrieves the complete planning directed acyclic graph (DAG) with its nodes and edges.

### Method
GET

### Endpoint
/api/planning/graph

### Response
#### Success Response (200)
- The response will contain the structured data of the planning DAG, including nodes and edges. (Specific schema to be detailed)

#### Response Example
```json
{
  "nodes": [
    { "id": "node1", "label": "Task A" },
    { "id": "node2", "label": "Task B" }
  ],
  "edges": [
    { "source": "node1", "target": "node2", "label": "depends on" }
  ]
}
```
```

--------------------------------

### List Opportunities - Bash curl

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This curl command lists all opportunities for the authenticated user via a GET request. It needs a JWT token for authorization and no additional inputs. The output is a JSON array of opportunity objects with details like ID, title, description, status, tags, and timestamps. Returns an empty array if no opportunities exist for the user.

```bash
curl http://localhost:8080/api/opportunities \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### Base API Client: HTTP Request Wrapper (TypeScript)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

A base HTTP request wrapper that constructs URLs based on environment variables. It includes stubbed fetch logic and helper functions for GET, POST, PATCH, and DELETE requests. Dependencies include environment variables for the base API URL.

```typescript
// File: neuroboost-web/src/lib/api.ts

const BASE_URL = import.meta.env.VITE_API_URL ?? '/api'

async function request(method: string, url: string, body?: any) {
  const fullUrl = url.startsWith('/')
    ? `${BASE_URL}${url}`
    : `${BASE_URL}/${url.replace(/^\/,'')}`

  console.log('[API STUB]', method, fullUrl, body ?? null)

  // TODO: Implement real fetch
  // const response = await fetch(fullUrl, {
  //   method,
  //   headers: {
  //     'Content-Type': 'application/json',
  //     'Authorization': `Bearer ${getToken()}`
  //   },
  //   body: body ? JSON.stringify(body) : undefined
  // })
  // return await response.json()

  return { data: null } // Stub response
}

export async function get(url: string) {
  return request('GET', url)
}

export async function post(url: string, body: any) {
  return request('POST', url, body)
}

export async function patch(url: string, body: any) {
  return request('PATCH', url, body)
}

export async function del(url: string) {
  return request('DELETE', url)
}

```

--------------------------------

### GET /api/tasks

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves a list of all tasks associated with the authenticated user. This endpoint supports task management by providing an overview of open, in-progress, and completed tasks. Authentication via Bearer token is required.

```APIDOC
## GET /api/tasks

### Description
Fetches all tasks for the currently authenticated user, including details like status and timestamps.

### Method
GET

### Endpoint
/api/tasks

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
None

### Request Example
None

### Response
#### Success Response (200)
- **tasks** (array) - List of task objects, each containing id, user_id, title, description, status, priority, estimated_minutes, opportunity_id, created_at, updated_at

#### Response Example
```json
{
  "tasks": [
    {
      "id": "a7b8c9d0-e1f2-0345-6012-378901234567",
      "user_id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Complete API documentation",
      "description": "Write comprehensive API docs with examples",
      "status": "IN_PROGRESS",
      "priority": 8,
      "estimated_minutes": 180,
      "opportunity_id": null,
      "created_at": "2025-11-10T15:00:00Z",
      "updated_at": "2025-11-10T16:00:00Z"
    },
    {
      "id": "b8c9d0e1-f2a3-1456-7123-489012345678",
      "user_id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Review pull requests",
      "description": null,
      "status": "OPEN",
      "priority": 5,
      "estimated_minutes": 60,
      "opportunity_id": null,
      "created_at": "2025-11-10T14:00:00Z",
      "updated_at": "2025-11-10T14:00:00Z"
    }
  ]
}
```
```

--------------------------------

### List Reflections by Event ID (GET API)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves all reflection entries associated with a specific event ID. This endpoint takes the event ID as a query parameter and returns a list of reflection objects.

```bash
curl "http://localhost:8080/api/reflections?event_id=c9d0e1f2-a3b4-2567-8234-590123456789" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### List Tasks - Bash curl

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This curl command retrieves all tasks for the authenticated user via a GET request. It requires a JWT token in the Authorization header for user authentication and has no additional input parameters. The output is a JSON array of task objects, each with details like ID, status, and timestamps. It assumes the user has existing tasks; otherwise, an empty array is returned.

```bash
curl http://localhost:8080/api/tasks \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### Create Event API Endpoint

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This endpoint allows for the creation of new calendar events. It supports specifying event details such as title, start and end times, timezone, color, and tags. It requires JWT authentication and accepts event data in JSON format. Recurrence rules can also be included.

```bash
# Create one-time event
curl -X POST http://localhost:8080/api/events \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{ \
    "title": "Project Review Meeting",
    "starts_at": "2025-11-12T14:00:00Z",
    "ends_at": "2025-11-12T15:30:00Z",
    "all_day": false,
    "tz": "America/New_York",
    "color": "#EF4444",
    "tags": ["work", "meetings", "project-alpha"]
  }'
```

--------------------------------

### Create Need - Bash curl

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This curl command creates a new personal need via a POST request. It depends on JWT authorization and JSON input with title, due date, and satisfaction status. The output would be a JSON object representing the created need, but the example is incomplete. Assumes the API handles due dates as strings and satisfies field as boolean.

```bash
curl -X POST http://localhost:8080/api/needs \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Exercise 3x per week",
    "due_date": "2025-11-17",
    "satisfied": false
  }'
```

--------------------------------

### Get Alert Status for Patterns (GET API)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Checks the crisis detection status and estimates days until potential burnout for a specific user. The user ID is passed as a query parameter. It returns the alert level and relevant recommendations.

```bash
curl "http://localhost:8080/api/patterns/alert-status?user_id=550e8400-e29b-41d4-a716-446655440000" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### Build Secure Go API with Multi-Stage Dockerfile

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This multi-stage Dockerfile builds a Go application using Alpine, then runs it in a distroless image for security. It requires Go 1.22 and distroless base. Inputs are Go source files and go.mod; outputs a containerized API binary. It's optimized for size and security but requires careful handling of CA certificates in distroless.

```dockerfile
# File: neuroboost-api-go/Dockerfile

FROM golang:1.22-alpine AS build
WORKDIR /app

# Install dependencies
RUN apk add --no-cache git ca-certificates

# Download Go modules
COPY go.mod ./
RUN go mod download || true

# Copy source
COPY . .
RUN go mod tidy

# Build binary
RUN CGO_ENABLED=0 GOOS=linux go build \
    -trimpath \
    -ldflags="-s -w" \
    -o /api \
    ./cmd/api

# Runtime stage
FROM gcr.io/distroless/static-debian12:nonroot
WORKDIR /srv
COPY --from=build /api /srv/api

USER nonroot:nonroot
EXPOSE 8080

ENTRYPOINT ["/srv/api"]
```

--------------------------------

### Get Weekly Pattern Metrics (GET API)

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves weekly pattern analytics for a given user ID. This includes metrics like completion rate, mood impact, energy impact, and time accuracy. The user ID is provided as a query parameter.

```bash
curl "http://localhost:8080/api/patterns/metrics?user_id=550e8400-e29b-41d4-a716-446655440000" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
```

--------------------------------

### Environment Variables Template

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Configuration template for deployment with database credentials, JWT secret generation, API settings, and external integrations. Includes documentation for required values and security considerations.

```Bash
# File: .env.example

# Database Configuration
POSTGRES_USER=neuroboost
POSTGRES_PASSWORD=CHANGE_THIS_STRONG_PASSWORD
POSTGRES_DB=neuroboost

# API Configuration
JWT_SECRET=GENERATE_WITH_openssl_rand_hex_32
NODE_ENV=production
FRONTEND_URL=https://neuroboost.website

# Telegram Integration
TELEGRAM_BOT_TOKEN=YOUR_MAIN_BOT_TOKEN
TELEGRAM_NOTIFICATION_BOT_TOKEN=YOUR_NOTIFICATION_BOT_TOKEN

# Optional: Context7 API
# CONTEXT7_API_KEY=your_api_key_from_context7.com
```

--------------------------------

### GET /api/health

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Provides a simple health check to verify that the NeuroBoost service is running and reachable.

```APIDOC
## GET /api/health

### Description
Basic health verification endpoint for monitoring service availability.

### Method
GET

### Endpoint
/api/health

### Parameters

#### Path Parameters
- *(none)*

#### Query Parameters
- *(none)*

#### Request Body
- *(none)*

### Request Example
{
  "status": "ok",
  "service": "neuroboost-api",
  "version": "0.4.0-skeleton"
}

### Response
#### Success Response (200)
- **status** (string) - Service health status
- **service**string) - Service name
- **version** (string) - API version

#### Response Example
{
  "status": "ok",
  "service": "neuroboost-api",
  "version": "0.4.0-skeleton"
}
```

--------------------------------

### Build Node.js Frontend with Nginx Dockerfile

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This multi-stage Dockerfile builds a Node.js application using pnpm, then serves it with Nginx. It requires Node 22 and pnpm. Inputs are package.json and source; outputs a static site in Nginx. It's efficient for production but assumes build scripts are defined in package.json.

```dockerfile
# File: neuroboost-web/Dockerfile

FROM node:22-alpine AS builder
WORKDIR /app

# Install pnpm
RUN npm i -g pnpm@9

# Install dependencies
COPY package.json ./
RUN pnpm install

# Build application
COPY . .
RUN pnpm build

# Runtime stage
FROM nginx:stable-alpine

# Remove default nginx content
RUN rm -rf /usr/share/nginx/html/*

# Copy built application
COPY --from=builder /app/dist /usr/share/nginx/html

EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]
```

--------------------------------

### GET /api/events

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Lists calendar events for the authenticated user with optional date‑range filtering via query parameters.

```APIDOC
## GET /api/events

### Description
Retrieve calendar events for the authenticated user. Supports optional `from` and `to` query parameters to filter events by date range.

### Method
GET

### Endpoint
/api/events

### Parameters

#### Path Parameters
- *(none)*

#### Query Parameters
- **from** (string) - Optional - ISO8601 start datetime for filtering events.
- **to** (string) - Optional - ISO8601 end datetime for filtering events.

#### Request Body
- *(none)*

### Request Example
GET /api/events?from=2025-11-10T00:00:00Z&to=2025-11-17T23:59:59Z
Headers:
Authorization: Bearer <jwt-token>

### Response
#### Success Response (200)
- **events** (array) - List of event objects.
  - **id** (string) - Event UUID.
  - **user_id** (string) - Owner user UUID.
  - **title** (string) - Event title.
  - **starts_at** (string) - ISO start datetime.
  - **ends_at** (string) - ISO end datetime.
  - **all_day** (boolean) - Indicates if the event spans the whole day.
  - **tz** (string) - Timezone.
  - **rrule** (string|null) - Recurrence rule if applicable.
  - **color** (string) - Hex color code for UI.
  - **tags** (array) - List of tag strings.
  - **task_id** (string|null) - Associated task UUID.
  - **created_at** (string) - ISO creation timestamp.
  - **updated_at** (string) - ISO last update timestamp.

#### Response Example
{
  "events": [
    {
      "id": "a1b2c3d4-e5f6-4789-0abc-def123456789",
      "user_id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Team Standup",
      "starts_at": "2025-11-11T09:00:00Z",
      "ends_at": "2025-11-11T09:30:00Z",
      "all_day": false,
      "tz": "America/New_York",
      "rrule": "FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR",
      "color": "#3B82F6",
      "tags": ["work", "meetings"],
      "task_id": null,
      "created_at": "2025-11-10T10:00:00Z",
      "updated_at": "2025-11-10T10:00:00Z"
    },
    {
 "id": "b2c3d4e5-f6a7-5890-1bcd-ef0234567890",
      "user_id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Deep Work Session",
      "starts_at": "2025-11-11T10:00:00Z",
      "ends_at": "2025-11-11T12:00:00Z",
      "all_day": false,
      "tz": "America/New_York",
      "rrule": null,
      "color": "#10B981",
      "tags": ["focus", "coding"],
      "task_id": "c3d4e5f6-a7b8-6901-2cde-f03456789012",
      "created_at": "2025-11-10T11:00:00Z",
      "updated_at": "2025-11-10T11:00:00Z"
    }
  ]
}
```

--------------------------------

### GET /api/auth/me

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Retrieves information about the currently authenticated user. Requires a valid JWT token in the Authorization header.

```APIDOC
## GET /api/auth/me

### Description
Retrieve authenticated user information. The request must include a valid JWT token.

### Method
GET

### Endpoint
/api/auth/me

### Parameters

#### Path Parameters
- *(none)*

#### Query Parameters
- *(none)*

#### Request Body
- *(none)*

### Request Example
Headers:
Authorization: Bearer <jwt-token>

### Response
#### Success Response (200)
- **id** (string) - Internal user UUID.
- **tg_id** (string) - Telegram user ID.
- **email** (string|null) - User email address.
- **created_at** (string) - ISO timestamp of user creation.

#### Response Example
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "tg_id": "279058397",
  "email": "user@example.com",
  "created_at": "2025-11-10T10:00:00Z"
}
```

--------------------------------

### POST /api/tasks

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Creates a new task. Supports setting title, description, priority, and estimated time.

```APIDOC
## POST /api/tasks

### Description
Create a new task with priority and optional linkage to opportunities.

### Method
POST

### Endpoint
/api/tasks

### Parameters
#### Request Body
- **title** (string) - Required - The title of the task.
- **description** (string) - Optional - A detailed description of the task.
- **priority** (integer) - Optional - The priority level of the task (e.g., 1-10).
- **estimated_minutes** (integer) - Optional - The estimated time to complete the task in minutes.
- **opportunity_id** (string) - Optional - The ID of the opportunity this task is related to.

### Request Example
```json
{
  "title": "Complete API documentation",
  "description": "Write comprehensive API docs with examples",
  "priority": 8,
  "estimated_minutes": 180
}
```

### Response
#### Success Response (200 or 201)
- **id** (string) - The unique identifier for the created task.
- **title** (string) - The title of the task.
- **description** (string) - The description of the task.
- **priority** (integer) - The priority level of the task.
- **estimated_minutes** (integer) - The estimated time to complete the task.
- **opportunity_id** (string | null) - The ID of the related opportunity.
- **created_at** (string) - The timestamp when the task was created.
- **updated_at** (string) - The timestamp when the task was last updated.

#### Response Example
```json
{
  "id": "a1b2c3d4-e5f6-7890-1234-567890abcdef",
  "title": "Complete API documentation",
  "description": "Write comprehensive API docs with examples",
  "priority": 8,
  "estimated_minutes": 180,
  "opportunity_id": null,
  "created_at": "2025-11-10T15:00:00Z",
  "updated_at": "2025-11-10T15:00:00Z"
}
```
```

--------------------------------

### Database Migration Schemas

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Provides the SQL schema definitions for PostgreSQL migrations, including tables for users and tasks.

```APIDOC
## Database Migration Schemas

### Description
These SQL scripts define the database schema for PostgreSQL, including the creation of tables for users and tasks, along with their respective fields, constraints, and indexes. These migrations run automatically on container startup.

### Tables:

#### `user` table

*   **id** (uuid) - Primary Key, defaults to `gen_random_uuid()`.
*   **tg_id** (text) - Unique identifier.
*   **email** (text) - User's email address.
*   **created_at** (timestamptz) - Timestamp of creation, defaults to `now()`.

**Indexes:**
*   `user_tg_id_idx` on `tg_id`.

#### `task` table

*   **id** (uuid) - Primary Key, defaults to `gen_random_uuid()`.
*   **user_id** (uuid) - Foreign Key referencing `user(id)`, NOT NULL, ON DELETE CASCADE.
*   **title** (text) - Task title, NOT NULL.
*   **description** (text) - Task description.
*   **status** (text) - Task status, defaults to 'OPEN'.
*   **priority** (integer) - Task priority, defaults to 0.
*   **estimated_minutes** (integer) - Estimated time in minutes.
*   **opportunity_id** (uuid) - Foreign Key referencing `opportunity(id)`, ON DELETE SET NULL.
*   **created_at** (timestamptz) - Timestamp of creation, defaults to `now()`.
*   **updated_at** (timestamptz) - Timestamp of last update, defaults to `now()`.

**Indexes:**
*   `task_user_status_idx` on `user_id`, `status`.
*   `task_user_priority_idx` on `user_id`, `priority`.
*   `task_opportunity_idx` on `opportunity_id`.

### Method
SQL DDL statements.

### Endpoint
Not applicable.

### Parameters
Not applicable.

### Request Example
Not applicable.

### Response
Database schema changes.

#### Success Response
Schema created/updated.

#### Response Example
None.
```

--------------------------------

### POST /api/planning/nodes

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

Creates a new node in the planning graph. Nodes can be of kind DREAM, GOAL, or TASK and include title, description and optional metadata.

```APIDOC
## POST /api/planning/nodes\n\n### Description\nCreates a new node in the planning graph. Nodes can be of kind DREAM, GOAL, or TASK and include title, description and optional metadata.\n\n### Method\nPOST\n\n### Endpoint\n/api/planning/nodes\n\n### Parameters\n#### Path Parameters\n*(none)*\n\n#### Query Parameters\n*(none)*\n\n#### Request Body\n- **kind** (string) - Required - The type of node (e.g., DREAM, GOAL, TASK).\n- **title** (string) - Required - Short title of the node.\n- **description** (string) - Optional - Detailed description.\n- **metadata** (object) - Optional - Additional key‑value pairs such as timeframe, deadline, etc.\n\n### Request Example\n{\n  "kind": "DREAM",\n  "title": "Build successful tech startup",\n  "description": "Create profitable SaaS product helping developers",\n  "metadata": {\n    "timeframe": "10 years",\n    "estimated_revenue": "1M ARR"\n  }\n}\n\n### Response\n#### Success Response (200)\n- **id** (string) - Identifier of the created node.\n- **user_id** (string) - Owner identifier.\n- **kind** (string) - Node type.\n- **title** (string) - Node title.\n- **description** (string) - Node description.\n- **metadata** (object) - Provided metadata.\n- **created_at** (string) - Timestamp of creation.\n- **updated_at** (string) - Timestamp of last update.\n\n### Response Example\n{\n  "id": "c5d6e7f8-a9b0-8123-4890-156789012345",\n  "user_id": "550e8400-e29b-41d4-a716-446655440000",\n  "kind": "GOAL",\n  "ref_id": null,\n  "title": "Launch MVP product",\n  "description": "Build and ship first version with 3 core features",\n  "metadata": {\n    "timeframe": "3 months",\n    "deadline": "2026-02-01"\n  },\n  "created_at": "2025-11-10T22:00:00Z",\n  "updated_at": "2025-11-10T22:00:00Z"\n}
```

--------------------------------

### Get Current User Authentication Endpoint

Source: https://context7.com/zemdenalex/neuroboost/llms.txt

This endpoint retrieves the details of the currently authenticated user. It requires a JWT in the Authorization header. The expected future response includes user ID, Telegram ID, email, and creation timestamp.

```bash
# Get current user (requires JWT)
curl http://localhost:8080/api/auth/me \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

# Expected future response
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "tg_id": "279058397",
  "email": "user@example.com",
  "created_at": "2025-11-10T10:00:00Z"
}
```
Tokens:
Raw