Skip to content

test: replace real client identifiers with generic placeholders - #632

Merged
roodboi merged 3 commits into
nextfrom
claude/scrub-client-identifiers-next
Nov 7, 2026
Merged

roodboi merged 3 commits into
nextfrom
claude/scrub-client-identifiers-next

Conversation

@roodboi

@roodboi roodboi commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Replaces real client and private project names, private development-host references, one personal home path and private tracker links in the current tree with neutral placeholders (example-app, sample, example_qa, large-application, hosts under example.test, /Users/example).

Files changed by kind:

  • Unit test fixtures and assertions (tests/*.test.ts, one e2e scenario, one test helper comment): project, branch, compose, session and profile names.
  • Rust test fixtures, test names, #[ignore] reasons and evidence strings in packages/runtime-core. Only test code changed. Ports, hostname shapes and assertions are the same.
  • Benchmark protocol labels (scripts/application-benchmark-protocol.json, its checker and the Python test): the workload id is renamed. Its shape, pin and correctness checks are unchanged.
  • Docs and READMEs: prose naming the trial application or a specific development host now uses generic wording. Private tracker links are now plain issue ids. One edited docs snapshot gets an updated hash in scripts/docs/versions.json.
  • A doc comment example in src/lib/project.ts (comment only).
  • Two committed example override files under examples/*/.hack/.internal/: a home path in a mount source.
  • Two CHANGELOG.md lines.

No production code special-cased these names. History is unchanged: no rewrite and no force-push.

Validation

  • bun test on every touched TS test file: 232 pass, 0 fail.
  • bun run --cwd packages/cli typecheck and check: pass. bun run privacy:check: ok. bun run docs:prepare && bun run docs:check: pass.
  • Rust (cargo +1.97.1): fmt --check, clippy --all-targets -D warnings and cargo test --locked: 1313 passed, 0 failed, 109 ignored.
  • python3 scripts/check-application-benchmark-protocol.py: valid. python3 -m unittest on the protocol test: 45 OK.
  • gitleaks over the new commit: no leaks.

Update: merged with next

next was merged in (merge commit takes the next side for the one textual conflict, a Rust test that next had already moved and renamed to the same placeholder name). The placeholder pass was then rerun over the whole merged tree with the full identifier checklist from this PR's diff. It found no remaining occurrences, so no extra scrub commit was needed: the batches merged since this PR was opened added none, and every replacement line from the original commit survives the merge.

Validation on the merged head:

  • bun test on the 17 touched TS test files: 234 pass, 0 fail.
  • bun run --cwd packages/cli typecheck (clean worktree) and check: pass. Biome on changed files: clean. bun run privacy:check: ok. bun run docs:prepare && bun run docs:check: pass.
  • Rust (1.97.1): fmt --check and check:local (clippy --all-targets -D warnings): pass. Affected lib tests and project_contract: 144 lib tests and 66 contract tests passed, 0 failed.
  • python3 -I scripts/check-application-benchmark-protocol.py: valid. Protocol unittest: 45 OK.
  • gitleaks over the new commits and the tree: no leaks.

🤖 Generated with Claude Code


Run Proof
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Replace real client and private project names, private host references,
a personal home path and private tracker links in fixtures, test names,
docs, comments and benchmark protocol labels with neutral placeholders.
Test intent and expectations are unchanged. The edited docs snapshot
hash in the docs manifest is updated to match.

History is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@roodboi

roodboi commented Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-07T10:12:51.388412Z 6471c66 Manual request
🔒 Security Review ✅ Completed 2026-11-07T10:13:56.518131Z 6471c66 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

The example projects tracked Hack-generated compose overrides under
`.hack/.internal/`, which hold machine-local paths and must not be
hand-edited. Remove them from version control and ignore generated
`.hack/.internal/` and `.hack/.branch/` state at any depth.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a87f016824

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@roodboi

roodboi commented Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 3a2ac43782

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 3a2ac43782

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

Conflicted files take the next side; the placeholder pass is redone
in the following commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@roodboi

roodboi commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: 6471c667b3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 6471c667b3

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@roodboi
roodboi merged commit e19e0b1 into next Nov 7, 2026
27 checks passed
@roodboi
roodboi deleted the claude/scrub-client-identifiers-next branch November 7, 2026 11:08
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