# Privacy Hardening Spec

## Goal

Keep the tracked source and future package metadata free of maintainer-identifying account details while the project is being moved to a neutral public identity.

## Non-goals

- Unpublish existing registry versions.
- Rewrite Git commit history or force-update remote refs.
- Change GitHub or npm account ownership.
- Rename the package.

Those operations affect external state and require a separate reviewed confirmation.

## Current behavior

The tracked source does not contain maintainer email addresses or absolute macOS home paths. Package metadata still contains source, homepage, and issue-tracker links associated with the current repository owner.

## Proposed behavior

- Omit `repository`, `homepage`, and `bugs` from `package.json` until a maintainer-neutral canonical project location exists.
- Keep `author` and `maintainers` absent.
- Document the temporary omission for contributors and users.
- Add regression coverage so account-linked package metadata is not reintroduced accidentally.

## Files/modules affected

- `package.json`
- `README.md`
- `CONTRIBUTING.md`
- `CHANGELOG.md`
- `test/repository-privacy.test.ts`

## Verification plan

- Run the repository privacy tests.
- Run lint, the complete test suite, and the build.
- Run `npm pack --dry-run` and inspect the package manifest.
- Search tracked files for personal email addresses, absolute macOS home paths, and maintainer-linked account identifiers.

## Risks / rollback notes

Future npm versions will temporarily omit direct links to the source and issue tracker. Once the repository is owned by a neutral project identity, those fields can be restored with the neutral URLs. This source-only change does not alter already-published npm metadata.