Docs: charter, code of conduct, testing plan, leak fixes

- Adds PROJECT_CHARTER.md, CODE_OF_CONDUCT.md, TESTING.md
- Fills contact email and maintainer entries
- Corrects TESTING.md sample-cases table to match the actual suite
- Removes residual internal-process language from
  vitest.config.ts, .gitignore, CONTRIBUTING.md, tests/README.md,
  and the PR template

Author: jpmarindiaz

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,11 +1,4 @@
-<!--
-Thanks for contributing! A few quick things before you submit:
-
-This repo is a public mirror — your PR will be reviewed here, applied
-upstream by a maintainer, and then merged in this repo. Your commit
-attribution stays on the PR. See CONTRIBUTING.md → "How PRs get merged"
-for the full flow.
--->
+<!-- Thanks for contributing! See CONTRIBUTING.md for the full guidelines. -->
 
 **What this changes**
 

.gitignore

@@ -8,8 +8,7 @@ coverage
 .vite
 deno.lock
 
-# Internal-only files written by the sync script — NEVER committed.
-# These contain context about the public/private split and the sync model.
+# Local-only workspace files — never committed.
 .local/
 CLAUDE.md
 .claude/

CODE_OF_CONDUCT.md

@@ -0,0 +1,35 @@
+# Code of Conduct
+
+The MonkeyTab project has adopted the **Contributor Covenant, version 2.1** as its code of conduct. The full text is available at:
+
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct/>
+
+## Why we adopted it
+
+The Contributor Covenant is the most widely used open-source code of conduct. It is concise, comprehensive, well-understood by contributors across the ecosystem, and maintained centrally so it stays current. Linking to the canonical version (rather than copying it inline) means the project automatically benefits from clarifications and improvements made upstream.
+
+## Scope
+
+This code of conduct applies to all project spaces — the GitHub repository, issue tracker, pull requests, discussions, and any other forum the project officially uses. It also applies when an individual is officially representing the project in public spaces.
+
+## Reporting concerns
+
+If you observe behavior that violates this code of conduct, please report it confidentially by emailing the maintainers at **info@datasketch.co**.
+
+Reports will be reviewed promptly. Reporters will not be identified to the person being reported without their consent. Maintainers will treat all reports seriously and apply enforcement consistently across the community.
+
+## Enforcement
+
+Maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate corrective action in response to any behavior they deem inappropriate, threatening, or unwelcoming.
+
+Possible actions include (but are not limited to): a private warning, a public clarification of expectations, removal of comments or commits, temporary suspension from project spaces, or permanent removal from the community. Decisions are made by the maintainer team and are not subject to public debate, though they will be explained to the affected parties.
+
+## Attribution
+
+This code of conduct is based on the Contributor Covenant, version 2.1, available at <https://www.contributor-covenant.org/version/2/1/code_of_conduct/>.
+
+For answers to common questions, see the Contributor Covenant FAQ at <https://www.contributor-covenant.org/faq>.
+
+---
+
+*Code of Conduct v0.1 · last updated 2026-04-08*

CONTRIBUTING.md

@@ -58,7 +58,7 @@ monkeytab/
 │   ├── browser/           # The @datasketch/monkeytab entry point
 │   └── adapters/
 │       └── memory/        # In-memory adapter (the default)
-├── tests/                 # Vitest test suite — public team owned
+├── tests/                 # Vitest test suite
 │   └── README.md          # How to write and run tests
 ├── examples/
 │   └── browser-standalone/   # Minimal demo app

PROJECT_CHARTER.md

@@ -0,0 +1,68 @@
+# Project Charter — MonkeyTab
+
+> First version. Expect this to evolve as the project and community grow. TODOs flag the parts that need a real answer before this charter is "done."
+
+## Vision
+
+Make tables easy to drop into any React app, so developers can give their users a real spreadsheet experience without spending weeks building one.
+
+## Mission
+
+MonkeyTab is an embeddable, editable React table component. Type-aware columns, spreadsheet-style keyboard navigation, copy-paste from Excel, sort/filter/search out of the box, virtualized for large datasets — installable from npm with one dependency and a peer dep on React.
+
+The project's job is to make the **80% case** of "I need a good table in my React app" a single component install, while staying small enough that the **20% case** can be solved by overriding renderers, editors, and behaviors via props.
+
+## Scope
+
+**In scope:**
+
+- The `@datasketch/monkeytab` npm package: a React component for editable tables
+- Built-in field types (Text, Number, Boolean, Date, SingleSelect, MultiSelect, Email, URL, Phone, Image, Attachment, Rating, Color, Computed)
+- Sort, filter, search, pagination, virtualization
+- An in-memory adapter for trivial use cases
+- Documentation site at <https://monkeytab.app>
+
+**Out of scope (for now):**
+
+- Hosted backend, multi-user collaboration, or sync — MonkeyTab renders, the host app owns the data
+- File-based persistence (CSV, JSON, SQLite) is on the roadmap but not in the initial release
+- Authentication, permissions, or organization features
+
+## License
+
+**MIT** — see [`LICENSE`](./LICENSE).
+
+The MIT license was chosen because:
+
+- It's permissive — anyone can use MonkeyTab in commercial products without copyleft obligations
+- It's familiar to React ecosystem contributors and is the de facto standard for React component libraries on npm
+- It minimizes legal friction for adoption, which is the primary success metric for a UI library
+- It's OSI-approved, GPL-compatible, and SPDX-recognized
+
+By contributing, you agree your contributions are licensed under the same terms.
+
+## Community and governance
+
+- **Issues and discussions**: <https://github.com/datasketch/monkeytab/issues>
+- **Pull requests**: see [`CONTRIBUTING.md`](./CONTRIBUTING.md)
+- **Code of conduct**: see [`CODE_OF_CONDUCT.md`](./CODE_OF_CONDUCT.md)
+
+**Maintainers**:
+
+- JP Marin Diaz — [@jpmarindiaz](https://x.com/jpmarindiaz)
+
+The project is in its early stages. All decisions about scope, design, breaking changes, and write access are currently made by JP Marin Diaz. As the contributor base and the project grow, this governance will be formalized into a multi-maintainer process with explicit criteria for new committers.
+
+## Trademarks
+
+"MonkeyTab" and the MonkeyTab logo are project marks. They may be used to refer to the project itself (in articles, presentations, integrations) without permission. Commercial use of the marks (selling derivative products under the MonkeyTab name) requires permission.
+
+> **TODO**: formal trademark policy if/when the project is donated to a foundation or when commercial derivatives become a real concern.
+
+## Charter changes
+
+This charter is intentionally short. Updates happen via PR to this file. Substantial changes (scope, license, governance) should be discussed in a GitHub issue first.
+
+---
+
+*Charter v0.1 · MIT licensed · last updated 2026-04-08*

TESTING.md

@@ -0,0 +1,98 @@
+# Testing
+
+> First version. Captures the testing approach today (Phase 1 of the project) and links out to the working configuration. Will be expanded as the test surface grows.
+
+## Strategy
+
+MonkeyTab tests focus on **behavior that ships to consumers**: the public API of `@datasketch/monkeytab`, the field type registries, the in-memory adapter, and the rendering of the React components.
+
+We test the source directly (via the `@monkeytab/*` aliases configured in `vitest.config.ts`) so that what's tested matches what's built. We do **not** mock — tests use real adapters, real registries, and real React renders via `@testing-library/react`.
+
+The minimum bar is **15% line coverage**, enforced by `vitest.config.ts` thresholds. CI fails if coverage falls below the threshold. The current target is to grow from this floor as new tests are added.
+
+> **TODO**: raise the coverage target as the test suite matures (suggested next step: 30% after a full pass on `src/core/`).
+
+## Test layout
+
+Tests live under [`tests/`](./tests/) and are picked up by Vitest's default glob `tests/**/*.test.{ts,tsx}`. There is no enforced sub-structure — flat files, `tests/unit/`, `tests/integration/`, and `tests/components/` are all fine. See [`tests/README.md`](./tests/README.md) for the conventions and example tests.
+
+## Sample test cases
+
+The test suite covers (or is targeted to cover) the following surface areas. This list is the working backlog for raising coverage past the 15% floor.
+
+| Area | What to test | Status |
+|---|---|---|
+| `<MonkeyTable>` render | Mounts via React Testing Library, headers from `columns` appear, mounts cleanly with empty rows / custom render / `editable: false` | ✅ in suite |
+| MemoryAdapter — schema | `listBases`, `getTable`, `info()` capabilities | ✅ in suite |
+| MemoryAdapter — CRUD | Create → query → get → update → delete round-trip | ✅ in suite |
+| MemoryAdapter — pagination | `queryRecords` with `offset` + `limit` slices correctly | ✅ in suite |
+| MemoryAdapter — schema mutation | `createField` / `deleteField` round-trip | ✅ in suite |
+| MemoryAdapter — error paths | `getRecord` throws on missing record | ✅ in suite |
+| Bundle import smoke | `dist/monkeytab.js` exports the documented public API | ✅ in suite |
+| SSR safety | Bundle imports cleanly in a no-DOM Node environment | ✅ in suite |
+| Public type contract | `dist/index.d.ts` compiles a consumer-style file via `tsc --noEmit` | ✅ in suite |
+| `compareValues` (sort) | numeric ordering, string ordering, null handling, mixed types | ⚠️ TODO |
+| `applySort` | single-column ascending/descending, multi-column tiebreakers | ⚠️ TODO |
+| `applyFilter` | each FilterOperator (eq, neq, lt/lte/gt/gte, contains, is_empty, etc.) per supported field type | ⚠️ TODO |
+| Field type registry | direct `lookup()` and override registration assertions | ⚠️ TODO |
+| `<MonkeyTable>` editing | `onChange` fires with new rows on cell edit | ⚠️ TODO |
+| Type-aware sort labels | correct label per field type | ⚠️ TODO |
+| Per-column control | `editable: false`, `sortable: false`, custom `width` exercised end-to-end | ⚠️ TODO |
+
+> **TODO**: each ⚠️ row is a good first issue for new contributors.
+
+## Data structures under test
+
+The core data shapes are defined in `src/core/types.ts` and re-exported through `src/browser/types.d.ts`. Tests import them through the `@monkeytab/core` alias rather than reaching into source paths directly.
+
+Key shapes:
+
+- **`FieldSpec`** — `{ id, label, type, options? }` — describes a column
+- **`Row`** — `{ id, fields: Record<string, Value>, createdAt, updatedAt }` — a single record
+- **`TableSpec`** — `{ id, label, fields, primaryFieldId?, columnOrder?, rowOrder? }` — schema
+- **`FilterCondition`** / **`FilterGroup`** — query filters
+- **`SortSpec`** — sort directives
+- **`FieldOptions`** — discriminated union of per-type options (NumberFieldOptions, SingleSelectFieldOptions, etc.)
+
+See [`src/browser/types.d.ts`](./src/browser/types.d.ts) for the full surface.
+
+## Pull request workflow
+
+Every PR must:
+
+1. Pass `npm run build:check` (TypeScript strict-mode check on the source)
+2. Pass `npm test` (the full Vitest suite)
+3. Pass `npm run test:coverage` (which enforces the 15% thresholds)
+4. Pass `npm run build` (Vite library build, produces `dist/monkeytab.js`)
+
+CI runs all four steps automatically on push and on PR. The CI status badge is in [`README.md`](./README.md). The coverage report is uploaded as a CI artifact (`coverage-report`) and can be downloaded from the Actions run page.
+
+For the full PR submission flow, see [`CONTRIBUTING.md`](./CONTRIBUTING.md). The pull request template at [`.github/PULL_REQUEST_TEMPLATE.md`](./.github/PULL_REQUEST_TEMPLATE.md) is auto-applied to every new PR.
+
+## Running tests locally
+
+```bash
+npm install              # one-time setup
+npm test                 # run the suite once
+npm run test:watch       # interactive watch mode
+npm run test:coverage    # run with coverage report (enforces 15% thresholds)
+npm run build:check      # TypeScript type-check the source
+npm run build            # Vite library build
+```
+
+The HTML coverage report is generated at `coverage/index.html` after `test:coverage`. Open it in a browser to see line-by-line coverage.
+
+## Reporting test failures
+
+If a test fails on `main`, file a GitHub issue with:
+
+- The failing test name and file
+- The expected vs actual output
+- A minimal reproduction (what command you ran, what environment)
+- Whether the failure is reproducible or intermittent
+
+If a contributor's test catches a real bug, the failing test should be merged with the fix (so it becomes a regression check for the future).
+
+---
+
+*Testing v0.1 · last updated 2026-04-08*

tests/README.md

@@ -1,24 +1,12 @@
 # Tests
 
-This directory holds the public team's test suite for `@datasketch/monkeytab`.
+The Vitest test suite for `@datasketch/monkeytab`. Tests run in Node with jsdom and V8 coverage; the configuration lives in `vitest.config.ts` at the repo root.
 
-## Important: this directory is YOURS
+## Layout
 
-The upstream sync script (in the private workspace) **never touches
-`tests/`**. Whatever you put here is preserved across every sync. You
-can:
+You can structure tests however you like — `tests/unit/`, `tests/integration/`, flat files, fixtures, helpers, mocks. The runner picks up anything matching `tests/**/*.test.{ts,tsx}`.
 
-- Write tests in any structure (`tests/unit/`, `tests/integration/`,
-  flat files, whatever works)
-- Use any test framework — the default `vitest.config.ts` is set up
-  for Vitest with jsdom + V8 coverage
-- Mix `*.test.ts` and `*.test.tsx` for component tests
-- Add fixtures, helpers, mocks — anything not committed by upstream
-
-The upstream maintainers run their own (Deno-based) tests against the
-private build. Your tests run in parallel against the same source code
-but in Node — different runtime, different test author, different blind
-spots. That's the point: parallel suites catch different things.
+`@testing-library/react` and `@testing-library/jest-dom` are preinstalled for component tests.
 
 ## Running tests
 
@@ -29,14 +17,11 @@ npm run test:watch       # watch mode
 npm run test:coverage    # with V8 coverage report
 ```
 
-Coverage output goes to `./coverage/` (gitignored). The HTML report
-at `./coverage/index.html` is the friendliest format. The `lcov.info`
-file is what coverage services consume.
+Coverage output goes to `./coverage/` (gitignored). The HTML report at `./coverage/index.html` is the friendliest format. The `lcov.info` file is what coverage services consume.
 
 ## Writing tests
 
-Tests can import directly from the source via the `@monkeytab/*`
-aliases configured in `vitest.config.ts`:
+Tests can import directly from the source via the `@monkeytab/*` aliases configured in `vitest.config.ts`:
 
 ```ts
 // tests/core/query-utils.test.ts
@@ -79,37 +64,20 @@ describe('<MonkeyTable>', () => {
 });
 ```
 
-You'll need to install `@testing-library/react` and `@testing-library/jest-dom`
-yourself if you want component tests — they're not in the default
-`devDependencies` to keep the install lean.
+`@testing-library/react` and `@testing-library/jest-dom` are included in the default devDependencies, so you can write component tests immediately without installing anything else.
 
 ## Coverage target
 
-The MonkeyTab project targets **15% line coverage** as a minimum bar.
-Aim higher when you can — exercising the core utilities (query, sort,
-filter, registries, MemoryAdapter) is usually enough to get to 25–30%
-without touching the React layer.
+The MonkeyTab project targets **15% line coverage** as a minimum bar. Aim higher when you can — exercising the core utilities (query, sort, filter, registries, MemoryAdapter) is usually enough to get to 25–30% without touching the React layer.
 
 ## What gets covered
 
-`vitest.config.ts` includes `src/**/*.{ts,tsx}` and excludes test
-files and type-only `.d.ts` files. Anything in `src/` is fair game,
-which means your tests can drive the actual implementation that ships
-to npm consumers.
+`vitest.config.ts` includes `src/**/*.{ts,tsx}` and excludes test files and type-only `.d.ts` files. Anything in `src/` is fair game.
 
 ## CI integration
 
-If you set up CI (`.github/workflows/ci.yml`), the test job should
-run `npm run test:coverage` and either fail on the 15% threshold or
-upload the `lcov.info` to a coverage service like Codecov.
-
-## A note on parallel suites
+`.github/workflows/ci.yml` runs `npm run test:coverage` and fails the build if any of the 15% thresholds (lines, branches, functions, statements) are not met. Coverage artifacts are uploaded by the workflow.
 
-The maintainers run their own internal test suite against the full
-feature set in a different runtime. This public test suite is
-**independent** — it tests only what ships in `@datasketch/monkeytab`,
-written by a different team.
+## Reporting bugs found by tests
 
-If your tests catch a bug, file it in the public repo. The maintainers
-will reproduce it on their side, fix it, and re-sync. Your test remains
-as a regression check on the public side.
+If a test catches a bug, file it as a GitHub issue with the failing test, expected behavior, and a minimal reproduction. Keep the failing test in your branch — it becomes the regression check once the bug is fixed.

vitest.config.ts

@@ -4,15 +4,11 @@ import { fileURLToPath } from 'node:url';
 
 const __dirname = fileURLToPath(new URL('.', import.meta.url));
 
-// Test runner config for the public team's parallel test suite.
+// Vitest config for the @datasketch/monkeytab test suite.
 //
-// The public test suite lives in ./tests/ and is owned entirely by the
-// datasketch team. The sync script never touches it — every team member
-// can write their own tests, contributors can add tests via PRs, and
-// nothing the upstream sync owner does will overwrite them.
-//
-// Tests can import from the synced source via @monkeytab/* aliases,
-// matching the workspace package names used in the source code.
+// Tests live in ./tests/ — see tests/README.md for conventions.
+// The @monkeytab/* aliases below match the package names used in
+// the source so tests can import without relative paths.
 export default defineConfig({
   test: {
     globals: true,