feat: implement ISSUE-WP-0005 connector mapping and scope alignment

Add MappingService (work_record_uuid ↔ external id), project/map CLI with
outward push-status, optional TaskSpec work_record fields, boundary-sync
policy, and packaging/capability framing cleanup. Mark WP-0005 finished.

CAPABILITY-issue-tracking.yaml

@@ -3,21 +3,20 @@
 
 metadata:
   name: issue-core
-  version: 1.0.0
-  type: coordination-tool
+  version: 0.2.1
+  type: connector
   description: >
-    Universal interface for issue tracking coordination across Gitea, GitHub, GitLab.
-    Provides unified API to prevent direct platform API usage and credential sprawl.
+    Backend-agnostic connector to external issue trackers (Gitea/Forgejo, SQLite).
+    Maps work-record UUIDs to external issue ids. Not the origin of fleet work records.
 
 # What problems this capability solves
 purpose:
-  primary: Agent coordination via issue tracking
+  primary: External tracker projection and ops (work-record-aware connector)
   problems_solved:
-    - Direct API calls to GitHub/GitLab/Gitea (avoid credential sprawl)
-    - Inconsistent issue tracking access patterns
-    - Token waste from redundant API calls
-    - Platform-specific code in agents
-    - Offline/online sync complexity
+    - Direct API calls to Gitea/GitHub/GitLab (credential sprawl)
+    - No durable link from work-record UUID to tracker issue
+    - Platform-specific agent code for tracker CRUD
+    - Offline SQLite cache / backend sync for tracker data
 
 # When agents should use this capability
 usage_rules:
@@ -25,19 +24,21 @@ usage_rules:
     - "Direct Gitea API calls (requests.post to /api/v1/repos/...)"
     - "GitHub CLI (gh issue create/list/...)"
     - "GitLab CLI (glab issue create/list/...)"
-    - "Python libraries (PyGithub, python-gitlab)"
-    - "Direct SQL queries to issue databases"
+    - "Python libraries (PyGithub, python-gitlab) for routine tracker ops"
 
   PREFER_OVER:
-    - "Web scraping of issue tracker UIs"
-    - "Manual issue management"
-    - "Custom issue tracking scripts"
+    - "Ad hoc curl scripts against tracker APIs"
+    - "Fire-and-forget Forgejo issues with no work-record mapping"
 
   USE_WHEN:
-    - "Creating, updating, or querying issues"
-    - "Multi-agent coordination needed"
-    - "Offline work with sync required"
-    - "Cross-platform issue management"
+    - "Projecting or linking a work record to an external issue"
+    - "Creating, updating, or querying issues on a tracker backend"
+    - "Offline tracker work with backend sync"
+    - "Intentional external issues (not fleet intake origin)"
+
+  DO_NOT_USE_WHEN:
+    - "Spawning fleet tasks/intake (use work records + promotion)"
+    - "Default sink for internal automation findings (see ACTIVITY-WP-0022)"
 
 # How to integrate this capability
 integration: