# Bilig Community Launch Pack

This is the working growth text for moving `proompteng/bilig` from a tiny
public footprint to `1,000` legitimate GitHub stars without fake accounts,
paid stars, spam, or inflated claims.

Baseline verified on May 8, 2026:

- GitHub repo: <https://github.com/proompteng/bilig>
- Baseline GitHub surface: public repo, `8` stars, `1` fork, `39` open issues
- npm package: <https://www.npmjs.com/package/@bilig/headless>
- Baseline npm surface: `@bilig/headless@0.10.62`, MIT, TypeScript types, npm
  API downloads: `2,399` last week and `16,491` last month
- Existing Hacker News launch:
  <https://news.ycombinator.com/item?id=48045427>, `2` points and `1`
  self-comment after roughly one day

Latest public snapshot on May 8, 2026:

- GitHub surface: public repo, `9` stars, `2` forks, `46` open issues
- npm surface: `@bilig/headless@0.11.2`, MIT, TypeScript types, npm API
  downloads: `7,182` last week and `21,748` last month
- Contributor funnel: `18` open `good first issue`, `18` open
  `first-timers-only`, and `18` open `help wanted` issues

Latest execution snapshot on May 18, 2026 at `02:02:33Z`:

- GitHub surface: public repo, `23` stars, `17` forks, `17` open issues
- npm surface: `@bilig/headless@0.21.1`, MIT, TypeScript types, npm API
  downloads: `17,235` last week and `32,535` last month
- Contributor funnel: `15` open `good first issue`, `15` open
  `first-timers-only`, and `15` open `help wanted` issues
- Starter funnel refresh: fourteen current first-timer example issues, `#207`
  through `#212` and `#217` through `#223`, cover inventory reorder points,
  accounts receivable aging, usage-based billing tiers, support SLA breach
  summaries, weighted sales pipeline forecasts, headcount capacity forecasts,
  loan amortization, cohort retention, commission payout, cash runway, currency
  sensitivity, payroll accrual, and deferred revenue workflows. Issues `#227`
  through `#233` and `#238` through `#240` add a small MCP starter track for
  contributors who prefer agent tool-server docs, client recipes, and tests to
  business examples.
- Discussion activity: `8` GitHub Discussions, including the MCP spreadsheet
  tool-server show-and-tell thread, the AI SDK/LangChain WorkPaper agent
  announcement, the five-example show-and-tell thread, and the workflow-feedback
  thread
- Discovery metadata: GitHub topics now include `agent-tools`, `ai-agents`,
  `excel`, `headless-spreadsheet`, `xlsx`, `mcp-server`, and
  `formula-recalculation` alongside the spreadsheet-engine and
  workbook-automation topics.
- npm discovery metadata now includes exact agent and formula search terms such
  as `ai-agents`, `spreadsheet-agent`, `workbook-agent`,
  `formula-recalculation`, `mcp`, and `model-context-protocol`.
- MCP discovery is live in the official registry as
  `io.github.proompteng/bilig-workpaper`, backed by `@bilig/headless` stdio
  package metadata and the packaged `bilig-workpaper-mcp` binary.
- MCP directory reviewer surfaces: the existing mcp.so and Cline MCP
  Marketplace submission issue bodies were refreshed on May 18, 2026 for
  `@bilig/headless@0.21.1`, the file-backed MCP command, the current seven-tool
  surface, and the static server card, without adding duplicate comments.
- External activity: `0` open external issues, `0` open external pull requests,
  `6` external issues opened in the last seven days, and `43` external pull
  requests opened in the last seven days
- Token-backed traffic: `602` views from `189` unique visitors and `28,427`
  clones from `3,596` unique cloners; top referrers include GitHub, Hacker
  News, X, the project site, and Google

Latest public execution snapshot on May 13, 2026 after the landing-page pass:

- GitHub surface: public repo, `24` stars, `10` forks, Forgejo and GitHub
  mirrors synced on `main`
- Contributor funnel: `45` open `first-timers-only` issues
- Site conversion surface: homepage now leads with a live WorkPaper demo,
  bundled webfonts, split product-demo CSS, and an npm-only smoke-test path at
  <https://proompteng.github.io/bilig/try-bilig-headless-in-node.html>
- Search-intent surface: a TypeScript-first "evaluate Excel formulas in
  Node.js" page now targets the exact formula-evaluation query with a runnable
  smoke test, readback, and persisted restore proof:
  <https://proompteng.github.io/bilig/evaluate-excel-formulas-in-node-typescript.html>
- Distribution surface: GitHub Discussion `#270` now points backend and agent
  developers at the npm-only TypeScript smoke test:
  <https://github.com/proompteng/bilig/discussions/270>

Latest growth snapshot on May 18, 2026 after the `0.21.1` release and MCP
registry refresh:

- GitHub surface: `23` stars, `17` forks, `17` open issues, and `0` open pull
  requests.
- npm surface checked again on May 18, 2026: `@bilig/headless@0.21.1`, with
  `17,235` downloads last week and `32,535` downloads in the last 30 days.
- Contributor funnel: `15` open `good first issue`, `15` open
  `first-timers-only`, and `15` open `help wanted` issues.
- New starter issues `#272` through `#281` cover NestJS, Express, Supabase Edge
  Functions, Deno Deploy, Next.js Route Handlers, Bun.serve, SvelteKit, Remix,
  Netlify Functions, and Cloudflare D1 WorkPaper smoke examples.
- Current MCP-client starter issues cover Cursor, Windsurf, MCP Inspector, VS
  Code, Claude Code, Codex, Zed, Continue, and MCPB setup notes. The completed
  Claude Desktop and Cline setup tasks closed `#282` and `#294`.
- New registry-proof starter issue `#287` asks a first-time contributor to add
  a copy-pasteable official MCP Registry API verification snippet to the
  WorkPaper docs.
- New agent-client starter issues `#288` through `#290` cover VS Code, Claude
  Code, and Codex MCP setup for the published WorkPaper stdio server.
- Current editor-client starter issues `#292` and `#293` cover Zed and Continue
  MCP setup for the published WorkPaper stdio server; Cline setup closed as
  `#294`.
- New framework and storage starter issues `#330` through `#333` cover Koa,
  Elysia, MongoDB persistence, and Univer boundary notes.
- Next.js Server Action starter issue `#336` shipped; current framework starter
  issues `#337` through `#339` cover Astro endpoints, TanStack Start server
  functions, and Qwik City route smoke examples for WorkPaper.
- New search-intent page targets server-side spreadsheet automation in Node.js
  with a TypeScript smoke test, service boundary notes, and links into the
  maintained examples:
  <https://proompteng.github.io/bilig/server-side-spreadsheet-automation-node.html>
- README and npm conversion surface: the GitHub README and package README now
  expose the Glama score badge, link the official MCP Registry and Glama pages,
  and make the npm sanity check prove formula readback after edit, JSON save,
  and restored workbook load instead of only printing a toy value.
- External contributor-directory surface: the Up For Grabs listing pull request
  is open and passing its project checks:
  <https://github.com/up-for-grabs/up-for-grabs.net/pull/5790>
- External contributor-directory surface: the Good First Issue CLI listing pull
  request is open, mergeable, and passing its security checks:
  <https://github.com/cutenode/good-first-issue/pull/1088>
- External first-time-contributor directory surface: the Awesome for Beginners
  listing pull request is open, mergeable, and adds Bilig to the TypeScript
  projects list with the `first-timers-only` label:
  <https://github.com/MunGell/awesome-for-beginners/pull/2012>
- External JavaScript spreadsheet directory surface: the JSpreadsheets listing
  pull request is open, mergeable, and adds the Bilig headless WorkPaper engine
  to `source/projects/bilig.md`:
  <https://github.com/krzysztofspilka/JSpreadsheets/pull/50>
- External JavaScript spreadsheet comparison surface: the jsgrids listing was
  already merged, and a follow-up pull request now points the Bilig entry at the
  live npm quickstart while documenting `@bilig/headless/xlsx` import/export:
  <https://github.com/statico/jsgrids/pull/94>
- External JavaScript spreadsheet benchmark surface: the js-spreadsheet-benchmark
  project now has a scoped issue for adding `@bilig/headless` as a headless
  WorkPaper target for formula, edit/readback, memory, and persistence lanes:
  <https://github.com/zhangming1978/js-spreadsheet-benchmark/issues/1>
- External open-source directory surface: the Open-Awesome submission for Bilig
  has a metadata refresh comment with the current `@bilig/headless` package
  package, proof page, benchmark evidence, and non-grid WorkPaper positioning;
  the prior `@bilig/headless@0.17.0` proof remains part of the launch-history
  trail:
  <https://github.com/chenz24/openawesome/issues/2#issuecomment-4467648527>
- External MCP ranking surface: the best-of-mcp-servers listing pull request is
  open, mergeable, and passing `yamllint` with the `@bilig/headless` npm
  package attached to the `proompteng/bilig` project entry:
  <https://github.com/tolkonepiu/best-of-mcp-servers/pull/192>
- External MCP directory surface: the TensorBlock awesome-mcp-servers listing
  pull request had a maintainer request to mirror the README entry into the
  matching category docs file. The branch now adds Bilig WorkPaper to both
  `README.md` and `docs/data-analysis--business-intelligence.md`, with a
  re-review comment posted:
  <https://github.com/TensorBlock/awesome-mcp-servers/pull/536#issuecomment-4454308656>
- External MCP directory hygiene: a newer duplicate TensorBlock pull request
  was closed on May 17, 2026 with a short note pointing back to the original
  submission, so the open path remains `#536` instead of two competing Bilig
  entries:
  <https://github.com/TensorBlock/awesome-mcp-servers/pull/557>
- External MCP directory surface: the abordage awesome-mcp listing pull request
  merged on May 14, 2026 with the Bilig repository entry in
  `repositories.yaml`:
  <https://github.com/abordage/awesome-mcp/pull/36>
- External MCP directory surface: the punkpeye awesome-mcp-servers listing pull
  request is open, mergeable, and passing its submission check with the
  required Glama score badge:
  <https://github.com/punkpeye/awesome-mcp-servers/pull/6291>
- External MCP directory surface: the YuzeHao2023 Awesome-MCP-Servers listing
  pull request is open with the Bilig WorkPaper MCP entry in the Development
  Tools category:
  <https://github.com/YuzeHao2023/Awesome-MCP-Servers/pull/244>
- External MCP registry surface: the ToolSDK MCP Registry package pull request
  is open with a `packages/developer-tools/bilig-workpaper-mcp.json` entry for
  `@bilig/headless` and the `bilig-workpaper-mcp` stdio binary:
  <https://github.com/toolsdk-ai/toolsdk-mcp-registry/pull/309>
- External MCP source-data surface: the Ever Works awesome-mcp-servers-data
  pull request is open with `data/bilig-workpaper-mcp` source files for the
  generated mcpserver.works / Awesome MCP Servers directory:
  <https://github.com/ever-works/awesome-mcp-servers-data/pull/4>
- External MCP directory surface: the mcpserve.com listing pull request is open
  with `content/servers/bilig-workpaper.md` and the npm stdio install command:
  <https://github.com/jmstfv/mcpserve/pull/19>
- External MCP directory surface: Glama published the Bilig WorkPaper server at
  <https://glama.ai/mcp/servers/proompteng/bilig>. The score badge was added to
  the punkpeye PR, replacing the `missing-glama` label with `has-glama`.
- Official MCP Registry surface: the published
  `io.github.proompteng/bilig-workpaper` entry was refreshed again to
  `@bilig/headless@0.14.0` with the existing Publish MCP Registry workflow:
  <https://github.com/proompteng/bilig/actions/runs/25812680602>
  Live API verification on 2026-05-13 returned 9 matching registry entries,
  with `0.14.0` marked as latest at the time.
- GitHub Discussion `#230` now has a maintainer update for MCP users with the
  `0.14.0` registry proof, MCPB proof, and a concrete feedback ask about the
  next useful WorkPaper tool shape:
  <https://github.com/proompteng/bilig/discussions/230#discussioncomment-16907632>
- Official MCP Registry refresh on May 14, 2026: the existing Publish MCP
  Registry workflow registered `@bilig/headless@0.14.2`, and the live Registry
  API returned 10 matching `io.github.proompteng/bilig-workpaper` entries with
  `0.14.2` marked as latest:
  <https://github.com/proompteng/bilig/actions/runs/25850256208>
- GitHub Discussion `#230` has a May 14 maintainer update for MCP users with
  the `0.14.2` registry proof, the unchanged npm stdio install command, and a
  concrete ask about named inputs, range validation, or storage-backed
  save/restore proof:
  <https://github.com/proompteng/bilig/discussions/230#discussioncomment-16916374>
- Official MCP Registry refresh on May 14, 2026: the existing Publish MCP
  Registry workflow registered `@bilig/headless@0.14.5`, and the live Registry
  API returned 11 matching `io.github.proompteng/bilig-workpaper` entries with
  `0.14.5` marked as latest:
  <https://github.com/proompteng/bilig/actions/runs/25868014475>
- GitHub Discussion `#230` has a May 14 maintainer update for MCP users with
  the `0.14.5` registry proof, the unchanged npm stdio install command, and a
  concrete ask about named input schemas, range-level validation errors, or
  storage-backed save/restore across multiple tool calls:
  <https://github.com/proompteng/bilig/discussions/230#discussioncomment-16920242>
- Official MCP Registry refresh on May 14, 2026: the existing Publish MCP
  Registry workflow registered `@bilig/headless@0.14.9`, and the live Registry
  API returned 12 matching `io.github.proompteng/bilig-workpaper` entries with
  `0.14.9` marked as latest:
  <https://github.com/proompteng/bilig/actions/runs/25882165865>
- External MCP directory surface: `mcp.directory` accepted the public server
  submission for review with repository `https://github.com/proompteng/bilig`,
  npm package `@bilig/headless`, and the WorkPaper persistence/readback
  description.
- External MCP directory surface: the mcp.so maintainer repository submission
  issue is open with the npm command, official registry name, tool list, and
  public package verification:
  <https://github.com/chatmcp/mcpso/issues/2295>
- External MCP directory follow-up: the mcp.so submission issue body was
  refreshed on May 18, 2026 with `@bilig/headless@0.21.1`, the file-backed MCP
  command, the static MCP server card, current tool names, and the maintained
  docs/transcript:
  <https://github.com/chatmcp/mcpso/issues/2295>
- External MCP directory surface: MCPFind's public submit page points
  contributors at `community-servers.yml`, and the Bilig WorkPaper PR is open
  with a single `@bilig/headless` npm entry plus repo, docs, transcript, and
  server-card evidence:
  <https://github.com/MCPFind/mcp-find/pull/37>
- External MCP directory surface: the mctrinh Awesome MCP Servers PR is open
  with a single production-ready server-list entry for Bilig WorkPaper and
  maintainer-review evidence in the PR body:
  <https://github.com/mctrinh/awesome-mcp-servers/pull/46>
- External MCP directory surface: MCPRepository has a live Bilig listing with
  the GitHub repository description mirrored as MCP server copy:
  <https://mcprepository.com/proompteng/bilig>
- External MCP directory follow-up on May 18, 2026: Glama search returns Bilig
  WorkPaper with TypeScript, Developer Tools, Workplace & Productivity, and
  Remote attributes. The Dockerfile test build
  `019e3900-c65c-73b4-b500-e3af43d37d46` succeeded and was published as
  Glama release `0.21.1`. The public Schema and Overview pages now expose the seven
  file-backed tools, and the score page reports A-grade Tool Definition Quality
  for each tool. The same npm path was smoked locally with
  `@bilig/headless@0.21.1`, server `bilig-headless-workpaper`, 7 file-backed
  tools, and `Summary!B3` display value `60000`; Glama's JSON API can lag the
  HTML listing immediately after release:
  <https://glama.ai/mcp/servers/proompteng/bilig>
- External MCP marketplace surface: the Cline MCP Marketplace server submission
  issue body was refreshed on May 18, 2026 with the GitHub repository, 400px
  logo, public npm command, `@bilig/headless@0.21.1`, the file-backed MCP
  command, current seven-tool surface, and static server-card proof:
  <https://github.com/cline/mcp-marketplace/issues/1557>
- External MCP directory surface: `mcpserver.cc` accepted the public Bilig
  WorkPaper submission for maintainer review with submission UUID
  `bcdce4e1-3b05-4be2-b611-2a2abb8baf79`. Immediate search for `bilig` still
  returned no published result:
  <https://mcpserver.cc/en?q=bilig>
- External MCP directory surface: AgentNDX accepted the public Bilig WorkPaper
  MCP submission for review through its no-login submit endpoint. Immediate API
  search for `bilig` returned `0` results before submission, so the listing is
  pending review:
  <https://agentndx.ai/browse?q=bilig>
- External MCP directory follow-up: PulseMCP still does not return Bilig in
  public search on May 17, 2026, while its API page says server data comes from
  manual submissions, automated crawling, and the Official MCP Registry. The
  Official Registry now marks `@bilig/headless@0.21.1` as latest, so the next
  PulseMCP move is a concise refresh request only if the listing remains missing
  after its ingest window.
- External MCP directory follow-up: starter issue `#384` closed after the first
  public PulseMCP verification pass. If the listing remains absent after the
  registry refresh window, reopen a narrower follow-up with the current
  `@bilig/headless@0.21.1` registry evidence:
  <https://github.com/proompteng/bilig/issues/384>.

Latest TypeScript-example guard action on May 14, 2026:

- Public conversion docs now have a `docs:discovery:check` guard that rejects
  JavaScript-labeled fences, direct dot-js smoke commands, dot-js creation
  instructions, and MJS example paths on the README, package README, core
  growth docs, and `examples/**/*.md`.
- The root README and `@bilig/headless` package README now say directly that
  runnable examples are TypeScript files, even when Node ESM import specifiers
  end in `.js` after compilation.
- The serverless example README now points SvelteKit readers at a `+server.ts`
  adapter boundary instead of a `+server.js` file.
- The completed guard replaced one closed starter with three new scoped
  first-timer issues. The Hapi route smoke
  <https://github.com/proompteng/bilig/issues/374>, AdonisJS route smoke
  <https://github.com/proompteng/bilig/issues/377>, and Oak route smoke
  <https://github.com/proompteng/bilig/issues/380> later shipped as runnable
  `framework-adapters.ts` paths, so the active queue now keeps Turso WorkPaper
  JSON persistence <https://github.com/proompteng/bilig/issues/375>, Firebase
  Genkit WorkPaper tool recipe <https://github.com/proompteng/bilig/issues/376>,
  and a Fresh WorkPaper route smoke
  <https://github.com/proompteng/bilig/issues/381>.

Latest Hapi route adapter action on May 14, 2026:

- The serverless WorkPaper API example now exercises a Hapi-style route pair in
  `examples/serverless-workpaper-api/framework-adapters.ts`: one route reads
  `/api/workpaper/summary`, and one route posts `/api/workpaper/revenue`.
- `npm run framework-adapters` now proves Fetch, Hono, Hapi, Express, and
  Fastify wrappers against the shared WorkPaper request handler, with Hapi
  returning through a typed `h.response()` toolkit shape.
- The serverless example README now includes the Hapi adapter in the expected
  output.

Latest AdonisJS route adapter action on May 14, 2026:

- The serverless WorkPaper API example now exercises an AdonisJS-style
  `HttpContext` route pair in `examples/serverless-workpaper-api/framework-adapters.ts`:
  one route reads `/api/workpaper/summary`, and one route posts
  `/api/workpaper/revenue`.
- `npm run framework-adapters` now proves Fetch, Hono, AdonisJS, Hapi, Express,
  and Fastify wrappers against the shared WorkPaper request handler, with
  AdonisJS writing status, headers, and JSON back through `ctx.response`.
- The framework adapter guide and serverless example README now include the
  AdonisJS route shape in the expected output and point contributors at the
  next first-time route task.

Latest Oak route adapter action on May 14, 2026:

- The serverless WorkPaper API example now exercises an Oak-style route pair in
  `examples/serverless-workpaper-api/framework-adapters.ts`: one route reads
  `/api/workpaper/summary`, and one route posts `/api/workpaper/revenue`.
- `npm run framework-adapters` now proves Fetch, Hono, Oak, AdonisJS, Hapi,
  Express, and Fastify wrappers against the shared WorkPaper request handler,
  with Oak receiving a web-standard `Request` from `ctx.request.source` and
  writing status, headers, and JSON back through `ctx.response`.
- The framework adapter guide and serverless example README now include the Oak
  route shape in the expected output and point contributors at the next
  first-time route task,
  <https://github.com/proompteng/bilig/issues/381>.
- External MCP directory follow-up: mcpservers.org submission was submitted in
  Dia on May 17, 2026 with category `Development`, the GitHub repo URL, the
  verified npm account contact email, and this description: "WorkPaper MCP
  server for editing formula workbooks, recalculating cells, and persisting
  JSON-backed workbook state." The form confirmed: "Bilig WorkPaper submitted
  successfully. You'll receive an email once your submission is approved."
- External MCP directory follow-up: MCP Server Spot submission form is staged
  in Dia with public project data, `Development` category, `Tools` feature,
  `GitHub` icon, Claude Desktop/Cursor/VS Code compatibility, TypeScript, stdio
  transport, npm command, and docs/repo/package links. The remaining step is
  clicking Submit, held for action-time confirmation.
- External MCP directory follow-up: the `appcypher/awesome-mcp-servers`
  repository has pull requests and issues disabled by the owner. The
  `gregkonush:codex/add-bilig-workpaper` fork branch contains the one-line
  Bilig WorkPaper addition, but GitHub rejects pull request creation because
  the upstream repository disabled PRs.

Latest MCPB execution snapshot on May 13, 2026 after the Claude Desktop bundle
pass:

- Claude Desktop adoption surface: the homepage, README, npm README,
  `llms.txt`, sitemap, and MCP client setup guide now point to
  <https://proompteng.github.io/bilig/claude-desktop-mcpb-workpaper.html>.
- Bundle path: `pnpm mcpb:workpaper:build -- --package-version 0.14.0`
  creates `build/mcpb/bilig-workpaper.mcpb` from the published npm package.
- Build proof: the MCPB manifest validates, packages `bilig-workpaper@0.14.0`,
  and emits a `4.1MB` local Claude Desktop bundle.
- Runtime proof: the generated `server/index.js` entrypoint responds to MCP
  `initialize` and `tools/list`, including `read_workpaper_summary` and
  `set_workpaper_input_cell`.

Latest PulseMCP verification snapshot on May 13, 2026 after the directory
status pass:

- Atlas search on <https://www.pulsemcp.com/servers?search=bilig&q=bilig>
  returned `0` servers for `bilig`.
- PulseMCP's submit page says server submissions are ingested from the official
  MCP Registry daily and processed weekly; if a listed official-registry server
  still does not appear after a week, maintainers should email
  `hello@pulsemcp.com`.
- The public Bilig docs now have an MCP directory status page that distinguishes
  live listings from pending reviews:
  <https://proompteng.github.io/bilig/mcp-spreadsheet-server-directory.html>.

Latest persistence-adapter distribution snapshot on May 13, 2026 after the
Postgres/Redis/object-storage adapter pass:

- GitHub Discussion `#307` now asks which storage layer should get the next
  production-shaped WorkPaper persistence recipe, with direct links to the
  runnable adapter source, service docs, and storage starter issues:
  <https://github.com/proompteng/bilig/discussions/307>
- GitHub Discussion `#308` now asks for feedback on the JavaScript spreadsheet
  library chooser page, with a direct path from grid/file/formula-engine search
  intent to the WorkPaper runtime:
  <https://github.com/proompteng/bilig/discussions/308>
- GitHub Discussion `#335` now asks OpenAI Responses API users whether the
  WorkPaper tool-call wrapper needs streaming `function_call_output`, richer
  write readback, or different audit fields:
  <https://github.com/proompteng/bilig/discussions/335>
- GitHub Discussion `#340` now asks benchmark skeptics what would make the
  WorkPaper vs HyperFormula comparison unfair, too synthetic, or too narrow:
  <https://github.com/proompteng/bilig/discussions/340>
- The public growth snapshot now records `12` GitHub Discussions and keeps the
  active feedback loops visible beside stars, npm demand, contributor
  queue health, and traffic.

Latest conversion snapshot on May 17, 2026:

- GitHub surface: `23` stars, `17` forks, `17` open issues, and `0` open pull
  requests. The star gap is still `977`; GitHub also reports `0` actual
  repository watchers/subscribers.
- npm surface: `@bilig/headless`, with `17,235` downloads in the
  latest weekly window and `32,535` downloads in the latest monthly window.
- Traffic surface: GitHub reports `602` views from `189` unique visitors and
  `28,427` clones from `3,596` unique cloners. The strongest referrers are
  GitHub, Hacker News, X, the project site, Google, Kagi, goodfirstissues.com,
  Reddit, and Slack.
- Contributor-funnel action: the public issue queue now has `15` open
  `good first issue`, `15` open `first-timers-only`, and `15` open
  `help wanted` starter issues. Keep the public path focused on the highest
  quality code/test/example tasks; do not rebuild the earlier oversized starter
  queue.
- Funnel read: cloning and npm demand are much stronger than stars. The public
  ask should stay concrete: try the npm smoke test, compare the compatibility
  limits, star/bookmark only if the workflow is relevant, and tell us what
  blocked a real adoption decision.
- Feedback surface: discussion `#157` keeps the conversion ask in one place for
  people who tried or considered the package and stopped:
  <https://github.com/proompteng/bilig/discussions/157#discussioncomment-16920401>
- Latest proof-page feedback action: the quote approval WorkPaper API proof is
  now live at
  <https://proompteng.github.io/bilig/quote-approval-workpaper-api.html> and
  posted back into discussion `#157` at
  <https://github.com/proompteng/bilig/discussions/157#discussioncomment-16938925>.
  The ask is deliberately concrete: if the service-shaped smoke is close but
  not adoptable, identify whether formula coverage, XLSX import/export,
  persistence, framework boundary, or agent/tool readback blocks the trial.
