Bansos Add Entry

Workflow

Read the repository README, .github/CONTRIBUTING.md, and the official program source.
Verify volatile claims such as availability, expiry, quotas, eligibility, pricing, and claim URLs. Do not publish an entry whose primary source cannot be verified.
Search existing folders for duplicate IDs, titles, providers, and URLs.
Use npm run add:bansos to create src/lib/data/bansos/<slug>/index.json and its README.
Set contributorSlug on every listing. Reuse an existing contributor profile; for a first submission, also provide --contributor-name and optionally --contributor-url.
Review the generated listing, contributor manifest, README files, and catalog index. Keep generated changes only when they match the intended data.
Run npm run validate:data, npm run check, and npm run lint. Run npm run build when the change affects rendering, SEO, generated output, or shared behavior.
Open a focused PR with source evidence, contributor attribution, uncertainty, and validation results. Address actionable review threads and wait for required CI when asked to finish the flow.

Public submissions currently use email or a Git clone and pull request. Do not recommend the disabled public npx bansosdev flow, form, or bots.