# KORA v0.2.1-alpha Good First Issue Seeding

Date: 2026-05-07

## Candidate Sources

Initial issue candidates were selected from:

- `docs/good_first_issues.md`
- `.github/ISSUE_TEMPLATE/good_first_issue.md`
- `.github/ISSUE_TEMPLATE/community-task.md`
- `.github/ISSUE_TEMPLATE/docs_improvement.md`
- `docs/reports/v0.2.1-alpha-contributor-path-audit.md`
- `CONTRIBUTING.md`
- `README.md`
- `docs/README.md`
- `experiments/README.md`

Selection favored small, documentation-oriented tasks that do not require release, tag, package-version, raw artifact, private-context, or architecture changes.

## GitHub CLI Result

GitHub CLI was available and authenticated. Issues were created in `Krako-Labs/KORA`.

Available labels used:

- `good first issue`
- `documentation`

`developer-experience` was not present in the repository label list, so it was skipped.

## Created Issues

| Issue | Title | Labels |
|---|---|---|
| https://github.com/Krako-Labs/KORA/issues/33 | Docs: explain the hello_kora example | `good first issue`, `documentation` |
| https://github.com/Krako-Labs/KORA/issues/34 | Docs: explain the retry_demo example | `good first issue`, `documentation` |
| https://github.com/Krako-Labs/KORA/issues/35 | Docs: clarify direct_vs_kora offline mode | `good first issue`, `documentation` |
| https://github.com/Krako-Labs/KORA/issues/36 | Docs: define core telemetry counters | `good first issue`, `documentation` |

No issue creation failures occurred.

## Issue Body Pattern

Each issue includes:

- task summary
- contribution type
- likely files or area
- expected outcome
- out-of-scope items
- validation checklist
- claim hygiene note

Issue bodies avoid production cost, real API-cost, production benchmark, full runtime-integrated benchmark, broad workload superiority, and energy reduction claims.

## Next Recommended Batch

Next issue-seeding batch should stay small and can draw from these backlog items:

1. `Docs: add expected output snippets for first-run examples`
2. `Docs: describe sample telemetry input`
3. `Docs: clarify benchmark docs are exploratory`
4. `CLI: review help wording for first-run commands`
5. `Test: cover unknown example error path`

Before creating the next batch, check whether any of issues 33-36 have already been claimed or completed.

## Do-Not-Touch Notes

- Do not create release tags or GitHub Releases.
- Do not update package versions.
- Do not upload release assets.
- Do not commit raw benchmark JSON artifacts.
- Do not require private context for good-first-issue work.
- Do not add unsupported production, API-cost, benchmark, broad workload, or energy claims.
