### Quick Start

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/planning/Project-KickOff-Preprations-CheckList.md

Guides for quickly getting started with ADPA using the CLI, API Server, or Admin Web Interface.

```APIDOC
## Quick Start

### 1. CLI Usage
```bash
# Generate project documentation
adpa generate --key project-charter --output ./docs

# Start the API server
adpa-api

# Initialize Confluence integration
adpa confluence init

# Initialize SharePoint integration  
adpa sharepoint init
```

### 2. API Server
```bash
# Start the Express.js API server
npm run api:start

# Access API documentation
open http://localhost:3000/api-docs
```

### 3. Admin Web Interface
```bash
# Install and start the admin interface
npm run admin:setup
npm run admin:serve

# Access at http://localhost:3001
```
```

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

### Setup and Serve ADPA Admin Interface

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/quality-assurance/bug-report.md

Install and start the admin web interface for ADPA.

```bash
# Install and start the admin interface
npm run admin:setup
npm run admin:serve

# Access at http://localhost:3001
```

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

### Install Server Dependencies and Start

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/01-getting-started/QUICK_START.md

Reinstall server dependencies and start the development server. Use this when the backend is not starting.

```powershell
cd server
npm ci
npm run dev
```

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

### Setup and Serve Admin Web Interface

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/planning/Project-KickOff-Preprations-CheckList.md

Install and start the ADPA admin web interface. Access it at http://localhost:3001.

```bash
npm run admin:setup
npm run admin:serve
```

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

### Install Frontend Dependencies and Start

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/01-getting-started/QUICK_START.md

Reinstall frontend dependencies and start the development server. Use this when the frontend is not loading.

```powershell
npm ci
npm run dev
```

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

### Basic Import Workflow Setup

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/roadmap/PROGRAMMATIC_IMPORT_DELIVERY.md

Initial setup for the import process. Includes setting the GitHub token and installing dependencies.

```bash
# 1. Setup (one-time)
export GITHUB_TOKEN=ghp_your_token_here
npm install
```

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

### Install Dependencies and Setup

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/01-getting-started/KNOWN_GOOD_LOCAL_RUNBOOK.md

Installs project dependencies and sets up local environment files. Ensure Node.js 18+ and pnpm are installed.

```bash
pnpm install
cd server && npm install && cd ..
cp .env.local.example .env.local
cp server/.env.example server/.env
```

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

### Setup Instructions

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/SEMANTIC-SEARCH-IMPLEMENTATION.md

Step-by-step guide to setting up the semantic search functionality, including database migrations, API key configuration, and initialization.

```APIDOC
## Setup Instructions

### Step 1: Apply Migration

```bash
cd server

# Apply the semantic search migration
supabase db push

# Or manually:
# psql -h <host> -U <user> -d <database> -f migrations/230_semantic_search_and_knowledge_base_optimization.sql
```

**Verify migration:**

```sql
-- Check embedding column exists
SELECT column_name FROM information_schema.columns 
WHERE table_name = 'knowledge_base_entries' AND column_name LIKE 'embedding%';

-- Check KB entry relationships table
SELECT * FROM information_schema.tables 
WHERE table_name = 'knowledge_base_entry_relationships';

-- Check indexes
SELECT indexname FROM pg_indexes 
WHERE tablename = 'knowledge_base_entries' 
AND indexname LIKE '%embedding%';
```

### Step 2: Ensure Voyage API Key

```bash
# In server/.env or environment variables
VOYAGE_API_KEY=<your-voyage-api-key>

# Get key from: https://www.voyageai.com/
# Free tier: 200M tokens/month
```

### Step 3: Initialize Semantic Search

```bash
# Option A: Via initialization script
cd server
node scripts/semantic-search-init.js

# Option B: Via npm script (add to package.json)
npm run semantic-search:init

# Option C: Manual initialization
npm run dev
```
```

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

### Setup Local Environment Variables

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/PIPELINE.md

Copy the example environment file to create a local configuration file. You will need to fill in specific values for your local setup.

```bash
cp .env.example .env.local
```

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

### Install and Run ADPA Project

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/README.md

Follow these steps to clone the repository, install dependencies, configure environment variables, and start the development servers for both the frontend and backend.

```bash
# 1. Clone repository
git clone <repository-url>
cd adpa

# 2. Install dependencies
pnpm install
cd server && npm install && cd ..

# 3. Configure environment
# Copy .env.example and add your Supabase/Railway credentials
cp .env.local.example .env.local
cp server/.env.example server/.env

# 4. Start development servers
# Frontend (terminal 1)
pnpm dev

# Backend (terminal 2)  
cd server && npm run dev

# 5. Access application
# Frontend: http://localhost:3005
# Backend:  http://localhost:5000/health
```

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

### Setup for GitHub Issues Import

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/roadmap/QUICK_REFERENCE_IMPORT.md

Follow these steps for a one-time setup: obtain a GitHub token with 'repo' scope, set it as an environment variable, and install dependencies.

```bash
# 1. Get GitHub Token
# Go to: https://github.com/settings/tokens/new
# Scopes: ✅ repo

# 2. Set Environment Variable
export GITHUB_TOKEN=ghp_your_token_here

# 3. Install Dependencies
npm install
```

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

### Starting the Backend Development Server

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/03-development/migrations/MIGRATION_208_COMPLETE.md

Use this command to start the backend server in development mode. Ensure you have the project dependencies installed.

```bash
# Start the backend
npm run dev
```

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

### Setup ADPA Admin Web Interface

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/planning/Project-KickOff-Preprations-CheckList.md

Installs necessary dependencies and prepares the admin web interface for ADPA.

```bash
npm run admin:setup
```

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

### Set Up Environment Variables

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/03-development/DOCKER_DEVELOPMENT_GUIDE.md

Copy the example environment file and customize it with your specific configuration variables.

```bash
cp .env.example .env
# Edit .env with your configuration
```

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

### Nixpacks Build Output

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/04-deployment/RAILWAY_DEPLOYMENT_EXPLAINED.md

Shows the output from Nixpacks, indicating the detected stack and the commands executed for setup, install, build, and start. This is the simpler, auto-generated method preferred for clean installs.

```text
╔═══════════ Nixpacks v1.38.0 ══════════╗
║ setup      │ nodejs_20                ║
║ install    │ cd server && npm install ║
║ build      │ cd server && npm install ║
║ start      │ cd server && npm start   ║
╚═══════════════════════════════════════╝
```

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

### Full Deployment Sequence - Setup and Migration

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/NPM-MIGRATION-SCRIPT-GUIDE.md

Steps to set up environment variables, navigate to the server directory, and run the migration script. Ensure all environment variables are correctly exported.

```bash
# 1. Navigate to server directory
cd server
```

```bash
# 2. Export environment variables
export DB_HOST=your-host
export DB_USER=postgres
export DB_PASSWORD=your-password
export DB_NAME=your-db
export DB_SSL=true
export VOYAGE_API_KEY=your-key
```

```bash
# 3. Run migration
npm run migrate:230
```

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

### Deploy Now Steps

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/DEPLOYMENT_AUTHORIZED.md

Recommended steps for deploying the project immediately. This path involves a minimal code change and verification of the startup summary.

```bash
1. Make 2-line change in server.ts
2. Run: npm run dev
3. Verify startup summary
4. Deploy to production
5. Done! Enjoy 50% faster startup 🎉
```

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

### Retrieve Template API Request

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/quality-assurance/test-environment.md

Example of a GET request to retrieve a specific template by its ID. Proper GUID validation is expected.

```http
GET /api/v1/templates/ca8d4758-03c5-4110-84a7-2f5bcd318539
```

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

### Verify Startup Summary

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/OPTIMIZED_INTEGRATION_GUIDE.md

After starting the server, verify that the startup summary appears and lists all 6 dependencies as initialized.

