@claude — Vet the Phase-2 services (chat-service #127, Unleash #125) so they're deploy-ready. Per the hard lesson from #129 (a service merged "gate-green" but its Docker tsc never built), do NOT trust the merge — confirm the actual images build + list exactly what's needed to enable each. Land any build fixes via PR.
chat-service (#127 / AI Chat)
Unleash (#125 / feature flags)
- Confirm the Unleash Helm chart renders + the
unleashorg/unleash-server image tag is pinned (external image; not a build-matrix entry). Confirm the unleash-db-bootstrap Job + unleash-secrets SealedSecret scaffolding exist.
- Confirm
@fuzefront/feature-flags (OpenFeature + Unleash provider) builds + publish-config.
- List enable-readiness: required secret keys (Unleash
INIT_ADMIN_API_TOKENS admin token, a client/frontend API token, the unleash DB password), the unleash.enabled gate, Argo wiring, and the client's connection endpoint/token.
Deliverable
A report (comment) per service: BUILD = pass/fail (+ fixes PR'd), and a precise ENABLE CHECKLIST (exact secret keys to seal + the enabled flag + tag to set). Do NOT enable in prod (needs real secrets from the operator) — just make them green + ready.
STATE
done = #127/#125 merged to master; remaining = verify real Docker builds (not gate-green), fix build gaps, produce the enable checklist + required secrets. decisions = verify image build + runtime before enabling (the #129 lesson).
End with DONE: <build status + enable checklist per service, PR link if fixes>. @izzywdev BLOCKED: <q> + STATE if blocked.
@claude — Vet the Phase-2 services (chat-service #127, Unleash #125) so they're deploy-ready. Per the hard lesson from #129 (a service merged "gate-green" but its Docker
tscnever built), do NOT trust the merge — confirm the actual images build + list exactly what's needed to enable each. Land any build fixes via PR.chat-service (#127 / AI Chat)
ghcr.io/izzywdev/fuzefront-chat-service(or the service's image) is in therelease.ymlmatrix AND actually builds + pushes (check the latest release run; if the build stepcontinue-on-error-masks a failure, FIX it — likely tsc/Dockerfile/deps).@fuzefront/chat-ui+@fuzefront/chat-clientpackages build + are wired to publish.ANTHROPIC_API_KEY, chat DB password), the Helmenabledgate + values, Argo wiring, ChromaDB RAG dependency, and the host-backend proxy path for the chat API (verify it's mounted same-origin, not just in the service — same gap class as Federated Clock app does not mount in prod (infinite spinner) — host /api/v1/app-registry proxy + frontend manifest-shape/loader + shared-React + slug migration + e2e #132).Unleash (#125 / feature flags)
unleashorg/unleash-serverimage tag is pinned (external image; not a build-matrix entry). Confirm theunleash-db-bootstrapJob +unleash-secretsSealedSecret scaffolding exist.@fuzefront/feature-flags(OpenFeature + Unleash provider) builds + publish-config.INIT_ADMIN_API_TOKENSadmin token, a client/frontend API token, the unleash DB password), theunleash.enabledgate, Argo wiring, and the client's connection endpoint/token.Deliverable
A report (comment) per service: BUILD = pass/fail (+ fixes PR'd), and a precise ENABLE CHECKLIST (exact secret keys to seal + the
enabledflag + tag to set). Do NOT enable in prod (needs real secrets from the operator) — just make them green + ready.STATE
done = #127/#125 merged to master; remaining = verify real Docker builds (not gate-green), fix build gaps, produce the enable checklist + required secrets. decisions = verify image build + runtime before enabling (the #129 lesson).
End with
DONE: <build status + enable checklist per service, PR link if fixes>.@izzywdev BLOCKED: <q>+ STATE if blocked.