feat: update HRevolution hackathon demo

[Nchpg]

Team Submission

App name: HRevolution
Team name: HepiR
Folder: HEpiR-HREvolution

Checklist

• My app folder is at the repository root
• app.json is present and valid
• app.json slug matches the folder name
• .env.example lists all required environment variables
• README.md explains what the app does and how to run it
• At least one preview image exists in assets/
• No real secrets or API keys are committed
• I have not modified files outside my team's folder
• I have not modified any root-level or platform files

What does this app do?

HEpiR is an AI-powered recruitment dashboard that helps HR teams manage, analyse, and rank candidates efficiently.

The app connects to HrFlow.ai to centralize job openings and applications. When a candidate uploads a resume, HEpiR automatically parses it, evaluates the candidate against the job requirements, and generates an AI-powered synthesis including strengths, weaknesses, recommendations, and a hiring verdict.

It also allows recruiters to enrich candidate profiles with additional documents (PDFs, notes, audio recordings), which are analysed and integrated into the scoring system. The platform further assists HR teams with interview question generation, email drafting, and pipeline tracking across recruitment stages.

How to run

1. Clone the repository:

git clone <repo-url>
cd HEpiR-HREvolution

2. Configure environment variables:

cp .env.example .env

3. Then edit the .env file and add your credentials:

• HrFlow.ai API key, source key, and board key
• OpenRouter (or compatible LLM) API key

4. Start the application with Docker:

docker compose up --build

Access the services: http://localhost:3000/

HrFlow.ai APIs used

The application uses the following HrFlow.ai endpoints:

POST /v1/profile/parsing/file
→ Parse a resume file and create a candidate profile
GET /v1/profile/indexing
→ Retrieve full candidate profile data (skills, experience, metadata)
PUT /v1/profile/indexing
→ Update candidate data (scores, synthesis, stage, documents)
POST /v1/tracking/indexing
→ Link a candidate to a job (create an application)
GET /v1/tracking/searching
→ List candidates for a specific job
GET /v1/job/indexing
→ Retrieve detailed job information
POST /v1/job/indexing
→ Create a new job
GET /v1/job/searching
→ List all jobs
POST /v1/score/searching
→ Compute matching scores between candidates and jobs