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.

issue_core/api/schemas.py

@@ -34,10 +34,25 @@ class TaskIngestionRequest(BaseModel):
         min_length=1,
         description=(
             "Activity event UUID, or a stable scheduler/source key when no "
-            "event row exists."
+            "event row exists. Not a work-record UUID."
         ),
     )
     activity_definition_id: str = Field(..., min_length=1)
+    work_record_uuid: Optional[str] = Field(
+        default=None,
+        description=(
+            "Optional work-record UUIDv7. When set, ingestion upserts a "
+            "mapping row (work_record_uuid ↔ backend issue id)."
+        ),
+    )
+    work_record_id: Optional[str] = Field(
+        default=None,
+        description="Optional canonical work-record id (human-facing).",
+    )
+    work_record_kind: Optional[str] = Field(
+        default=None,
+        description="Optional work-record kind (task, intake, …).",
+    )
 
 
 class TaskIngestionResponse(BaseModel):