docs: add product roadmap

[folathecoder]

Public, directional roadmap: Reliability, then Observability, then more models.

[qodo-code-review]

PR Summary by Qodo

docs: add public product roadmap

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Add a public, directional roadmap for agentling’s near- and mid-term priorities.
• Clarify alpha (0.x) stability expectations and that milestones are not schedules.
• Outline planned focus areas: reliability, observability/evals, then more model adapters.

High-Level Assessment

Adding a dedicated ROADMAP.md is the most discoverable, low-maintenance way to publish a directional roadmap. Alternatives (wiki/website-only) reduce visibility for GitHub users and complicate versioning alongside the code.

Files changed (1) +88 / -0

Documentation (1) +88 / -0

ROADMAP.mdAdd directional product roadmap (v0.1 shipped through 1.0 goals) +88/-0

Add directional product roadmap (v0.1 shipped through 1.0 goals)

• Introduces a public roadmap describing shipped v0.1.0 scope and upcoming priorities across v0.2 (reliability), v0.3 (observability/evaluation), and v0.4 (more model adapters). Includes non-schedule disclaimers, exploratory ideas, and guidance for community input.

ROADMAP.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Roadmap not linked 🐞 Bug ⚙ Maintainability

Description

ROADMAP.md is added but the project’s README (the primary landing page) doesn’t link to it, so most
users won’t discover the roadmap unless they browse the repo file list directly. This is a
low-severity documentation/navigation gap.

Code

ROADMAP.md[R1-3]

+# agentling roadmap
+
+agentling is a tiny async framework for reliable, observable, tool-using agents:

Evidence

The roadmap file is present, but the repository README has a curated Contents list and does not
mention/link the roadmap anywhere, and no other files reference it, so it won’t be discoverable from
the README flow.

ROADMAP.md[1-3]
README.md[44-62]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A new `ROADMAP.md` is introduced, but `README.md` doesn’t reference it. This makes the roadmap hard to discover for users who primarily read the README.

## Issue Context
`README.md` contains a "Contents" section but no "Roadmap" entry/link.

## Fix Focus Areas
- README.md[44-62]
- ROADMAP.md[1-3]

## Suggested fix
- Add a "Roadmap" bullet/link in `README.md` (either near the top description or in the Contents list), pointing to `ROADMAP.md`.
- (Optional) Add a `Roadmap = ".../ROADMAP.md"` entry under `[project.urls]` in `pyproject.toml` if you want it visible on package indexes.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Roadmap not linked 🐞 Bug ⚙ Maintainability

ROADMAP.md is added but the project’s README (the primary landing page) doesn’t link to it, so most
users won’t discover the roadmap unless they browse the repo file list directly. This is a
low-severity documentation/navigation gap.

Agent Prompt

## Issue description
A new `ROADMAP.md` is introduced, but `README.md` doesn’t reference it. This makes the roadmap hard to discover for users who primarily read the README.

## Issue Context
`README.md` contains a "Contents" section but no "Roadmap" entry/link.

## Fix Focus Areas
- README.md[44-62]
- ROADMAP.md[1-3]

## Suggested fix
- Add a "Roadmap" bullet/link in `README.md` (either near the top description or in the Contents list), pointing to `ROADMAP.md`.
- (Optional) Add a `Roadmap = ".../ROADMAP.md"` entry under `[project.urls]` in `pyproject.toml` if you want it visible on package indexes.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools