Skip to content

fix(ai): complete Diffex provider branding - #288

Merged
Pepps233 merged 6 commits into
mainfrom
fix/diffex-provider-branding
Oct 27, 2026
Merged

Pepps233 merged 6 commits into
mainfrom
fix/diffex-provider-branding

Conversation

@Pepps233

Copy link
Copy Markdown
Contributor

Summary

Use consistent Diffex branding on OAuth callback pages and default provider request attribution.

Reasoning

Users should see accurate application identity and sign-in status throughout the Diffex migration.
Provider-specific protocols and explicit header overrides remain respected.

Changes

  • Update callback artwork, terminal-return instructions, and safe error presentation.
  • Apply Diffex request attribution while preserving optional-attribution settings.
  • Cover callback behavior, browser transport, configured headers, and SDK dispatch.
  • Record offline validation.

Testing

  • npm run check and ./test.sh passed on the complete local revision.
  • Focused callback, OAuth, transport, attribution, and SDK tests passed with controlled fixtures.
  • Live provider compatibility was not established.

- Direct users back to the terminal for final sign-in status
- Keep callback validation and timing while hiding provider error details
- Identify default provider traffic as Diffex without changing authentication or inference protocols
- Preserve configured headers, optional attribution controls, and session behavior
- Record offline evidence and the intentional identity exceptions
- Keep live provider compatibility checks explicit before release
- Use the official Diffex mark and entrance boat for consistent branding
- Keep browser return instructions concise
Comment thread packages/ai/test/oauth-page.test.ts Fixed
@Pepps233
Pepps233 added this pull request to stack #293 October 27, 2026 13:31
- Match only the exact inline SVG namespace so unrelated hosts cannot pass callback resource checks
- Create private temporary directories atomically for SDK tests
@Pepps233

Copy link
Copy Markdown
Contributor Author

Addressed the callback resource assertion by exempting only the exact SVG namespace.
Lookalike hostnames can no longer pass the assertion.
SDK attribution fixtures now use atomically created private temporary directories.

Validation: callback and attribution tests, npm run check, and the isolated non-live suite pass.

This comment is AI-generated.

@Pepps233
Pepps233 merged commit 041cca8 into main Oct 27, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants