[jallers]

This repository is public and published to npmjs, but its tree named private repositories, Claude sessions, internal branches and pull requests, people, a real account, and hosted instances. This PR scrubs the tree, adds a mechanical check so nothing new is added, and sets out where that material lives instead.

Audit (confirmed and extended)

• plans/001–005 and plans/handoffs/* (nine files): private repositories (three consumer projects and the product's source), session ids, internal branch names and PR numbers, people, the API-testing instance URL. The CLI consumer's repository was checked and is private, so it is treated like the others.
• Source comments (src/types/oid.ts, src/services/{attachments,guard,batch,schema,resolve}.ts, src/wire/{assetApi,fields,rest1}.ts, src/types/asset.ts), test names and comments (test/unit/*, test/integration/*), CHANGELOG.md and README.md: consumer names, the product's source by name and file path, "verified live on ", the instance URL as the example base URL.
• test/unit/client.test.ts and test/unit/rest1.test.ts: a real account's username, display name and member OID, and a maintainer's name, copied from live responses.
• metamodel.json: the instance's path in 19,196 href/HREF values.
• test/integration/instance.ts and spec 000 §5: the hosted testing instance in a committed allowlist.
• test/integration/customFields.ts: product source file paths and a path on a personal machine.
• src/core/clientConfig.ts and the README example: a production instance's URL as the documented example base URL.
• Git history: 87 of the 89 commit messages on the branch name a private repository or a session.

What this PR does (six commits, in order)

1. Scrub comments, tests and changelog. Consumers are "a CLI consumer", "a chat-bot consumer", "a browser app consumer"; the product's source is "the server"; the instance is "the API-testing instance". Fixtures keep the server's shape with fictitious identities.
2. Metamodel. scripts/download-metamodel.mjs spells every href from /meta.v1/ (raw pulls untouched); the committed file is rewritten the same way; a test checks the rewrite and the committed file. Nothing in the SDK reads an href; the generated types are byte-for-byte unchanged.
3. Integration allowlist from the environment. The hosted instances the tier may write to come from SDK_TEST_ALLOWED_INSTANCES (comma-separated base URLs) instead of a committed list. Same rule: local always, hosted only when allowed, V1Production never; it lives in test/integration/instanceGuard.ts with a unit test, and a refused URL says what to set. Live tier with the variable set: 40 passed, 3 skipped. Wherever the tier runs against a hosted instance, the cloud environment included, the variable is set beside the credential.
4. The approach. CONTRIBUTING.md, a README pointer, and spec 000 §8. test/unit/publicTree.test.ts enforces it by shape, without listing any name: no session id, no repository slug under the product's organisations other than this one, no hosted instance URL. plans/ is skipped by the test until it leaves the tree.
5. The alpha.6 changelog note from CI: actions on the Node 24 runtime; Node 22 or later #55 (merged after this branch was cut) named the three consumers; it is reworded by kind.
6. No hosted instance URL at all. The example base URL (README, client config doc, metamodel script usage, unit-test fixtures) was the product documentation's production example; it is now a fictitious domain, and the public-tree test refuses any hosted instance URL, with no exception.

plans/ stays in this PR, by decision: it leaves the tree once the private planning repository exists, in a PR of its own. The branch is rebased on the current base (after #55). npm run verify is green at every commit: 26 files, 173 unit tests.

The approach

• Plans live in a private planning repository in the versionone organisation; proposed name agility-sdk-planning, to be created by a maintainer. One file per plan, as today. A plan may cite this repository by commit, tag or PR number; this repository never cites a plan.
• Hand-offs live with the consumer: a file in the consumer's own repository, or a message to the session working on it. Sessions hand work to each other by message, not by a committed file; the durable copy, if wanted, goes in the planning repository under handoffs/.
• Findings come back here as issues, PRs, tests and changelog lines worded for the public; their origin stays in the planning repository.
• Here: specs/ (invariants of this code, nothing private), CHANGELOG.md and README.md (they ship in the package), and docs/ for longer consumer-facing material when there is some. No docs/ directory is created in this PR because there is nothing to put in it yet.

History

The 87 commit messages that name private repositories and sessions are left as they are. The branch is public, the npm releases are tagged on it, and a consumer vendors builds by commit SHA, so history is not rewritten. The goal is to stop adding such names and to clear the tree; the test does the first and this PR the second.

Decisions taken

• The allowlist stays in the environment.
• The plans stay until the planning repository exists; the removal commit was dropped from this branch.

🤖 Generated with Claude Code

https://claude.ai/code/session_016NSWj6JhfcwPfucX8mr1jH