Trazza

Texto del repositorio público, commit 8729248. Fuente: docs/oss-export.md.

OSS export tree (tools/oss/export-oss.mjs)

What it does

Builds a publishable copy of the repository under a target directory:

  1. Lists paths with git ls-files (only tracked files; no .git, node_modules, or untracked secrets).
  2. Skips every path matched by the same rules as tools/oss/check-sanitized.mjs (.claude/, deploy/, docs/claude/{production,growth,history}.md, informes/, root test*.js, etc.).
  3. Strips forbidden substrings (`, `) from text files in the copy only.
  4. Merges into .gitignore: informes/, .env*, e2e/artifacts/.
  5. Adds .dockerignore when the tree did not already have one.
  6. Runs checkSanitized({ root: targetDir, hashesFile }) and exits non-zero on violations (path + reason only).

Usage

node tools/oss/export-oss.mjs /path/to/oss-export [--hashes /path/to/hashes.txt]

Gastos in the export

The export includes the Gastos (expenses and savings) UI, route, tables and tests. Access is a universal opt-in (isExpensesFeatureAllowed: any non-empty email; each user enables the module with user_preferences.expenses_enabled). User-facing documentation is written to docs/gastos.md during the export if it is not already present. docs/claude/expenses.md from the product repo is excluded.

In-memory filters on the oss-merge migrations

The published origin files are not edited. Two later origin steps would otherwise fail if the raw oss-merge chain were applied verbatim:

Both transforms live in tools/oss/export-oss.mjs and are applied through filterOssPgMigrationContent. The origin test:pg harnesses call the same function when they load those files (they do not rewrite them on disk).

The raw oss-merge chain is not deployable

Applying supabase/baseline + supabase/migrations verbatim from this branch (the unfiltered oss-merge chain) is not a supported deploy path: 20261107001100 would drop the Gastos tables, 20261107000200 would drop the plan-guard function, and 20261111000100 would fail. The publishable, applyable artifact is the export produced by tools/oss/export-oss.mjs. Use that tree (or the harness filters, in tests only) to apply migrations.

e2e

e2e/dashboard.smoke.mjs opens /app/settings and clicks Guardar. It must only run against a local or test app (BASE_URL, default http://localhost:3000). It must never be pointed at production. When no local/test server is available, this smoke is left pending.