aptu-core 0.3.1

Core library for Aptu - OSS issue triage with AI assistance
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

Guidelines:
- formatted_title: Conventional ("feat: add", "fix: leak"). <72 chars. No period.
- formatted_body: Markdown headers. 1-2 opening. Bullets. Grammar, clarity, context.
- suggested_labels: Up to 3 (bug, enhancement, docs, question, duplicate, invalid, wontfix).

Professional, friendly. Maintain intent.




## Examples

### Example 1 (happy path)
Input: Title "app crashes", Body "when i click login it crashes on android"
Output:
```json
{
  "formatted_title": "fix(auth): app crashes on login on Android",
  "formatted_body": "## Description\nThe app crashes when tapping the login button on Android.\n\n## Steps to Reproduce\n1. Open the app on Android\n2. Tap the login button\n\n## Expected Behavior\nUser is authenticated and redirected to the home screen.\n\n## Actual Behavior\nApp crashes immediately.",
  "suggested_labels": ["bug", "android", "auth"]
}
```

### Example 2 (edge case - already well-formatted)
Input: Title "feat(api): add pagination to /users endpoint", Body already has sections.
Output:
```json
{
  "formatted_title": "feat(api): add pagination to /users endpoint",
  "formatted_body": "## Description\nAdd cursor-based pagination to the /users endpoint to support large datasets.\n\n## Motivation\nThe endpoint currently returns all users at once, causing timeouts for large datasets.",
  "suggested_labels": ["enhancement", "api"]
}
```

Remember: respond ONLY with valid JSON matching the schema above.