- Site conversion action: the homepage final action now links directly to the
  star page beside npm install and GitHub, and the docs index links to the live
  community growth snapshot so visitors can inspect the current public signals.
- MCP registry action: the official MCP Registry refresh was verified for
  `@bilig/headless@0.21.1` with workflow run
  <https://github.com/proompteng/bilig/actions/runs/26008585881>. The live API
  now includes `0.21.1` with `isLatest: true`, so downstream directory
  verification should be rerun after each runtime package release.

Latest star-spike research on May 16, 2026:

- GitHub stargazer timestamps show that the jump was concentrated from May 7
  through May 11, 2026: 4 stars on May 7, 4 on May 8, 7 on May 10, and 6 on
  May 11, after only two earlier April stars.
- GitHub traffic confirms the same window as the strongest visitor window:
  May 7 had `125` views from `64` unique visitors, and May 8 had `122` views
  from `42` unique visitors.
- The current traffic referrer list says the most useful external channels are
  Hacker News (`52` views / `37` uniques), X/t.co (`29` / `24`), the docs site
  (`17` / `10`), Google (`16` / `2`), Kagi (`7` / `7`),
  goodfirstissues.com (`7` / `4`), Reddit (`6` / `4`), and Slack (`3` / `1`).
- HN Algolia shows two relevant submissions on May 7:
  <https://news.ycombinator.com/item?id=48045427> at `2` points / `0`
  comments and <https://news.ycombinator.com/item?id=48052832> at `3` points
  / `0` comments. The lesson is not that HN discussion worked; it is that even
  small HN exposure sent qualified evaluators.
- The HN item API shows the first submission comment child `48045467` is dead
  and the second submission comment child `48052854` is flagged. Treat this as
  a launch-discipline failure mode: the linked page must be self-contained, and
  any follow-up comment should be added only when the thread is visibly live and
  the comment answers a real question or adds concrete proof.
- The Reddit r/coolgithubprojects post had no public comments in the current
  page snapshot:
  <https://www.reddit.com/r/coolgithubprojects/comments/1t6jo3s/i_built_a_headless_spreadsheet_engine_for_node/>.
  Treat it as weak awareness until it creates comments, referrers, issues, or
  discussion replies.
- The replicable pattern is: narrow technical audience, single proof URL,
  concrete feedback ask, public npm package, and immediate README/example/docs
  conversion. The next loop should make the HN/X/MCP follow-up about one
  adoption blocker, not a general launch.
- The post-proof CTA now routes adoption blockers to the `general` discussion
  form so HN/X visitors are asked for blocker type, workflow, attempted proof,
  and smallest unblocking evidence instead of leaving an unstructured comment.
- Timing discipline: do not submit another HN item on a weekend or immediately
  after a flagged/dead attempt. Stage the artifact first, then submit during a
  weekday US morning only if the linked page is materially new and the
  maintainer is ready to answer technical questions.
- Research alignment: GitHub's Open Source Guide says users become
  contributors because the project solves a problem for them, recommends one
  focal home URL, and warns against spamming broad communities. GitHub traffic
  docs confirm the referrer and popular-content data is a 14-day, UTC-based
  signal, so each distribution push needs a before/after snapshot.
- Trust alignment: OpenSSF Scorecard frames CI, branch protection, token
  permissions, package publishing, and maintenance as machine-checkable trust
  surfaces. Public red CI from stale runtime-package workflows is therefore a
  growth problem, not just an engineering nuisance.
- Newsletter alignment: Cooperpress publishes JavaScript Weekly and Node
  Weekly to large JavaScript/Node audiences and lists `editor@cooperpress.com`
  as the editorial contact. Use this only after the proof page and npm README
  are current; the pitch should be a short editorial suggestion, not a paid
  sponsor request.

Latest contributor-funnel action on May 14, 2026:

- GitHub traffic shows people checking the issue queue, but the repository had
  `0` open pull requests and `106` first-time starter issues to scan.
- A pinned issue now gives first-time visitors a short map of current code/test,
  examples, agent, and MCP starter picks:
  <https://github.com/proompteng/bilig/issues/372>.
- The issue is intentionally a navigation surface, not a fake contribution
  request: it points contributors at existing scoped tasks and asks them to
  comment on the target issue before opening a PR.

Latest XLSX oracle feedback action on May 14, 2026:

- GitHub Discussion `#382` asks people who evaluate spreadsheet engines how a
  headless runtime should handle stale XLSX cached formula values, fresh Excel
  recalculation oracles, cache-only diagnostics, and CI-safe private workbook
  reports:
  <https://github.com/proompteng/bilig/discussions/382>.
- Starter issue `#383` turns that feedback thread into a small first-time
  contribution: add a sanitized sample `summary.md` or issue draft so evaluators
  can see the safe report shape before running the oracle harness on private
  workbooks:
  <https://github.com/proompteng/bilig/issues/383>.
- The stale-cache walkthrough now points readers at that feedback thread so the
  public accuracy framework can be challenged without turning stale embedded
  workbook caches into fake wins or fake bugs:
  <https://proompteng.github.io/bilig/xlsx-corpus-verifier-walkthrough.html>.

Latest technical-content action on May 14, 2026:

- The agent/workbook API article source now leads with the maintained
  empty-directory `@bilig/headless` eval instead of asking readers to clone the
  monorepo first.
- The canonical page and DEV article source both show the same TypeScript
  proof shape: create workbook state, edit one input, read the recalculated
  value, serialize WorkPaper JSON, restore it, and read the restored value.
- Public pages:
  <https://proompteng.github.io/bilig/why-agents-need-workbook-apis.html> and
  <https://github.com/proompteng/bilig/blob/main/docs/dev-to-workbook-apis-post.md>.
- Do not route new evaluator traffic to the older public DEV copy until it is
  edited by the article owner. A Dia check on May 16, 2026 found that public
  article still showing stale `46/46` benchmark evidence while the current
  checked package evidence is `@bilig/headless@0.40.43`, `94/100` comparable
  mean wins, and `93/100` mean+p95 wins.

Latest search-intent boundary action on May 14, 2026:

- A new Google Sheets API boundary page targets backend developers who are
  deciding whether their workflow needs a hosted collaborative spreadsheet or a
  local WorkPaper owned by a Node service.
- The page does not claim that `bilig` replaces Google Sheets. It says to use
  Google Sheets API when sharing, permissions, spreadsheet IDs, and a durable
  Google Workspace URL are the product.
