Rewrite SCOPE to separate what issue-core provides today (models, backends, CLI, REST, sync, deploy) from in-scope growth and out-of-scope fleet work. Align package __init__ description with the connector role.
16 lines
592 B
Python
16 lines
592 B
Python
"""
|
|
issue-core — external issue-tracker connector
|
|
|
|
Backend-agnostic CLI, library, and optional REST surface for operating on
|
|
third-party issue trackers (Gitea/Forgejo, local SQLite). Not the origin of
|
|
fleet work records (see INTENT.md / SCOPE.md).
|
|
|
|
Shipped:
|
|
- Unified issue model and IssueBackend plugin architecture
|
|
- Local SQLite + Gitea backends; bidirectional sync CLI
|
|
- CLI (`issue` / `issue-core`) and optional FastAPI REST (`issue serve`)
|
|
"""
|
|
|
|
__version__ = "0.2.1"
|
|
__author__ = "Coulomb / MarkiTect Project"
|
|
__description__ = "External issue-tracker connector with plugin backends"
|