docs(dashboard): refresh post-PRs #867-871 + branch sync - #872
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated the production audit dashboard docs to reflect merged PRs Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md`:
- Around line 16-24: Update the "PRs `#867-`#871 — Port Registry, Smoke Test &
Security Fixes" section to actually include PR `#869` and the promised
verification artifacts: add a bullet for PR `#869` summarizing its change, then
append concise verification lines stating "docs-reconcile drift: 0", the updated
static smoke test totals (new counts) and "CodeQL suppression comment confirmed
at serviceHealth.ts:71 (pending GitHub dismissal)"; edit the top-of-file
narrative to reflect the full merge window (PRs `#867`–#871) and that these three
verification artifacts have been added so the section is consistent with the PR
scope.
- Line 24: Update the inconsistent CodeQL open-alerts counts by replacing the
hardcoded "CodeQL status: 1 open (FP `#195`)" text with a single source-of-truth
value used elsewhere in the doc: locate the occurrences of the literal "CodeQL
status" / "open" and "FP `#195`" and make them derive from the same computed
status or evidence block (the runbook/smoke results) used for the live status
line; ensure all occurrences (including the block that currently reads "0 open")
reference that shared variable or text and adjust the FP annotation so every
section shows the same current open-count and matching FP note.
- Around line 19-21: Update the canonical services catalog entries to match the
recent port remaps: change the PostgREST service entry (label "PostgREST") to
use port 3000 instead of 3010, and add a dedicated service entry for
"supabase-realtime" (or "subabase-realtime" if that exact label is used) with
port 4010; ensure the service entry follows the same schema/fields as other
services in services-catalog.md so the PORT_REGISTRY/smoke-test expectations
align with the dashboard.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f8feaf79-7d70-48d9-a79b-f683d37c5b30
📒 Files selected for processing (1)
pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md
| ### PRs #867-#871 — Port Registry, Smoke Test & Security Fixes | ||
|
|
||
| - **PR #867** (`fix(security)`): CodeQL #196 — validate service URLs with `URL` constructor (XSS prevention) | ||
| - **PR #868** (`fix(smoke)`): Remap supabase-realtime port 4000→4010 in smoke tests + widen grep window | ||
| - **PR #870** (`fix(ports)`): Complete realtime 4000→4010 migration across PORT_REGISTRY and smoke tests | ||
| - **PR #871** (`fix(ui)`): Align PostgREST port registry (3010→3000) + env template fix + widen Jellyfin smoke HTTP codes (accept 502) | ||
| - **PR #866 closed** — superseded by the individual targeted PRs #867-#871 | ||
| - **Branch sync:** main → Hardened synced (`c6bc276f`) | ||
| - **CodeQL status:** 1 open (#195 — false positive, `lgtm` suppression comment at `serviceHealth.ts:71`, pending GitHub dismissal on next scan) |
There was a problem hiding this comment.
Complete the #867-#871 refresh section.
This section says the dashboard is refreshed for PRs #867-#871, but it skips PR #869 and also omits the fresh verification artifacts called out in the PR scope (docs-reconcile drift status, updated static smoke totals, suppression confirmation). That leaves the new top-of-file narrative incomplete relative to the stated merge window.
As per coding guidelines, "Extend Latest Changes to include PRs 867–871 with precise fixes ... Verification artifacts: note 0 drift from docs reconciliation, static smoke test results, and CodeQL suppression comment confirmation ..."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md` around lines 16 - 24, Update the
"PRs `#867-`#871 — Port Registry, Smoke Test & Security Fixes" section to actually
include PR `#869` and the promised verification artifacts: add a bullet for PR
`#869` summarizing its change, then append concise verification lines stating
"docs-reconcile drift: 0", the updated static smoke test totals (new counts) and
"CodeQL suppression comment confirmed at serviceHealth.ts:71 (pending GitHub
dismissal)"; edit the top-of-file narrative to reflect the full merge window
(PRs `#867`–#871) and that these three verification artifacts have been added so
the section is consistent with the PR scope.
| - **PR #868** (`fix(smoke)`): Remap supabase-realtime port 4000→4010 in smoke tests + widen grep window | ||
| - **PR #870** (`fix(ports)`): Complete realtime 4000→4010 migration across PORT_REGISTRY and smoke tests | ||
| - **PR #871** (`fix(ui)`): Align PostgREST port registry (3010→3000) + env template fix + widen Jellyfin smoke HTTP codes (accept 502) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
catalog="$(fd '^services-catalog\.md$' .claude | head -n1)"
test -n "$catalog"
# Expect the catalog entries for supabase-realtime and PostgREST to reflect 4010 and 3000,
# and not retain stale 4000/3010 mappings for the current host-port assignments.
rg -n -C2 'supabase-realtime|PostgREST|4010|4000|3010|3000' "$catalog"Repository: POWERFULMOVES/PMOVES.AI
Length of output: 1294
🏁 Script executed:
#!/bin/bash
set -euo pipefail
catalog="$(fd '^services-catalog\.md$' .claude | head -n1)"
test -n "$catalog"
echo "=== Full Supabase section ==="
rg -n -A 10 '^### Supabase$' "$catalog"
echo ""
echo "=== Check for supabase-realtime section ==="
rg -n -B2 -A5 'realtime|supabase-realtime' "$catalog"Repository: POWERFULMOVES/PMOVES.AI
Length of output: 1296
Sync the canonical services catalog with these port remaps.
This doc now records subabase-realtime 4000→4010 and PostgREST 3010→3000. However, .claude/context/services-catalog.md has not been updated:
- PostgREST still shows port 3010 (line 608), not the migrated 3000
- Subabase-realtime has no dedicated service entry with port assignment
Update the catalog to reflect both port migrations to prevent immediate drift from the dashboard.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md` around lines 19 - 21, Update the
canonical services catalog entries to match the recent port remaps: change the
PostgREST service entry (label "PostgREST") to use port 3000 instead of 3010,
and add a dedicated service entry for "supabase-realtime" (or
"subabase-realtime" if that exact label is used) with port 4010; ensure the
service entry follows the same schema/fields as other services in
services-catalog.md so the PORT_REGISTRY/smoke-test expectations align with the
dashboard.
| - **PR #871** (`fix(ui)`): Align PostgREST port registry (3010→3000) + env template fix + widen Jellyfin smoke HTTP codes (accept 502) | ||
| - **PR #866 closed** — superseded by the individual targeted PRs #867-#871 | ||
| - **Branch sync:** main → Hardened synced (`c6bc276f`) | ||
| - **CodeQL status:** 1 open (#195 — false positive, `lgtm` suppression comment at `serviceHealth.ts:71`, pending GitHub dismissal on next scan) |
There was a problem hiding this comment.
Make the CodeQL “open alerts” count internally consistent.
These lines now report 1 open (FP #195), but Line 679 still says live CodeQL status is 0 open. A single dashboard should not present two different current counts for the same date window.
As per coding guidelines, "Keep status claims aligned with evidence in runbooks and smokes."
Also applies to: 505-513
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pmoves/docs/PRODUCTION_AUDIT_DASHBOARD.md` at line 24, Update the
inconsistent CodeQL open-alerts counts by replacing the hardcoded "CodeQL
status: 1 open (FP `#195`)" text with a single source-of-truth value used
elsewhere in the doc: locate the occurrences of the literal "CodeQL status" /
"open" and "FP `#195`" and make them derive from the same computed status or
evidence block (the runbook/smoke results) used for the live status line; ensure
all occurrences (including the block that currently reads "0 open") reference
that shared variable or text and adjust the FP annotation so every section shows
the same current open-count and matching FP note.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 87ee9f57cb
ℹ️ 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".
| - **PR #870** (`fix(ports)`): Complete realtime 4000→4010 migration across PORT_REGISTRY and smoke tests | ||
| - **PR #871** (`fix(ui)`): Align PostgREST port registry (3010→3000) + env template fix + widen Jellyfin smoke HTTP codes (accept 502) | ||
| - **PR #866 closed** — superseded by the individual targeted PRs #867-#871 | ||
| - **Branch sync:** main → Hardened synced (`c6bc276f`) |
There was a problem hiding this comment.
The new branch-sync bullet references c6bc276f, but that SHA is not present in this repository history (no match in git rev-list --all), so readers cannot verify the claimed main → Hardened sync event from the dashboard. Since this document is positioned as the production audit source of truth, an unresolvable commit ID breaks traceability for release/audit checks and should be replaced with an actual reachable sync commit.
Useful? React with 👍 / 👎.
postgres-meta image lacks wget/curl — use built-in Node.js http module for the /health endpoint check. Verified healthy in local testing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Docker Hardening ValidationHardening Validation ReportValidated: Wed Mar 11 23:26:38 UTC 2026Services CheckedPMOVES.AI Docker Hardening Validation[INFO] Checking: pmoves/docker-compose.hardened.yml [INFO] Validating: hi-rag-gateway-v2 [INFO] Validating: extract-worker [INFO] Validating: langextract [INFO] Validating: presign [INFO] Validating: render-webhook [INFO] Validating: retrieval-eval [INFO] Validating: pdf-ingest [INFO] Validating: jellyfin-bridge [INFO] Validating: invidious-companion-proxy [INFO] Validating: ffmpeg-whisper [INFO] Validating: media-video [INFO] Validating: media-audio [INFO] Validating: hi-rag-gateway-v2-gpu [INFO] Validating: hi-rag-gateway-gpu [INFO] Validating: deepresearch [INFO] Validating: supaserch [INFO] Validating: publisher-discord [INFO] Validating: mesh-agent [INFO] Validating: nats-echo-req [INFO] Validating: nats-echo-res [INFO] Validating: publisher [INFO] Validating: analysis-echo [INFO] Validating: graph-linker [INFO] Validating: comfy-watcher [INFO] Validating: grayjay-plugin-host [INFO] Validating: agent-zero [INFO] Validating: archon [INFO] Validating: channel-monitor [INFO] Validating: pmoves-yt [INFO] Validating: notebook-sync [INFO] Validating: supabase_service_role_key [INFO] Validating: supabase_jwt_secret ====================================== |
2 participants
Summary
c6bc276f)lgtmsuppression, pending GitHub dismissalc81b2431) and executive summary timestampVerification
make -C pmoves docs-reconcile— 0 drift, documents freshTest plan
docs-reconcileexit 0git diffserviceHealth.ts:71)🤖 Generated with Claude Code
Summary by CodeRabbit