- The same page gives an empty-directory TypeScript smoke test for the local
  WorkPaper case: install `@bilig/headless`, build workbook state, edit one
  input, read a recalculated value, save JSON, restore it, and verify the
  restored value.
- Starter issue `#385` gives a first-time contributor a focused follow-up:
  add a Sheets API handoff checklist to the boundary page without making broad
  replacement claims:
  <https://github.com/proompteng/bilig/issues/385>.
- Public page:
  <https://proompteng.github.io/bilig/google-sheets-api-alternative-node-workpaper.html>.

Latest homepage polish action on May 14, 2026:

- The homepage first viewport now leads with the product name `bilig` and the
  plain category line "Headless workbooks for TypeScript services."
- The hero copy says exactly what the package does: keep a workbook-shaped
  formula model, change inputs from code, read the formula result, and save the
  workbook as JSON.
- The product visual is now a generated `bilig-hero-workbook-api.png` asset
  instead of a CSS-composed table/code mockup that can overlap at narrow widths.

Latest HN conversion signal on May 14, 2026:

- The checked-in public growth snapshot records `news.ycombinator.com` as a top
  referrer with `51` views from `36` unique visitors.
- The two public Show HN submissions are
  <https://news.ycombinator.com/item?id=48045427> and
  <https://news.ycombinator.com/item?id=48052832>. The HN Algolia API returned
  `2` points and `0` comments for `48045427`, and `3` points and `0` comments
  for `48052832`.
- There is no HN comment thread to answer right now. The next HN move is not
  reposting; it is making the landing page, README, and narrow benchmark asks
  convert the traffic that already arrived.

Latest star-jump attribution snapshot on May 17, 2026:

- GitHub stargazer timestamps show the jump concentrated on May 7-11: 4 stars
  on May 7, 4 on May 8, 7 on May 10, and 6 on May 11. No later stargazer
  timestamp is visible in the current API result.
- The jump started the same day as the two public Show HN submissions:
  `48045427` at `2026-05-07T04:34:01Z` and `48052832` at
  `2026-05-07T18:16:44Z`. HN Algolia still reports only `2` and `3` points
  with no comment thread, so the likely mechanism was qualified repo discovery,
  not a discussion breakout.
- GitHub traffic for May 7-8 was `247` views from `106` unique visitors and
  `9,571` clones from `1,197` unique cloners. Current top referrers still show
  Hacker News at `52/37`, ahead of `t.co` at `29/24` and Reddit at `6/4`.
- Replication action: keep the `headless-spreadsheet` wedge that HN/LibHunt
  already understood, but make the project easier for broader classifiers to
  place. GitHub topics now trade narrower custom tags for `ai-agents` and
  `excel`, while npm metadata keeps the exact agent and formula-recalculation
  terms.

Latest LibHunt discovery snapshot on May 17, 2026:

- LibHunt has a live `headless-spreadsheet` topic page that includes Bilig:
  <https://www.libhunt.com/topic/headless-spreadsheet>.
- The entry is explicitly tied to the May 7 Show HN mention and categorizes the
  project under TypeScript, Spreadsheet, Excel, Agents, and `ai-agents`.
- The LibHunt card still shows stale stars and an older broad description. The
  current GitHub repository description is the tighter WorkPaper/runtime copy:
  "Formula WorkPaper runtime for Node.js services and agent tools: edit cells,
  recalculate, verify readback, persist JSON."
- Replication action: treat LibHunt as evidence that the HN/topic classifier
  path worked. Keep the repo and npm package metadata aligned to the same
  classifier vocabulary so LibHunt-style indexers refresh toward the sharper
  positioning.

Latest Product Hunt launch surface on May 14, 2026:

- The public launch kit is now wired into the docs site:
  <https://proompteng.github.io/bilig/product-hunt-launch-kit.html>.
- It keeps the tagline, short description, first comment, proof links, thumbnail,
  gallery images, WebM demo, and launch checklist together so the next launch
  action can use the real assets instead of rewriting copy in a browser form.
- The launch kit also records the Product Hunt-specific guardrails: submit from
  a personal maker account, ask for feedback instead of upvotes, keep the
  tagline at `53 / 60` characters, keep the description at `214 / 500`
  characters, use `240x240` thumbnail art, use `1270x760` gallery images, and
  use a YouTube link if video is added to the Product Hunt form.

## Goal Text

Grow `proompteng/bilig` from `8` to `1,000` legitimate GitHub stars by making
`@bilig/headless` the obvious headless spreadsheet engine for Node services,
coding agents, and workbook automation.

Execution update: use Atlas or Dia through Computer Use, plus authenticated
personal accounts where they are relevant, to research, stage, and execute
growth work. Public browser-side actions such as submitting posts, comments,
likes, or forms still need a final action-time confirmation before the click.
Private drafts, account-backed GitHub PRs/issues, directory submissions, SEO
edits, assets, and repo/community maintenance should be executed directly when
they advance legitimate adoption.

The star goal is a proxy for useful adoption, not the product. The real target
is a repeatable external-user loop:

1. A developer sees a concrete workbook-automation problem.
2. They find a short `@bilig/headless` example that matches the problem.
3. They run it without cloning the monorepo.
4. They see formula or persistence proof, not a toy printout.
5. They bookmark the repo, open an issue, or ask for a missing workflow.

## Research Inputs

- GitHub's Open Source Guide says promotion starts with a clear message, a
  single home URL, going where the exact audience already is, asking for
  feedback, and helping people before asking for attention:
  <https://opensource.guide/finding-users/>
- GitHub Docs says repository topics help people find projects to use and
  contribute to, and topic choices should describe purpose, subject area,
  community, and language:
  <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics>
- Current HN evidence says the generic Show HN post did not break out. The next
  move should be targeted, evidence-led replies and adjacent problem-solving,
  not reposting the same launch pitch.

## Growth Hacks That Are Allowed

These are aggressive but legitimate. They optimize distribution around a real
library and real proof.

### 1. Piggyback On Existing Search Intent

Create narrowly titled pages and examples for exact searches people already
make:

- `headless spreadsheet engine for Node`
- `HyperFormula alternative`
- `spreadsheet engine for agents`
- `Vercel AI SDK spreadsheet tool`
- `LangChain spreadsheet tool`
- `evaluate Excel formulas in Node`
- `persist formula backed workbook JSON`
- `server side spreadsheet automation`
- `XLSX formula cache verifier`

Every page should have one runnable command, one expected output block, and one
link back to the repo star URL. Do not ask for stars before the example proves
something.

### 2. Turn Benchmarks Into A Distribution Loop

The `94/100` WorkPaper mean-win claim should become small, quotable artifacts:

- one chart image for X, Bluesky, LinkedIn, and README embeds:
  [`docs/assets/workpaper-benchmark-card.png`](assets/workpaper-benchmark-card.png)
- one short post explaining the worst p95 row honestly
- one "run this benchmark locally" post
- one "what would make this benchmark unfair?" discussion prompt:
  <https://github.com/proompteng/bilig/discussions/340>

The hack is to invite skeptics into the measurement instead of only announcing
a win. Spreadsheet-engine users trust reproducible evidence more than launch
copy.

### 3. Mine Competitor And Adjacent Issues For Real Problems

Search public issues and discussions in adjacent tools for unsolved workflows:
HyperFormula, ExcelJS, SheetJS, formula.js, Handsontable, AG Grid, agent
frameworks, LangChain, LlamaIndex, and Vercel AI SDK examples.

When someone has a problem `@bilig/headless` genuinely solves, answer with:

1. the relevant diagnosis,
2. a tiny runnable snippet,
3. a disclosure that you maintain `bilig`,
4. the repo link only after the solution.

Do not necro-bump old issues unless the answer is materially useful.

### 4. Package Every Example As A Shareable Gist-Sized Artifact

For each high-intent workflow, keep the example small enough to paste:

- revenue model with formulas and restore
- JSON records to WorkPaper
- serverless JSON route to WorkPaper
- CSV-shaped input to WorkPaper
- agent writeback and verification
- named-expression update
- formula cache mismatch verifier
- unsupported formula troubleshooting

Each example needs a title that names the user problem, not the internal
package architecture.

### 5. Use Feedback Loops Instead Of Launch Blasts

Post asks that are easy to answer:

- "What spreadsheet automation workflow would make this worth trying?"
- "Which Excel formulas would block you from replacing a headless engine?"
- "Does this WorkPaper API feel too custom, or boring enough to script?"
- "What benchmark row looks suspicious?"

The point is to make experts correct the project in public. Useful corrections
create better issues, better docs, and more credible follow-up posts.

### 6. Convert npm Demand Into GitHub Stars

The npm page already has visible downloads while GitHub stars are low. Add or
keep star/bookmark CTAs only after value proof:

- after the quickstart expected output
- after the benchmark evidence link
- after the external-consumer example
- after troubleshooting recipes

Good CTA:

> If this saves you a workbook-automation spike, star the repo so the package is
> easier to find later: <https://github.com/proompteng/bilig>

Avoid generic "please star" copy at the top of technical docs.

### 7. Build A Contributor Discovery Flywheel

Keep at least three current starter issues alive. Each starter issue should
ship one new shareable example or compatibility reduction. That turns
contributor onboarding into public marketing:

- new issue names a real user workflow
- PR adds a runnable example
- release notes mention the example
- docs link it from package README
- social post explains the workflow

## Channel Copy

### X / Bluesky Thread

```text
1/ I am working on @bilig/headless.

It is for the boring spreadsheet cases that end up in backend code anyway:
pricing rules, payout checks, quote calculators, import validators.

2/ The shortest eval now starts from an empty npm project:
https://github.com/proompteng/bilig#try-it-in-90-seconds

It edits an input cell, reads the recalculated value, saves WorkPaper JSON,
restores it, and checks the value again.

3/ Current benchmark artifact: 94/100 comparable mean-latency rows are faster
than the HyperFormula-style baseline.

The worst p95 row is public too: structural-move-rows is the visible worst p95
row, and UI rendering is not part of that benchmark.

4/ If you have shipped spreadsheet automation from Node, what would make you
reject this library in five minutes?
```

### Short Evidence-Led Post

Use this when the audience already cares about Node services, coding agents,
spreadsheet automation, or headless formula engines. Do not post it unchanged
to every channel.

```text
I maintain Bilig. The public npm package is @bilig/headless.

It exists because I do not want backend jobs or coding agents clicking around a
spreadsheet UI and then treating a screenshot as proof.

The quickest way to judge the package starts from an empty directory:

1. npm install @bilig/headless
2. download the maintained eval.ts file
3. run it with tsx
4. inspect the before/after/afterRestore output

The example builds a small formula workbook, edits an input, reads the dependent
formula result, serializes WorkPaper JSON, restores it, and checks that the
restored value still matches.

Repo quickstart:
https://github.com/proompteng/bilig#try-it-in-90-seconds

This is not an Excel clone. It is for the smaller case where workbook formulas
are service logic and the code path needs readback plus persisted state.

Compatibility limits are documented:
https://github.com/proompteng/bilig/blob/main/docs/where-bilig-is-not-excel-compatible-yet.md

The benchmark claim is intentionally narrow: 94/100 comparable mean-latency
wins against HyperFormula-style workloads, structural-move-rows is the visible
worst p95 row, and UI rendering is not part of the benchmark.

If you automate spreadsheets from Node, what would make you reject this API
quickly?
```

### Hacker News Follow-Up Comment

Do not repost the same Show HN. Add a follow-up only when there is new proof or
a concrete question:

```text
Follow-up after the Show HN: I am looking for rejection reasons, not "nice
project".

The package is for Node code that needs to change workbook inputs, recalculate,
read the result, and save the workbook-shaped state as JSON. No browser grid in
the runtime path.

If you have shipped something with HyperFormula, ExcelJS, SheetJS, or the Google
Sheets API: what would make you reject this API quickly?
```

### Hacker News Submission After The Formula Workbooks Page

Use this only when the linked page is live and the submitter is ready to answer
technical questions in the thread. Do not add an immediate generic first
comment; the last two HN child comments were dead or flagged. If the HN item
stays live and someone asks for details, answer with the concrete proof,
limitations, and maintainer disclosure in the thread.

Title:

```text
Show HN: Bilig runs small formula workbooks in Node
```

URL:

```text
https://proompteng.github.io/bilig/formula-workbooks-node-services-agent-tools.html
```

Optional response comment, only after the thread is visibly live or someone asks
for details:

```text
I maintain this project. The linked page is the shorter version after the
earlier Show HN.

The runnable proof starts from an empty Node directory, installs
@bilig/headless, changes quote inputs, recalculates net revenue / gross margin /
approval decision, saves WorkPaper JSON, restores it, and checks the same result
again.

The package is for backend workflows where spreadsheet formulas are business
logic but opening a browser grid is the wrong runtime boundary. It is not a full
Excel clone, and the compatibility gaps are public.

Useful feedback would be specific: missing formula families, import/export
cases, persistence shape, or any API choice that would make you reject it.
```

### JavaScript Weekly / Node Weekly Editorial Pitch

Use email only after action-time confirmation because this contacts an external
editorial inbox. Send to Cooperpress editorial, not the advertising form, and
keep the link suggestion concise.

