Move bone data to server

[leandrumartin]

Pull Request Summary

Closes #352

A brief description/summary of your PR here. What does it add? Why is it necessary? How was the change made, and how was it tested?

Bone data is now stored directly on the server, copied over from the data branch. The server code has been rewritten to fetch the data from these files instead of from GitHub.

Screenshots

If applicable, add screenshots showing the before and after of any UI changes made.

PR Checklist

• Project builds and runs
• Tests and linters pass
• Any related documentation has been updated, including JSDoc comments or docstrings

Detailed Description

A more detailed description and any additional information.

An Express endpoint is created for images with

app.use("/api/images", express.static(IMAGES_DIR));

to replace the previous functionality whereby the server would send the frontend the URL of each image. Now, the URL provided is this endpoint so that the images can be pulled from the Express server rather than GitHub.

[leandrumartin]

??? This code was your suggestion. But fine

[leandrumartin]

@copilot Review ONLY the changes to the file boneset-api/server.js. Make NO CHANGES to the file; instead, ONLY add comments to this thread, acting as a code reviewer.

[Copilot]

@copilot Review ONLY the changes to the file boneset-api/server.js. Make NO CHANGES to the file; instead, ONLY add comments to this thread, acting as a code reviewer.

One blocking issue in boneset-api/server.js: API_BASE_URL is hardcoded to http://127.0.0.1:${PORT}, so /api/bone-data/ returns image URLs that won’t work for non-local clients/deployments. Please return relative URLs (e.g. /api/images/${encodeURIComponent(filename)}) or derive the host from the incoming request.