feat(share): add human-readable bundle page with JSON fallback

[benjaminshafii]

Summary

• add content negotiation to GET /b/:id: browser-style requests now get a human-readable OpenWork Share page, while machine clients keep receiving JSON
• preserve parseability for OpenWork imports with explicit ?format=json, Accept: application/json, and embedded machine-readable metadata (meta tags + application/json script payload)
• add ?format=json&download=1 support, document the behavior in the share-service README, and add unit tests for format detection/rendering helpers

Testing

• node --test services/openwork-share/api/b/render-bundle-page.test.js
• packaging/docker/dev-up.sh (stack booted successfully)
• docker compose -p openwork-dev-b0c92812 -f packaging/docker/docker-compose.dev.yml down

Notes

• full end-to-end publish/fetch against Vercel Blob was not run locally because BLOB_READ_WRITE_TOKEN is not available in this environment.
• no feature screenshots are attached for the same reason: there is no live local bundle ID without Blob-backed publish.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-software	Ready	Preview, Comment	Feb 20, 2026 5:50am

[github-actions]

The following comment was made by an LLM, it may be inaccurate: