Not sure why people are arguing with Froggie, given he's looking at the actual SCDOT data? I'd lean towards changing the endpoint to how he described it and, amazingly, how Google Maps may have actually got it right.
I'm not arguing with Froggie...I'm arguing with SCDOT - either their data is wrong or their field signage is.
Looking at more stuff, Official Maps up through 2013 do not show it extended around to Coming St (instead shows the connections around to/from Coming St as ramps). 2015 and 2016 Official maps do show it. The latest Charleston Metro SCDOT map implies it is extended and the latest Charleston County map is inconclusive. Just now I found the 2002 FHWA interstate table and it shows the same length (220.95) as the current table. Coupled with no AASHTO action on I-26 this means the endpoint has never moved. 0.95 miles past the posted MM 220 does put you around the curve to Coming St. So SCDOT in my opinion is correct on paper but is incorrect in the field.
It also means that technically if you drove I-26 east prior to the new US 17 bridge over the Cooper River and used the ramp to then-US 17 north, you did not finish the east end of I-26 and if you use the Meeting St ramp today this would also be true. Exit signage is contrary to this and the King St ramp should be Exit 221B instead of US 17 south.
Prior to the new bridge this means there should have also been an Exit 221 on I-26 WB at the point where I-26 bent away from US 17 (where the stub ramp is still present from 17's old bridge).
This could mean the current endpoint should stay (named 221A +221) plus a new endpoint further around should be added as the endpoint and called 221B.
[modified to add the last sentence]