@zen-agent@zen-agent1mo ago
Post-PR status update (Zen)
Codex review
- Iteration 1: LGTM — "The changes consistently propagate the new managed-auth flag to footer attribution rendering and avoid showing the badge in the loading skeleton."
- Iteration 2 (after the defensive-cast push): LGTM — "The changes consistently propagate the managed-auth flag to all LinkCardFooter usages in the link flow and preserve existing attribution behavior when the flag is absent."
CI
10/10 green on initial push, and all checks have started/completed cleanly on ca5a0f3b (defensive cast push):
typecheck,lint,test (1-4 of 4)shards,merge-reports- CodeQL: javascript-typescript, actions, python
- Vercel preview: now DEPLOYED at
platform-frontend-git-zen-whitelabel-hide-composio-attri-a5f64e.preview.composio.dev. (Initial deploy failed because the staging OpenAPI didn't yet haveis_composio_managed; the defensive-cast commit fixed the typecheck.)
Tests / E2E
- Build checks:
pnpm lint✅ (0 errors, 322 pre-existing warnings);pnpm build --force✅ in 67s. Re-validated against the staging OpenAPI spec (which currently does NOT containis_composio_managed) — build still succeeds with the defensive cast. - Visual E2E via agent-browser (re-run after every commit, against local Apollo serving the new field):
- Custom Firecrawl auth (BYOC) → FormInputScreen and StateScreen: badge hidden ✓
- Composio-managed Gmail → StateScreen: badge visible ✓
- DOM snapshot of custom flow confirms
[data-testid="composio-attribution"]is absent.
- Demo video: https://pub-b70cb36a6853407fa468c5d6dec16633.r2.dev/260902/generic/file_upload/request/8d868b155ec926f4e8e7700ee8bfd158
Comments addressed
- No human or codex review comments left on this PR. The Vercel preview-build failure was self-discovered via the Vercel comment status — addressed in by intersecting an extension type so the build remains valid against either spec (current staging or post-hermes-deploy).
