coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: refresh SCOPE.md for post-ISSUE-WP-0005 shipped mapping
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
Correct stale "mapping when implemented" / "design only" wording: store,
CLI project/map, TaskSpec work_record_uuid, and boundary-sync policy are
shipped; note remaining gaps (REST /mappings/, inward sync).
This commit is contained in:
tegwick 2026-07-22 01:08:20 +02:00
parent 4ce3e263ed
commit 26064f0c25
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
SCOPE.md
View file

@ -1,12 +1,14 @@
# SCOPE — issue-core
Concrete **what this repo provides**, **what it owns**, and **what it does not**.
Paired with `INTENT.md` (*why*) and `docs/uuid-external-id-mapping.md` (*mapping design*).
Paired with `INTENT.md` (*why*), `docs/uuid-external-id-mapping.md` (design),
and `docs/boundary-sync-and-status-mapping.md` (status policy).
**Fleet role (2026-07-20):** issue-core is a **connector** to external issue
trackers — not the origin of fleet work records (ADR-001 / work-record canon).
Work records live in repo files and state-hub; this package projects to and
operates on tracker backends when that is intentional.
operates on tracker backends when that is intentional. Mapping store + CLI
shipped under ISSUE-WP-0005 (2026-07-22).
**Package:** `issue-core` **v0.2.1** · Python ≥ 3.8 · entry points `issue`,
`issue-core` (alias), `issue-tracker` (legacy deprecation hint).