Create new production release

.agents/skills/vortex-review/SKILL.md

@@ -26,6 +26,11 @@ the implementing session or via `/address-feedback`.
   A stale snapshot on the branch = automatic P1 finding.
 - Read the PR description and any linked proposal/ADR: findings include "the change
   doesn't achieve its stated intent", not just "the code is wrong".
+- Public-repo check (CLAUDE.md "Public Repository: No Client Data"): scan the diff, every
+  commit message in the range, the branch name, and the PR title and body for client,
+  partner or prospect names, commercial terms tied to a named party, and production
+  personal data. Any hit is an automatic P1 finding. Cite its location only: never repeat
+  the name or term in the report or in anything posted to GitHub.
 
 ## 2. Round 1 — finder fleet
 

.github/copilot-instructions.md

@@ -11,6 +11,7 @@
 
 ## Repository invariants
 
+- This repository is public. Flag customer, business-client, partner or prospect names, commercial terms tied to a named party, and production personal data anywhere in the change, including fixtures, the PR title and the PR description. Point to the location without repeating the name or term in your comment.
 - Treat `docs/security-spec/` as normative for security-sensitive behavior. Flag code/spec contradictions and behavior changes that leave the relevant specification stale.
 - Treat public OpenAPI schemas, `packages/sdk` exports, and shared wire types as compatibility contracts. Check consumers and documentation when their shapes, semantics, defaults, or errors change.
 - Changes to `packages/shared` can affect every application. Check downstream assumptions, and require the shared build before consumer verification.

.github/workflows/e2e.yml

@@ -71,6 +71,8 @@ jobs:
         if: always()
         working-directory: apps/api
         env:
+          # Live test: skips the hermetic preload, whose fetch guard would block these calls.
+          RUN_LIVE_TESTS: "1"
           VORTEX_QUOTE_SMOKE_URLS: https://api-staging.vortexfinance.co,https://api.vortexfinance.co
         run: bun test src/tests/deployed-quotes.e2e.test.ts
 

CLAUDE.md

@@ -102,6 +102,11 @@ update the existing canonical document when one owns the topic.
   `docs/adr-NNNN-<topic>.md`, with current behavior updated in the relevant maintained
   document.
 - Keep local `README.md` files only when they explain a non-obvious subsystem contract.
+- Never add a document written for a specific client or partner, or one that tracks
+  commercial gates, terms or negotiation status (see "Public Repository: No Client Data").
+- Operator runbooks are maintained outside this repository. Cite them by name and section
+  (for example "runbook §2.7"); when a change alters a documented procedure, say so in the
+  pull request description.
 - Repair indexes and relative links in the same change as a move or deletion.
 - Agent skills live in `.agents/skills/<name>/SKILL.md` so every coding agent can use
   them; `.claude/skills/` holds only symlinks to those directories (Claude Code follows
@@ -139,6 +144,27 @@ Commit examples from history: `fix(api): keep active phase retries below lock ex
 `feat(dashboard): add searchable token selection`, `docs(dashboard): sync implemented
 feature specs`.
 
+## Public Repository: No Client Data
+
+This repository is public. Files, commit messages, branch names, PR titles and
+descriptions, and review comments are world-readable, and git and GitHub keep every
+earlier version even after an edit.
+
+- Never name customers, business clients, partners, prospects, or their end users. Write
+  "the partner", "a business client", or another neutral role, even when the user or the
+  task context uses the real name. Providers the code already integrates (for example
+  Monerium or Avenia) are not clients and may be named.
+- Keep commercial details out as well: agreement and negotiation status, prices, fees or
+  discounts agreed with a specific party, onboarding status, contacts, and anything quoted
+  from a client conversation.
+- Never commit production personal data (names, emails, tax IDs, IBANs, wallet addresses
+  tied to a person). Fixtures use obviously fake values such as `@example.com`, and must
+  not hint at a real client in disguise.
+- Before every commit, push, `gh pr create`, `gh pr edit`, or review comment, check the
+  diff, message, branch name, and PR title and body for any of the above.
+- If something already leaked, stop and tell the user. Never write a commit message, PR
+  title, or comment that explains what was removed or why.
+
 ## Lean, Safe Fixes
 
 For fixes, prefer the smallest change that fully resolves the demonstrated root cause

apps/api/.env.example

@@ -9,7 +9,7 @@ BROWSER_SDK_ORIGINS=
 # Environment Configuration
 SANDBOX_ENABLED=false
 
-# Sales-demo account (sandbox only) — see docs/operations-demo-environment.md
+# Sales-demo account (sandbox only) — see the internal demo-environment runbook
 DEMO_ACCOUNT_EMAIL=demo@satoshipay.io
 # Serves Alfredpay KYB from canned in-process responses so the demo corridor can be
 # re-onboarded endlessly. Refuses to start unless DEPLOYMENT_ENV=sandbox.

apps/api/scripts/monerium-b2b-sandbox-e2e.ts

@@ -1,6 +1,6 @@
 /**
  * End-to-end run of the Monerium B2B onramp against a live backend, the sandbox or a local
- * rehearsal (docs/operations-monerium-b2b-runbook.md §8). It registers a client's destination
+ * rehearsal (B2B operations runbook §8). It registers a client's destination
  * the way the partner does, waits until the keeper has deployed, linked and activated the
  * account, then waits for one EUR payment and checks on chain that it was converted and
  * forwarded, or refunded with --refund.

apps/api/scripts/seed-demo-account.ts

@@ -5,7 +5,7 @@
  *
  * Sandbox only — the restore routine itself refuses to run anywhere else. The demo profile
  * must have signed in once via OTP first; the seed cannot forge a Supabase Auth user.
- * See docs/operations-demo-environment.md.
+ * See the internal demo-environment runbook.
  */
 import path from "node:path";
 import dotenv from "dotenv";