```bash
# 1. Start the server
npm run dev

# 2. Verify startup summary appears (should show all 6 dependencies)
```

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

### Quick Start: Get Task Cost via cURL

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/features/legacy-06-features/task-costing/TASK_COST_SUMMARY.md

This example shows how to retrieve the complete cost breakdown for a specific task using a cURL command. The expected JSON response structure is also provided.

```bash
curl http://localhost:5000/api/tasks/550e8400-e29b-41d4-a716-446655440000/cost

# Response
{
  "success": true,
  "data": {
    "taskId": "...",
    "taskName": "Implement Payment Gateway",
    "plannedTotalCost": 14650,
    "actualTotalCost": 15200,
    "costVariance": 550,
    "resourceCount": 3,
    "resources": [ ... ]
  }
}
```

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

### API GET OKRs Endpoint Examples

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/tasks/TASK-1119-OKR-KPI-LINKING-STATUS.md

Examples of how to query OKRs using entity_id, entity_type, and level parameters via the GET /api/okrs endpoint.

```http
GET /api/okrs?level=program&entity_id={programId}&entity_type=program
```

```http
GET /api/okrs?level=project&entity_id={projectId}&entity_type=project
```

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

### Parallel Server Startup with Dependency Graph (After)

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/EXECUTIVE_SUMMARY.md

Demonstrates the improved parallel startup process using a dependency graph, showing reduced total startup time and a summary table.

```text
🚀 Starting server initialization with dependency graph...
✅ Database initialized successfully (2.5s)
✅ Redis initialized successfully (1.2s)
✅ Neo4j initialized successfully (0.9s)
✅ AI Providers initialized successfully (2.3s)
✅ Workers initialized successfully (1.5s)

╔════════════════════════════════════════════════════════════════╗
║                 STARTUP DEPENDENCY SUMMARY                     ║
╠════════════════════════════════════════════════════════════════╣
║ ✅ Database                    [CRITICAL]  2500  ms ║
║ ✅ Redis                       [OPTIONAL]  1200  ms ║
║ ✅ Neo4j                       [OPTIONAL]  900   ms ║
║ ✅ AI Providers                [OPTIONAL]  2300  ms ║
║ ✅ Workers                     [OPTIONAL]  1500  ms ║
╠════════════════════════════════════════════════════════════════╣
║ Ready: 5/5 | Failed: 0 | Total: 2500ms                         ║
╚════════════════════════════════════════════════════════════════╝

✅ All dependencies initialized successfully
🌐 Starting server on port 5000...

Total startup: ~2.5 seconds (parallel) - ~70% faster!
```

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

### GET /api/search/suggestions

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/INTEGRATION_PLAN_GKG_RAG_AI_SEARCH.md

Gets search suggestions based on a starting entity and depth.

```APIDOC
## GET /api/search/suggestions

### Description
Provides search suggestions based on a starting entity and the depth of relationships to consider.

### Method
GET

### Endpoint
/api/search/suggestions

### Parameters
#### Query Parameters
- **startEntityId** (string) - Required - The ID of the entity to start suggestions from.
- **depth** (integer) - Optional - The depth of relationships to explore for suggestions. Defaults to 1.

### Response
#### Success Response (200)
- **suggestions** (array of strings) - A list of suggested search terms or entities.

#### Response Example
```json
{
  "suggestions": [
    "payment gateway integration",
    "fraud detection systems",
    "PCI compliance"
  ]
}
```
```

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

### Example: Clone Preview Channel to Live

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/skills/firebase-hosting-basics/references/deploying.md

An example demonstrating how to clone the 'feature-beta' channel from a default site to the live channel.

```bash
npx -y firebase-tools@latest hosting:clone my-project:feature-beta my-project:live
```

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

### Prepare Environment Files

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/03-development/AGENT_HANDOVER_GETTING_STARTED.md

Copy example environment files to create your local configuration.

```bash
cp .env.local.example .env.local
cp server/.env.example server/.env
```

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

### Run Example Script for Task Cost

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/features/legacy-06-features/task-costing/TASK_COST_IMPLEMENTATION.md

Execute the example script to display calculation examples or test API endpoints. Ensure you have Node.js and npm installed.

```bash
# Display calculation examples
npx tsx server/scripts/examples-task-cost.ts
```

```bash
# Also test API endpoints
npx tsx server/scripts/examples-task-cost.ts --test-api
```

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

### Get Follow-up Suggestions API Request (GET)

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/PHASE2_COMPLETION_REPORT.md

Example of how to make a GET request to retrieve follow-up suggestions for an entity. Specify entity ID and type.

```bash
curl http://localhost:5000/api/search/suggestions/ENTITY_ID \
  -H "Authorization: Bearer <token>" \
  -G --data-urlencode "entityType=project"
```

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

### API Testing Examples

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/tasks/TASK-1282-OKR-API-COMPLETION.md

Examples for testing the OKR API using curl. Includes GET and POST requests.

```bash
# Test with curl or Postman
curl -X GET http://localhost:5000/api/okrs \
  -H "Authorization: Bearer <token>"
```

```bash
curl -X POST http://localhost:5000/api/okrs \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"objective_title": "Test OKR", "level": "organization"}'
```

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

### Sequential Server Startup (Before)

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/EXECUTIVE_SUMMARY.md

Illustrates the traditional sequential startup process for a server, highlighting the time taken for each dependency.

```text
🚀 Starting server initialization...
📊 Connecting to database... (waits 2-3 seconds)
✅ Database connected
💾 Connecting to Redis... (waits 1-2 seconds)
✅ Redis connected
🕸️ Connecting to Neo4j... (waits 1 second)
✅ Neo4j connected
🤖 Initializing AI providers... (waits 2-3 seconds)
✅ AI providers initialized
🔄 Initializing workers... (waits 1-2 seconds)
✅ Workers initialized

Total startup: ~7-11 seconds (sequential)
```

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

### Example `.env.test` Configuration

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/e2e/TEST_SETUP.md

An example of a fully configured `.env.test` file with sample credentials and project ID. Use this as a template for your own configuration.

```bash
# .env.test
TEST_USER_EMAIL=admin@adpa.com
TEST_USER_PASSWORD=admin123
TEST_PROJECT_ID=a1b2c3d4-e5f6-7890-abcd-ef1234567890
BASE_URL=http://localhost:3001
```

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

### Get Project Rankings (TypeScript)

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/tasks/TASK-328-COMPLETION-SUMMARY.md

Example of how to fetch project rankings for a specific program using the `GET /api/prioritization/rankings` endpoint.

```typescript
// Get rankings for a program
const response = await fetch('/api/prioritization/rankings?program_id=program-uuid', {
  headers: {
    'Authorization': `Bearer ${token}`
  }
})

const result = await response.json()
// result.data contains ranked projects with priority tiers
```

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

### Clean Install Commands with Nixpacks

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/04-deployment/RAILWAY_DEPLOYMENT_EXPLAINED.md

Demonstrates the commands executed during a clean install when using Nixpacks. This involves navigating to the server directory, performing a fresh npm install, and starting the application.

```bash
cd server
npm install          # Fresh install from package.json
npm start            # Run tsx src/server.ts
```

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

### Quick Start Command

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/scripts/migrate-to-supabase.md

This command sets up your Supabase project and starts the development server. Ensure your .env file is updated before running.

```powershell
# After creating Supabase project and updating .env
cd D:\source\repos\adpa\server
node scripts/apply-baseline-migration.js && node scripts/create-change-request-template.js && npm run dev
```

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

### Start Genkit Dev Mode with Next.js

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/skills/developing-genkit-js/references/docs-and-cli.md

Starts Genkit in development mode, enabling the Developer UI. This example is configured for a Next.js application.

```bash
genkit start -- npx next dev
```

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

### Initialize App Hosting

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/skills/firebase-app-hosting-basics/references/cli_commands.md