Subject:

```text
Link suggestion: Formula workbooks for Node services
```

Body:

```text
Hi Cooperpress editors,

I maintain Bilig, an MIT TypeScript library with a published Node package:
https://www.npmjs.com/package/@bilig/headless

The shortest decision page is here:
https://proompteng.github.io/bilig/formula-workbooks-node-services-agent-tools.html

It shows a runnable empty-directory Node proof for formula-backed WorkPaper
documents: install @bilig/headless, write quote inputs into cells, recalculate
net revenue / gross margin / approval decision, serialize the workbook JSON,
restore it, and verify restoredMatchesAfter.

This is aimed at backend services and coding-agent tools where spreadsheet
formulas are business logic but opening Excel, Google Sheets, or a browser grid
is the wrong runtime boundary. The page also includes benchmark caveats and
explicit notes on when HyperFormula, SheetJS, ExcelJS, or Google Sheets API are
better choices.

If it is a fit for JavaScript Weekly or Node Weekly, I would appreciate a look.

Greg
```

### Reddit / Community Post

```text
I am looking for feedback from people who automate spreadsheets from Node.

Project: @bilig/headless
Repo: https://github.com/proompteng/bilig

It is a TypeScript workbook runtime: formula evaluation, structural row/column
edits, range reads, JSON persistence, and verification after writes.

The docs include a quick npm-only smoke test and benchmark evidence against
HyperFormula-style workloads. It is early infrastructure, not a complete Excel
clone.

What I am trying to learn: which workflows, formulas, or file cases would make
you reject this quickly?
```

### GitHub Discussion Prompt

```text
Which headless spreadsheet workflow should @bilig/headless prove next?

Current supported path:

- build a workbook from data
- evaluate formulas
- apply structural edits
- read ranges
- persist and restore JSON
- verify agent writes

Candidates:

- more XLSX formula-cache corpus reductions
- more finance-model examples
- a LangChain / Vercel AI SDK tool-calling example
- broader formula compatibility fixtures
- a migration guide from HyperFormula

If you have a real workflow, please describe the input shape, formulas, and the
output you need to trust.
```

Live workflow-feedback thread:
<https://github.com/proompteng/bilig/discussions/157>

Live five-example show-and-tell thread:
<https://github.com/proompteng/bilig/discussions/213>

Search-targeted page for the five runnable Node workbook automation examples:
<https://proompteng.github.io/bilig/workbook-automation-examples-node.html>

Live serverless-route feedback thread:
<https://github.com/proompteng/bilig/discussions/167>

## Weekly Operating Cadence

Every week until `1,000` stars:

1. Ship one public-facing example, comparison, or fixture writeup.
2. Answer five relevant external threads where the answer helps even if nobody
   clicks through.
3. Open or refresh three starter issues tied to shareable examples.
4. Publish one short evidence-led post.
5. Record stars, npm downloads, referrers, issue sources, discussion activity,
   and external PRs.
6. If a channel produces no useful feedback after two attempts, change the
   angle before posting there again.

Capture the baseline before and after each distribution push:

```sh
pnpm community:growth:snapshot
```

Publish the current Markdown snapshot when the weekly operating cadence changes
or after a major distribution push:

```sh
pnpm community:growth:snapshot:markdown
```

Current checked-in snapshot:
[`docs/community-growth-snapshot.md`](community-growth-snapshot.md).

Latest JavaScript-library comparison starter snapshot on May 13, 2026:

- Starter issues `#309` through `#314` now cover Handsontable, AG Grid,
  SheetJS, ExcelJS, HyperFormula, and Formula.js boundary notes for the
  JavaScript spreadsheet library guide.
- Starter issues `#315` through `#319` covered Mastra, LlamaIndex.TS,
  LangGraph.js, CopilotKit, and Cloudflare Agents WorkPaper tool recipes and
  were closed after the framework pages shipped in `fd2cb58f8`.
- Replacement starter issues `#323` through `#327` now cover verification
  transcripts, LangGraph state handoff, CopilotKit UI result copy, and
  Cloudflare Agents persistence notes for the same framework pages.
- Starter issues `#328` and `#329` cover social preview contributor guidance
  and OpenGraph cache-busting notes for public distribution work.
- The public growth snapshot now records `89` open `first-timers-only`,
  `good first issue`, and `help wanted` issues, with `89` generally available
  and `0` already in review.

Latest agent-framework search-intent snapshot on May 13, 2026:

- Five framework-specific WorkPaper tool pages now target people searching for
  spreadsheet tools inside Mastra, LlamaIndex.TS, LangGraph.js, CopilotKit, and
  Cloudflare Agents:
  <https://proompteng.github.io/bilig/mastra-workpaper-spreadsheet-tool.html>,
  <https://proompteng.github.io/bilig/llamaindex-workpaper-spreadsheet-tool.html>,
  <https://proompteng.github.io/bilig/langgraph-workpaper-toolnode-spreadsheet.html>,
  <https://proompteng.github.io/bilig/copilotkit-workpaper-spreadsheet-action.html>,
  and
  <https://proompteng.github.io/bilig/cloudflare-agents-workpaper-spreadsheet-tool.html>.
- Each page points to the same checked `npm run agent:framework-adapters`
  example so the SEO surface is tied to verified formula readback, JSON
  persistence, and restored-workbook proof instead of framework-name stuffing.

Set `GITHUB_TOKEN` or `GH_TOKEN` with repository traffic access, or run with an
authenticated `gh` CLI session, to include recent discussion activity, views,
clones, popular referrers, and popular paths. Without either authenticated
source, the snapshot still records public GitHub stars, forks, open issues,
package version, and npm download windows.

## Anti-Spam Rules

- Do not buy stars, trade stars, automate follows, or ask unrelated audiences
  for stars.
- Do not claim full Excel compatibility.
- Do not claim blanket performance wins; keep the worst p95 row visible.
- Do not post the same launch copy across communities.
- Do not hide that the maintainer is recommending their own project.
- Do not contact people through private channels unless there is a specific,
  relevant reason and the message would still be useful without a repo link.

## Success Metrics

Primary:

- `1,000` legitimate GitHub stars on <https://github.com/proompteng/bilig>

Leading indicators:

- npm weekly downloads
- GitHub traffic and referrers
- external issues with real workbook examples
- external PRs
- GitHub Discussions from non-maintainers
- stars per public post
- stars per new runnable example
- conversion from npm README visits to GitHub stars

If stars rise but no external users ask questions or open issues, the growth is
weak. If external users bring real workflows and compatibility gaps, the flywheel
is working even before the star count catches up.
