Feat/ghcr integrations health - #232
Conversation
…Zero + Ollama behavior; add integration and model management guides
…ith env overrides; update LOCAL_DEV/TOOLING for TensorZero/Ollama notes
…onsole pages; docs: note MCP UI wrappers and env overrides
… port collision; docs: note alternate port in UI README
…date compose default public_url to 8281; console Quick Link for Invidious; docs unchanged
…Archon; add published-image override; console wrappers + personas page; boot‑JWT upload fixes; model profiles + tooling; docs updated (LOCAL_DEV, MAKE_TARGETS, SMOKETESTS, AGENTS)
…R build workflow for forks; docs: CI guide + env vars
…t; align with console defaults
…d POSTGREST_URL env with 3010 default
…ST_URL to query pmoves_core when Supabase CLI REST hides schema
…d SERVICE_HEALTH_ENDPOINTS guide; update LOCAL_DEV/SMOKETESTS/AGENTS/README
…ous 3005; Hi-RAG health path; next steps (Loki, YT fallback, rerank). Update AGENTS, NEXT_STEPS, ROADMAP (2025-11-06).
…bilization sprint.
|
Caution Review failedThe pull request is closed. WalkthroughAdds a GHCR multi-arch build/publish workflow, extensive operational and stabilization documentation, model-management tooling and manifests, boot-JWT auth plumbing across the UI, TensorZero embedding support and Hi‑RAG GPU device handling, many compose/image parameterizations, new services, and multiple scripts/migrations for environment and infra orchestration. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant Proxy as Next.js Proxy
participant UI as PMOVES UI
participant SupAuth as Supabase Auth
Client->>Proxy: Request page
alt NEXT_PUBLIC_SUPABASE_BOOT_USER_JWT present
Proxy->>Proxy: Bypass auth (NextResponse.next)
Proxy->>UI: Allow request through
else
Proxy->>SupAuth: Check session cookie
alt session valid
Proxy->>UI: Serve page
else
Proxy->>Client: Redirect to /login
end
end
Note over UI: UI may call getBootUser()/createSupabaseServerClient to bootstrap session from boot JWT
sequenceDiagram
participant PMOVES.YT as App
participant Resolver as _geometry_url_candidates
participant GPU as HiRAG GPU
participant CPU as HiRAG CPU
PMOVES.YT->>Resolver: compute candidates (gpu first)
Resolver-->>PMOVES.YT: [gpu_base, cpu_base, ...]
PMOVES.YT->>GPU: POST /geometry_events
alt 200 OK
GPU-->>PMOVES.YT: success
PMOVES.YT->>PMOVES.YT: log primary route
else
GPU-->>PMOVES.YT: error
PMOVES.YT->>CPU: POST /geometry_events
alt 200 OK
CPU-->>PMOVES.YT: success
PMOVES.YT->>PMOVES.YT: log fallback route
else
CPU-->>PMOVES.YT: error
PMOVES.YT->>PMOVES.YT: raise 502 with aggregate errors
end
end
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Areas requiring extra attention:
Possibly related PRs
Suggested labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (104)
Note Free review on us!CodeRabbit is offering free reviews until Fri Nov 07 2025 to showcase some of the refinements we've made. Comment |
There was a problem hiding this comment.
💡 Codex Review
PMOVES.AI/pmoves/ui/app/api/uploads/persist/route.ts
Lines 221 to 225 in eb22d27
The persist upload handler now supports running under a boot JWT without a browser session, but the transcript upsert still references session.user.id. When the endpoint is invoked in the new boot‑JWT mode (no cookie session, ownerId passed in the body), session is null, so this line throws before any metadata is stored. That breaks uploads for exactly the configuration the commit introduced. Use the already computed effectiveUserId (or skip the owner field) so the route works both with and without a logged-in session.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Feat/ghcr integrations health
…-state-consolidation Fix Supabase key validation and consolidate frontend state management
PMOVES.AI — Stabilization Sprint (Nov 6, 2025)
This PR captures infra/app hardening completed today and a short plan to finish the sprint.
Summary
Notable decisions
Operator quick links
Evidence
Follow‑ups (next 48h)
Files touched
@codex review
Summary by CodeRabbit
New Features
Documentation
Chores