\r \r

BugPack - Fix Bug\r

\r Read bug context from BugPack, locate the relevant code, apply a fix, and mark the bug as fixed.\r \r

Instructions\r

\r

1. Get bug context: Call GET http://localhost:3456/api/bugs/:id to fetch full bug details including description, screenshots, environment, and related files.\r \r
2. Analyze the bug: Read the description and examine the screenshots to understand what is broken and what the expected behavior should be.\r \r
3. Locate code: Use the relatedFiles array from the bug context to find the relevant source files. If relatedFiles is empty, use the pagePath and description to search the codebase.\r \r
4. Apply fix: Edit the source code to fix the described issue. Follow the project's existing code style and conventions.\r \r
5. Mark as fixed: After applying the fix, call PATCH http://localhost:3456/api/bugs/:id with:\r

   { "status": "fixed" }\r
   ```\r
   

\r 6. Add fix note (optional): Call PATCH http://localhost:3456/api/bugs/:id with a description update to document what was changed.\r \r

Example\r

\r

# Step 1: Get bug context\r
GET http://localhost:3456/api/bugs/abc-123\r
\r
# Step 5: Mark as fixed\r
PATCH http://localhost:3456/api/bugs/abc-123\r
Content-Type: application/json\r
\r
{ "status": "fixed" }\r
```\r
\r
Response:\r
\r
```json\r
{\r
  "ok": true,\r
  "data": {\r
    "id": "abc-123",\r
    "status": "fixed"\r
  }\r
}\r
```\r