fix: share-ready polish + model-agnostic LLM selection - #9
Merged
Conversation
Unblock pnpm 11 CI (xlsx integrity + core-js allowBuilds), strip vapourware OAuth/MCP claims from agent discovery, add /api/health, and point public docs at datasink.dev / chrisschouk/sink-cli. Co-authored-by: Chris Schofield <info@totalaudiopromo.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Git deploys were building the monorepo root and looking for public/, so preview/production stayed broken. Add root vercel.json → web/dist, promote api/ + middleware to root, and align README provider docs with the CLI. Co-authored-by: Chris Schofield <info@totalaudiopromo.com>
Add --model for any vendor model ID, apply the same LLM choice to soak and steep, share alias resolution, and open the web BYOK panel to either vendor with a free-form model field. Co-authored-by: Chris Schofield <info@totalaudiopromo.com>
cursor
Bot
changed the title
chrisschouk
marked this pull request as ready for review
September 4, 2026 10:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Before sharing sink / datasink as a LinkedIn + chrisscho.uk case study, the public surface needed to be airtight. Audit found a red CI badge, vapourware agent-discovery claims, a broken Vercel git deploy, README drift, and LLM selection locked to a handful of shortcut models.
What changed
xlsxintegrity +core-jsallowBuilds: falseGET /api/healthvercel.jsonbuilds datasink + web →web/dist, serves edge functions from rootapi/sink demo, four-phase tagline--model <id>accepts any Anthropic/OpenAI model string--provider anthropic|openai(or shortcuts) — same choice applied to soak and steepVerified locally
After merge
main/llms.txt,/api/health, drop a CSV on datasink.devhttps://datasink.devrepository/homepagefields matchSafe share claims
Works without keys: scrub, rinse, spot, inspect, demo, browser scrub/rinse.
Needs BYOK: soak, steep (any Anthropic or OpenAI model).
Do not claim hosted OAuth, remote MCP, or a public contact API beyond health + Firecrawl proxy.