Broken Message refactor

`transcribe.js` has at least one place where the `try... catch` is repeated over and over instead of just going up a level.

Here's an example of this pattern:

```js
if (data.KEY) {
try {
tpen.project.KEY= JSON.parse(data.KEY);
} catch (e) {
clearTimeout(longLoadingProject);
$(".turnMsg").html("Sorry! We had trouble fetching this project. Refresh the page to try again.");
$(".transLoader").find("img").attr("src", "../TPEN/images/BrokenBook01.jpg");
return false;
}
}
```

The `try` can definitely be pushed out one level or this can be a map on the keys, unless I am missing a bit.

Start in transcribe.js by locating the repeated try...catch blocks around project data parsing, using the KEY example in the issue as an entry point. Compare the existing error handling across keys and verify that the refactor preserves the loading timeout, error message, image change, and return behavior.

Written by the indexing model from the issue text.