# Open-Source Checklist

Use this before copying the package into a public GitHub repository.

## Repository Content

- [ ] README explains the problem, workflow, safety model, demo, and evaluation.
- [ ] Homepage content is ready in `docs/index.md`.
- [ ] Case study is public-safe and does not mention private local paths.
- [ ] Demo data is synthetic or public-safe.
- [ ] Match and eval reports are generated from sample data only.
- [ ] No private candidate profile, resume, or tracker is included.
- [ ] No account sessions, cookies, tokens, or browser profiles are included.
- [ ] No gated-platform content is included.

## GitHub Setup

- [ ] Repository name: `ai-job-radar`.
- [ ] About description copied from `GITHUB_REPO_PROFILE.md`.
- [ ] Topics copied from `GITHUB_REPO_PROFILE.md`.
- [ ] GitHub Pages enabled only if `docs/index.md` or a static site is used.
- [ ] Issues are enabled only if public feedback is desired.
- [ ] Security policy or privacy note is linked from README.

## License Choice

Recommended default for a portfolio documentation package:

- `MIT` if publishing lightweight examples and docs.
- `Apache-2.0` if publishing reusable implementation code later and patent language matters.
- `No license yet` if the repository is portfolio-visible but not intended for reuse.

Do not add a license until the intended reuse boundary is clear.

## Pre-Publish Redaction Commands

Run equivalent searches before publishing:

```text
rg -n "token|cookie|session|password|bearer|authorization|secret" .
rg -n "[A-Z]:\\\\|Users/|AppData|Chrome profile|vault|resume|phone|email" .
rg -n "linkedin.com/in|boss|tracking|utm_|recruiter|interview" .
```

Review matches manually. Some words may be allowed in security guidance, but no actual secret, private path, account name, or real application data should remain.

## Publish Sequence

1. Create a clean public repository.
2. Copy only files from this package.
3. Add a license only after choosing reuse policy.
4. Run redaction searches.
5. Render README and docs in GitHub preview.
6. Add repository About fields.
7. Pin the repository only after the README, docs, and demo files render correctly.