From 26064f0c2513b810aa2ef9cd3c97f8c7fe527397 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 22 Jul 2026 01:08:20 +0200 Subject: [PATCH] docs: refresh SCOPE.md for post-ISSUE-WP-0005 shipped mapping 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). --- SCOPE.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/SCOPE.md b/SCOPE.md index 1cd71ee..d6a96ca 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -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).