Skip to content

[Docs] README: mark as open source, add reference site, set v0.0.1 - #117

Merged
vedanshujain merged 3 commits into
mainfrom
docs/oss-readme-v0-0-1
Jul 28, 2026
Merged

[Docs] README: mark as open source, add reference site, set v0.0.1#117
vedanshujain merged 3 commits into
mainfrom
docs/oss-readme-v0-0-1

Conversation

@vedanshujain

Copy link
Copy Markdown
Contributor

Prepares the README for going public.

Changes

Title — now # Urumi — an open-source commerce layer for EmDash, with MIT and version badges.

"What this is" — three parts, not two. Added the reference site (sites/staging) as a first-class component alongside the plugin and the service: it's the default EmDash site with the plugin already registered, the storefront in the screenshot, and what the quick start boots. Flagged that it's catalog + cart only today.

"Why two parts" — the split is meant to collapse. Added the upstream story: emdash-cms/emdash#2169 adds ctx.storage.<collection>.updateIf(id, { where, set?, delta? }) — one guarded UPDATE … RETURNING, exactly the statement the README already prints — so a plugin can decrement stock race-free with no companion database.

Two things stated honestly rather than optimistically:

  • #2169 is a Draft, not pending approval.
  • #2169 alone does not retire the service. The @urumi/store-emdash proof adapter passes the full InventoryStore contract in-process (real-Postgres no-oversell race + idempotent replay included), but it calls updateIf (5×), insert (3×), and batch (5×) — and insert/batch are not upstream yet. Folding orders, payments, webhooks, and reporting into the plugin needs those two as well.

Version 0.0.1 — the six publishable @urumi/* packages go 0.1.0 → 0.0.1, and Status names the version and notes nothing is published to npm. Internal deps are all workspace:*, so no dependency specifiers changed and the lockfile is untouched.

Notes

  • No changeset. The version fields are a hand-set release baseline, and nothing is published; a changeset would bump them straight off 0.0.1 on the next release run. Happy to add one if you'd rather drive this through changesets.
  • packages/service/tsdown.config.ts and sites/staging/emdash-env.d.ts had unrelated pre-existing working-tree changes — deliberately left out of this branch.

Verification

pnpm typecheck clean; pnpm install --lockfile-only reports the lockfile already up to date. Docs + version metadata only — no runtime code touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XXBjHj6foi2JpL6az7DfyQ

Prepare the README for the public repo:

- Title marks the project as open source; add MIT + version badges.
- "What this is" now lists three parts, not two — the reference site
  (sites/staging) is called out as the default site that uses the plugin
  and the thing the quick start actually boots.
- "Why two parts" notes that emdash-cms/emdash#2169 (draft) adds the
  guarded updateIf primitive that closes the no-oversell race in-sandbox,
  and that a @urumi/store-emdash adapter already proves the InventoryStore
  contract in-process. Also states plainly what #2169 does NOT cover:
  the atomic insert and batch primitives are not upstream yet, so the
  rest of the service can't fold into the plugin on that PR alone.
- Set the six publishable @urumi/* packages to 0.0.1 to match, and say so
  under Status.

No changeset: the version fields are being set to a release baseline by
hand, and nothing is published to npm — a changeset would bump them off
0.0.1 on the next release run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XXBjHj6foi2JpL6az7DfyQ
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

vedanshujain and others added 2 commits July 28, 2026 10:09
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XXBjHj6foi2JpL6az7DfyQ
Correctness under concurrency is table stakes for commerce, not a
feature to lead with. Reframe the section around the actual gap — the
sandbox can't express a guarded update, a uniqueness constraint, or a
multi-document commit — with inventory as one instance rather than the
headline. Drops the display SQL block and the "one atomic operation that
matters" framing; the section is ~13 lines shorter.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XXBjHj6foi2JpL6az7DfyQ
@vedanshujain
vedanshujain merged commit bd5d9a8 into main Jul 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant