chore(sponsors): remove PackyCode sponsorship

[lidge-jun]

HOLD: waiting for Jun's approval

Summary

PackyCode has stopped sponsoring the project, so this removes everything that presented it as a sponsor. The packycode provider preset stays as an ordinary key preset with the same id, adapter, base URL (https://cf.api.fan/v1), models and live discovery, so existing packycode rows in users' configs keep working unchanged.

Removed:

• The PackyCode row (logo plus aff=k5KT affiliate links) from the sponsor table in README.md and all seven translated READMEs. readme/i18n-manifest.json is resynced to the new English hash.
• assets/sponsors/packycode.png with its package.json files entry, and the four unreferenced PackyCode marketing screenshots in assets/sponsors/.
• The registry sponsor field. Without it, PackyCode is no longer pinned in the Add provider picker, loses the Sponsor badge, and is no longer pinned in ocx init or ocx provider presets. dashboardUrl is now the plain https://www.packyapi.com.
• The PackyCode provider overview sponsor card (ProviderSponsor brand row) and the pws.sponsor.packyTitle / packyDescription copy in all eleven locales.
• The "sponsor" wording and affiliate link in docs-site/.../guides/providers.md, plus PackyCode in the sponsor brand list in structure/dashboard-and-usage.md.

Kept on purpose: the generic provider icon (gui/public/provider-icons/packycode.svg, its GUI/desktop mappings) and the tests that use packycode / packyapi.com only as a provider or hostname fixture. devlog/ history is untouched.

Screenshots

Same config (one packycode provider), dev vs this branch.

	Before (dev)	After
Provider overview
Add provider → Paid

Verification

• bun run typecheck passed.
• bun test tests/providers/sponsor-presets.test.ts tests/providers/provider-registry-parity.test.ts tests/ci-workflows/docs-readme-translation-parity.test.ts tests/ci-workflows/repo-hygiene.test.ts tests/gui/provider-workspace-data.test.ts tests/routing/destination-policy-resolved.test.ts tests/ci-workflows/skill-ocx.test.ts passed.
• cd gui && bun test tests/provider-sponsor-overview.test.tsx tests/provider-catalog-sponsor-pinning.test.ts tests/i18n-locales.test.ts passed. The Packy-specific sponsor test now covers the same "identical console link is not repeated" behavior with a TokenLab fixture, and the pinning test uses a synthetic sponsor id.
• bun run privacy:scan and bun run structure:check passed.
• I did not run the full bun run test locally because this is a narrow content and registry change. The remaining coverage is left to the PR's Ubuntu CI.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Summary by CodeRabbit

• Changes
  • PackyCode is no longer listed or labeled as a sponsor in the app, documentation, or README translations.
  • The PackyCode registration link now points to its homepage instead of a referral link.
  • PackyCode remains available as a provider; its setup and registration information now appears without sponsor messaging.

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T17:01:47.667349Z	f5ec00f	PR opened

ℹ️ 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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 4a865afd-4bc0-4e9f-950d-cada47304dc4

📥 Commits

Reviewing files that changed from the base of the PR and between 16d36fb and f5ec00f.

⛔ Files ignored due to path filters (5)

• assets/sponsors/packycode-overview-mobile.png is excluded by !**/*.png
• assets/sponsors/packycode-overview.png is excluded by !**/*.png
• assets/sponsors/packycode-picker.png is excluded by !**/*.png
• assets/sponsors/packycode-readme.png is excluded by !**/*.png
• assets/sponsors/packycode.png is excluded by !**/*.png

📒 Files selected for processing (27)

• README.md
• docs-site/src/content/docs/guides/providers.md
• gui/src/components/provider-workspace/ProviderSponsor.tsx
• gui/src/i18n/de.ts
• gui/src/i18n/en.ts
• gui/src/i18n/fr.ts
• gui/src/i18n/ja.ts
• gui/src/i18n/ko.ts
• gui/src/i18n/pt.ts
• gui/src/i18n/ru.ts
• gui/src/i18n/tr.ts
• gui/src/i18n/vi.ts
• gui/src/i18n/zh-TW.ts
• gui/src/i18n/zh.ts
• gui/tests/provider-catalog-sponsor-pinning.test.ts
• gui/tests/provider-sponsor-overview.test.tsx
• package.json
• readme/README.fr.md
• readme/README.ja.md
• readme/README.ko.md
• readme/README.ru.md
• readme/README.tr.md
• readme/README.zh-CN.md
• readme/README.zh-TW.md
• readme/i18n-manifest.json
• src/providers/registry/entries-core.ts
• structure/dashboard-and-usage.md

💤 Files with no reviewable changes (21)

• readme/README.tr.md
• package.json
• readme/README.ja.md
• readme/README.ko.md
• readme/README.zh-CN.md
• gui/src/i18n/ru.ts
• gui/src/i18n/vi.ts
• readme/README.ru.md
• gui/src/i18n/fr.ts
• gui/src/i18n/tr.ts
• gui/src/i18n/de.ts
• gui/src/i18n/pt.ts
• gui/src/components/provider-workspace/ProviderSponsor.tsx
• gui/src/i18n/ja.ts
• gui/src/i18n/en.ts
• gui/src/i18n/zh-TW.ts
• gui/src/i18n/zh.ts
• README.md
• gui/src/i18n/ko.ts
• readme/README.zh-TW.md
• readme/README.fr.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

📝 Walkthrough

The PackyCode sponsor association and related sponsor copy were removed from provider data, the GUI, and sponsor listings. The provider guide now links to the PackyCode homepage. Package metadata and tests were updated.

Changes: PackyCode sponsor removal

Layer / File(s)	Summary
Remove provider sponsor association src/providers/registry/entries-core.ts, gui/src/components/provider-workspace/ProviderSponsor.tsx, gui/src/i18n/*.ts, gui/tests/provider-catalog-sponsor-pinning.test.ts, gui/tests/provider-sponsor-overview.test.tsx	The PackyCode registry entry no longer includes sponsor metadata or an affiliate dashboard URL. The GUI sponsor brand and localized sponsor strings were removed. Tests now use Lumen for sponsor pinning and TokenLab for the duplicate-link case.
Update sponsor references README.md, readme/README.*.md, docs-site/src/content/docs/guides/providers.md, structure/dashboard-and-usage.md, package.json, readme/i18n-manifest.json	PackyCode sponsor rows and sponsor documentation references were removed. The provider guide links to the PackyCode homepage. Package metadata no longer lists the PackyCode sponsor image, and locale source hashes were updated.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to f5ec0

This is a sponsor-removal cleanup. Existing PackyCode provider configurations keep working, and no merge-blocking risk was identified.

Pre-merge checks · 5

Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title accurately and concisely describes the primary change: removing PackyCode sponsorship presentation while retaining the provider preset.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 3…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[lidge-jun]

Maintainer integration into dev (MAINTAINERS.md dev-only exception), on behalf of @lidge-jun as part of the 2026-10-13 release train. Exact-head verification: all required PR checks passed on f5ec00f0934e934a729e2d83aaf1d2577a2ef6c4; macOS/Windows legs skipped per CI policy and will be covered by the post-merge manual cross-platform dispatch on dev.