Use this interactive command to set up App Hosting in your local project. It detects your web framework, creates/updates `apphosting.yaml`, and can optionally create a backend.

```bash
npx -y firebase-tools@latest init apphosting
```

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

### Clone and Install ADPA Project

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/generated-documents/technical-design/deployment-architecture.md

Initial setup commands for the ADPA project, including cloning the repository, navigating into the directory, and installing npm dependencies.

```bash
git clone https://github.com/mdresch/adpa.git
cd adpa
npm install
```

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

### Railway Backend Build and Start Commands

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/04-deployment/railway/RAILWAY_CONFIGURATION.md

Commands to configure the build and start process for the backend service on Railway. Ensure the build command installs dependencies and builds the project, and the start command runs the application.

```bash
# Build Command: cd server && npm install && npm run build
# Start Command: cd server && npm start
```

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

### Startup Dependency Summary Output

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/adpa-server-bootstrap/SKILL.md

An example of the console output generated by the StartupManager, providing a summary of each dependency's initialization status, criticality, and duration.

```text
╔════════════════════════════════════════════════════════════════╗
║                 STARTUP DEPENDENCY SUMMARY                     ║
╠════════════════════════════════════════════════════════════════╣
║ ✅ Database                    [CRITICAL]  245   ms ║
║ ✅ Redis                       [OPTIONAL]  125   ms ║
║ ✅ Neo4j                       [OPTIONAL]  87    ms ║
║ ⏳ RabbitMQ                    [OPTIONAL]  0     ms ║
║ ✅ AI Providers                [OPTIONAL]  1250  ms ║
║ ✅ Workers                     [OPTIONAL]  340   ms ║
╠════════════════════════════════════════════════════════════════╣
║ Ready: 5/6 | Failed: 1 | Total: 2047ms                         ║
╚════════════════════════════════════════════════════════════════╝
```

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

### Next Steps - Verify Environment and Start Server

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/NPM-MIGRATION-SCRIPT-GUIDE.md

After a successful migration, ensure the VOYAGE_API_KEY is set and start the development server.

```bash
1. **Verify environment** - VOYAGE_API_KEY is set
2. **Start server** - `npm run dev`
```

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

### Setup Environment Variables

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/projects/ai-risk-management/22-implementation-plan.md

Copy example environment files to create local configuration files for the application and its server component. Ensure sensitive information is not committed to version control.

```bash
# Setup environment variables
cp .env.local.example .env.local
cp server/.env.example server/.env
```

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

### Start Development Environment and Validate

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/03-development/DOCKER_README.md

A sequence of commands to initiate the development environment, including starting services and validating the configuration. This is part of the initial development setup.

```bash
# 1. Ensure Docker is running
docker --version

# 2. Start services
docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d

# 3. Validate configuration
validate-docker.bat

# 4. Check logs if needed
docker-compose logs -f adpa-backend
```

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

### Start Services with Docker Compose

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/PIPELINE.md

Use this command to start all necessary services for local development using Docker Compose. Ensure Docker and Docker Compose are installed.

```bash
docker-compose up -d
```

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

### Expected Server Startup Output

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/OPTIMIZED_INTEGRATION_GUIDE.md

This is the expected output when the server starts successfully after integrating the serverBootstrap helper, showing dependency initialization and summary.

```text
🚀 Starting server initialization with dependency graph...
✅ Database initialized successfully (245ms)
✅ Redis initialized successfully (125ms)
✅ Neo4j initialized successfully (87ms)
✅ AI Providers initialized successfully (1250ms)
✅ Workers initialized successfully (340ms)

╔════════════════════════════════════════════════════════════════╗
║                 STARTUP DEPENDENCY SUMMARY                     ║
╠════════════════════════════════════════════════════════════════╣
║ ✅ Database                    [CRITICAL]  245   ms ║
║ ✅ Redis                       [OPTIONAL]  125   ms ║
║ ✅ Neo4j                       [OPTIONAL]  87    ms ║
║ ✅ AI Providers                [OPTIONAL]  1250  ms ║
║ ✅ Workers                     [OPTIONAL]  340   ms ║
╠════════════════════════════════════════════════════════════════╣
║ Ready: 5/5 | Failed: 0 | Total: 2047ms                         ║
╚════════════════════════════════════════════════════════════════╝

✅ All dependencies initialized successfully
🌐 Starting server on port 5000 at 0.0.0.0...
✅ Server running on port 5000
```

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

