feat: add Aetheris - AI Agent execution runtime

[Colin4k1024]

Aetheris

A library for developing AI agents based on the CoRAG(Chunk-Omni Retrieval-Augmented Generation) pattern. It supports multiple LLM providers, vector databases, and web search engines.

Added to list: 2026-04-14

Forge link: https://github.com/Colin4k1024/Aetheris
pkg.go.dev: https://pkg.go.dev/github.com/Colin4k1024/Aetheris@v2.5.1
goreportcard.com: https://goreportcard.com/report/github.com/Colin4k1024/Aetheris
Coverage: https://app.codecov.io/gh/Colin4k1024/Aetheris

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
❌ pkg.go.dev: unreachable

How to fix: The pkg.go.dev page could not be reached.
Ensure your module path in go.mod matches the URL. After pushing a tagged release, pkg.go.dev indexes the module automatically — this can take a few minutes. You can trigger it manually by visiting https://pkg.go.dev/your-module-path.
✅ Go Report Card: OK (grade unknown)

Additional checks

✅ License: Apache-2.0
⚠️ Maturity: repo appears to have less than 5 months of history

How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
✅ CI/CD: GitHub Actions workflows detected
✅ README: present
✅ Coverage: link accessible

---

Action needed: one or more required checks failed. Please update your PR body with the missing links and ensure the repository meets the quality standards.

These checks are automated and do not replace maintainer review. See CONTRIBUTING.md for full guidelines.

---

PR Diff Validation

Content checks

✅ Files changed: only README.md
❌ Single item: 1 added, 2 removed (expected exactly 1 change per PR)

How to fix: Each PR should add, remove, or change only one package.
Please split this into separate PRs — one package per PR.
✅ Link consistency: README link matches forge link in PR body
✅ Link text: matches repository name
✅ Description: ends with punctuation
✅ Description tone: no promotional language detected
✅ Category size: Artificial Intelligence has 13 items

---

Action needed: one or more content checks failed. Please review the contribution guidelines.

Automated diff validation — does not replace maintainer review.

[sentry]

Bug: The new entry Aetheris in the README.md is not in correct alphabetical order within its section.
_{Severity: LOW}

Suggested Fix

Move the line for Aetheris to the correct alphabetical position within the "Artificial Intelligence" section, which should be before the chromem-go entry.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: README.md#L225

Potential issue: The pull request adds the entry `Aetheris` to the "Artificial
Intelligence" section of the `README.md` file. The new entry is placed after `fun` and
before `langchaingo`. However, this violates the alphabetical ordering of the list, as
`Aetheris` should appear before entries starting with 'c' and 'f', such as `chromem-go`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The new entry "Aetheris" in README.md is not in the correct alphabetical order. It should be placed before "chromem-go" to satisfy the TestAlpha CI check.
_{Severity: LOW}

Suggested Fix

Move the line containing the "Aetheris" entry in README.md to its correct alphabetical position. It should be placed before the "chromem-go" entry to maintain the case-insensitive alphabetical order enforced by the TestAlpha CI test.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: README.md#L225

Potential issue: The new entry "Aetheris" in `README.md` is not in the correct
case-insensitive alphabetical order. The repository contains an automated test,
`TestAlpha`, which verifies the alphabetical ordering of items in this list. The current
placement of "Aetheris" after "fun" will cause this test to fail during CI checks, as
'a' comes before 'f'. The test failure will report an expectation mismatch, such as
`expected 'aetheris' but actual is 'fun'`, blocking the pull request from being merged.

[sentry]

Bug: The new entry "Aetheris" in README.md is not in the correct alphabetical position, which will cause the TestAlpha CI check to fail.
_{Severity: MEDIUM}

Suggested Fix

In README.md, move the [Aetheris] entry to the beginning of its list section, before [chromem-go], to ensure the list remains in alphabetical order and passes the CI checks.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: README.md#L225

Potential issue: The addition of the "Aetheris" entry to the list in `README.md`
violates the alphabetical ordering requirement for that section. A test function,
`TestAlpha` in `main_test.go`, validates this ordering by fetching all list items,
converting them to lowercase, and comparing the result to a sorted version of the list.
Because "aetheris" is placed after "fun" instead of at the beginning of the list, the
check `item != sorted[k]` will evaluate to true, causing the test to fail and block the
continuous integration pipeline.