soportepreguntas
SOPORTEP-1
Google OAuth client + seed Puia client row
Done high
cecoder-enamel-cc
Service is deployed and live at https://preguntas-pen.pensanta.com (unit soportepreguntas.service, /opt/soportepreguntas, schema applied, 16/16 tests, agent API and answer-DM both smoke-tested end to end). Two inputs only Elazar can supply: (1) a Google Cloud OAuth web-application client id+secret whose authorized redirect URI is exactly https://preguntas-pen.pensanta.com/auth/callback - GOOGLE_CLIENT_ID/SECRET are placeholders, so client sign-in is the one path that cannot work yet; (2) Puia's Google email, to insert into soportepreguntas.clients against project key 'puia' (project row already seeded).
Activity
-
Waiting on Elazar: Google OAuth client credentials + Puia's email
-
cleared: Waiting on Elazar: Google OAuth client credentials + Puia's email
-
Both blocking inputs landed. (1) Google OAuth web client installed in /opt/soportepreguntas/.env 2026-09-11 (client id 266911981121-1u0qavt8..., redirect https://preguntas-pen.pensanta.com/auth/callback); sign-in start verified 302 to accounts.google.com with the exact redirect_uri. (2) Puia allowlist row seeded 2026-09-11 10:58Z: sebastian.puia@odontologia.uba.ar, projectKey puia, name Puia. Address is Elazar verbatim on EVO-83 2026-07-31 ('2 yes central. sebastian.puia@odontologia.uba.ar 3 Client ok. 4 grant it'), read from the WI event, not relayed recall; relayed to me by pmmaster-evolutiva-cc and verified against the source before writing. Name stored as 'Puia' deliberately: EVO-83 bars copying the venus nombre/apellido strings, whose provenance is indistinguishable from title-casing the local-part. Consent-screen publishing is a console action only Elazar can take and is tracked separately.
feature
6w ago by wi-cli-venus
5w ago
2026-09-11 10:58