### Start Genkit Dev Mode with Node.js

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/skills/developing-genkit-js/references/docs-and-cli.md

Starts Genkit in development mode, enabling the Developer UI. This example uses Node.js with TypeScript and watches for file changes.

```bash
genkit start -- npx tsx --watch src/index.ts
```

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

### Core Implementation Files

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/server/docs/reports/YOU_DID_IT.md

Lists the core implementation files for the server startup module. Includes the main engine, manager, bootstrap, and dependency configurations.

```tree
server/src/startup/
├── dependencyGraph.ts           ✅ Core engine
├── startupManager.ts            ✅ Manager
├── serverBootstrap.ts           ✅ Bootstrap
├── README.md                    ✅ Docs
└── dependencies/
    ├── database.ts              ✅
    ├── redis.ts                 ✅
    ├── neo4j.ts                 ✅
    ├── rabbitmq.ts              ✅
    ├── aiProviders.ts           ✅
    ├── workers.ts               ✅
    └── index.ts                 ✅
```

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

### Find Related Entities API Request (GET)

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/PHASE2_COMPLETION_REPORT.md

Example of how to make a GET request to find related entities. Specify entity ID, type, relationship types, and depth.

```bash
curl http://localhost:5000/api/search/related/ENTITY_ID \
  -H "Authorization: Bearer <token>" \
  -G --data-urlencode "entityType=document" \
  --data-urlencode "relationshipTypes=impacts,depends_on" \
  --data-urlencode "depth=2"
```

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

### Start Development Server

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/tasks/TASK-1283-OKR-DASHBOARD-UI-COMPLETION.md

Use this command to start the development server for the project. Navigate to http://localhost:3000/portfolio/okrs to view the application.

```bash
# Start development server
npm run dev

# Navigate to:
http://localhost:3000/portfolio/okrs
```

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

### Git and Service Setup for Week 1

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/roadmap/MASTER_STRATEGIC_PLAN_2026.md

Provides commands for setting up a feature branch, creating database migrations, and initializing backend and frontend service files for the financial management week.

```powershell
# Create feature branch
git checkout -b feature/financial-management-week1

# Create database migrations
# Migration 203: program_budgets
# Migration 204: program_cost_performance  
# Migration 205: program_financial_analysis

# Begin backend service development
cd server/src/services
# Create: programFinancialService.ts
# Create: evmCalculator.ts

# Begin frontend components
cd ../../../components/program
# Create: FinancialDashboard.tsx
# Create: EVMDashboard.tsx

# Run tests, deploy to staging
```

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

### GET /api/search/suggestions/:entityId API Request

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/PHASE2_IMPLEMENTATION_SUMMARY.md

Example of a cURL request to get suggested follow-up searches based on entity relationships within the GKG. Requires specifying the entity type.

```bash
curl http://localhost:5000/api/search/suggestions/proj-uuid \
  -H "Authorization: Bearer <token>" \
  -G --data-urlencode "entityType=project"
```

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

### Full Deployment Sequence - Verification and Start

Source: https://github.com/mdresch/adpa/blob/adpa-project-charter/docs/reports/NPM-MIGRATION-SCRIPT-GUIDE.md

Verifies the migration by checking the count of entries in the knowledge_base_entries table and then starts the development server. Expected entry count is 10.

```bash
# 4. Verify migration
psql -h $DB_HOST -U $DB_USER -d $DB_NAME \
  -c "SELECT COUNT(*) FROM knowledge_base_entries;"
```

```bash
# 5. Start server
npm run dev
```