Skip to content

feat: add sub2api provider (upstream 0.43.0)#202

Merged
Finesssee merged 1 commit into
mainfrom
feat/sub2api-provider
Jul 17, 2026
Merged

feat: add sub2api provider (upstream 0.43.0)#202
Finesssee merged 1 commit into
mainfrom
feat/sub2api-provider

Conversation

@Finesssee

Copy link
Copy Markdown
Collaborator

Summary

Port sub2api from upstream CodexBar v0.43.0 into Win-CodexBar (PR A of the 0.43.0 port stack).

  • New provider: GET {base}/v1/usage with Bearer group/fallback API key
  • Env: SUB2API_API_KEY, SUB2API_BASE_URL (HTTPS or loopback HTTP)
  • Maps keyQuota / subscription (daily/weekly/monthly) / wallet + rate_limits
  • Token accounts for group API keys; settings workspace base URL
  • Icons + frontend catalog wiring
  • Unit tests (10) for parse, URL join, base URL validation

Version

Still 0.42.0 marketing version (packaging PR F comes last).

Validation

  • cargo test --manifest-path rust/Cargo.toml sub2api — 10 passed
  • test_provider_id_all / every_provider_id_is_instantiable — ok (per implementer)

Plan

Part of Windows 0.43.0 port. Next: account-scoped notifications, Factory API-key Auto, cost/stale refresh, P1 residuals, then version bump.

@Finesssee
Finesssee merged commit dc3906b into main Jul 17, 2026
1 check failed
@Finesssee
Finesssee deleted the feat/sub2api-provider branch July 17, 2026 04:49
Finesssee added a commit that referenced this pull request Jul 17, 2026
Close P0/P1 findings from reviews of PRs #202-#207: refresh generation lock ownership, Factory cookie-off/dotenv/usage, sub2api Kind mapping, notification identity, informational tray metrics, and watermark containment.

Co-authored-by: NessZerra <Finesssee@users.noreply.github.com>
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