docs(ops): align data services and release cadence

[POWERFULMOVES]

Summary

• align the canonical operator docs around one modular data-services provisioning contract across Supabase, Neo4j, Qdrant, Meilisearch, and optional n8n
• make the Supabase runtime choice explicit so bootstrap/data-repair and release-mode parity do not silently drift
• document the existing release-note / CVE intake funnel using CodeQL, weekly bump/canary workflows, local GHCR+Trivy gates, and the dashboard/hardening docs

Testing

• git diff --check

Reviewer Notes

• Docs-only PR.
• This intentionally updates existing canonical docs instead of adding another parallel runbook.
• The goal is to give the z890 node and the in-flight Supabase work one operator-facing source of truth for data-plane layering and maintenance cadence.
• Operational note: this PR documents the intended contract, but the live Supabase/runtime lane still needs to be reconciled against the running node work when Claude is available again.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates documentation across eight files to establish Release Notes/CVE intake funnel workflows, standardize modular data-plane provisioning guidance (Supabase, Qdrant, Meilisearch, Neo4j, n8n), clarify Supabase runtime selection, and document new operational Make targets and cadence-based review processes.

Changes

Cohort / File(s)	Summary
Hardening & Release Tracking docs/hardening/PMOVES-hardening-tracker.md, pmoves/docs/PMOVES.AI PLANS/README_DOCS_INDEX.md	Added Release Notes/CVE Funnel section defining cadence-based review workflows (daily merge lane, weekly scanning, pre-release checks); extended doc index with hardening tracker, data services, and production audit dashboard links.
Planning & Roadmap Documentation pmoves/docs/NEXT_STEPS.md, pmoves/docs/PMOVES.AI PLANS/ROADMAP.md	Updated last-modified dates and added March 26 sections documenting modular data-plane provisioning order (Supabase→retrieval indexes→graph→optional n8n) and routing release/CVE intake through scheduled CI workflows with explicit runtime selection via SUPABASE_RUNTIME environment variable.
Operations Guides pmoves/docs/operations/FIRST_RUN.md, pmoves/docs/operations/MAKE_TARGETS.md	Refactored FIRST_RUN to emphasize layered provisioning with MinIO compatibility guidance and added integration checkpoints; expanded MAKE_TARGETS with data services bootstrap targets, optional n8n bring-up, release-gate targets, and clarified Supabase runtime mode selection to prevent bootstrap/compose drift.
Services Documentation pmoves/docs/services/README.md, pmoves/docs/services/supabase/README.md	Added core data-plane service index listing Supabase, Qdrant, Meilisearch, Neo4j, and N8N; expanded Supabase README with explicit runtime selection warnings, data services provisioning contract, runtime-specific command guidance, and Release Notes/CVE funnel links.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• POWERFULMOVES/PMOVES.AI#792: Updates MAKE_TARGETS and operations docs with layered bring-up sequencing and modular provisioning targets that align with this PR's operational guidance.
• POWERFULMOVES/PMOVES.AI#822: Adds GHCR image entries and per-image Makefile targets that correspond to the Release Notes/CVE intake and docker-build documentation added in this PR.
• POWERFULMOVES/PMOVES.AI#762: Modifies ROADMAP.md and NEXT_STEPS.md with overlapping release-cadence and CI/CVE intake wording updates.

Suggested labels

codex

Poem

🐰 Fresh docs hop through the data lanes,
Supabase guards and Neo4j reigns,
Release cadence flows with weekly scans,
Runtime selection now in steady hands,
Provisioning layers, modular and neat—
Our ops documentation now complete!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	PR description covers summary and testing, but is missing several required template sections and detailed testing output.	Add Testing details with actual command output/results, complete Required Checks section with all checkboxes, and fill in Reviewer Notes with specific scrutiny areas or coverage notes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly summarizes the main change: aligning documentation around data services provisioning and release cadence across multiple components.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/data-services-provisioning-docs

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

pmoves/docs/services/README.md (1)

5-44: ⚠️ Potential issue | 🟠 Major

Address duplicate service entries between "Core data plane" and other sections.

The new "Core data plane" section lists neo4j (line 9), n8n (line 10), and supabase (line 44), but these services also appear in later sections:

• Line 33: neo4j in "Implemented (compose-managed)"
• Line 43: n8n in "Auxiliary / Libraries / Adapters"
• Line 44: supabase in "Auxiliary / Libraries / Adapters"

This duplication creates ambiguity about which categorization is authoritative.

Recommended approach:

1. Keep services in "Core data plane" only (preferred), OR
2. Add a note like (also listed in Core data plane above) for the duplicate entries, OR
3. Remove the duplicates from the lower sections if "Core data plane" is the new canonical grouping

As per coding guidelines, the services index should reflect the "core data plane" set without creating parallel/copy runbooks.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pmoves/docs/services/README.md` around lines 5 - 44, The services index lists
neo4j, n8n, and supabase in the "Core data plane" section but repeats them
later, causing ambiguity; update pmoves/docs/services/README.md so the "Core
data plane" is canonical by removing the duplicate entries for neo4j from
"Implemented (compose-managed)" and for n8n and supabase from "Auxiliary /
Libraries / Adapters" (or alternatively add “(also listed in Core data plane)”
next to those entries if you prefer to keep them), and verify the remaining
lists and links (section headings "Core data plane", "Implemented
(compose-managed)", "Auxiliary / Libraries / Adapters") remain correctly ordered
and formatted.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@pmoves/docs/services/README.md`:
- Around line 5-44: The services index lists neo4j, n8n, and supabase in the
"Core data plane" section but repeats them later, causing ambiguity; update
pmoves/docs/services/README.md so the "Core data plane" is canonical by removing
the duplicate entries for neo4j from "Implemented (compose-managed)" and for n8n
and supabase from "Auxiliary / Libraries / Adapters" (or alternatively add
“(also listed in Core data plane)” next to those entries if you prefer to keep
them), and verify the remaining lists and links (section headings "Core data
plane", "Implemented (compose-managed)", "Auxiliary / Libraries / Adapters")
remain correctly ordered and formatted.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d7a947fa-8802-4916-8cb0-007e137cd65e

📥 Commits

Reviewing files that changed from the base of the PR and between 3995b98 and 33e10b4.

📒 Files selected for processing (8)

• docs/hardening/PMOVES-hardening-tracker.md
• pmoves/docs/NEXT_STEPS.md
• pmoves/docs/PMOVES.AI PLANS/README_DOCS_INDEX.md
• pmoves/docs/PMOVES.AI PLANS/ROADMAP.md
• pmoves/docs/operations/FIRST_RUN.md
• pmoves/docs/operations/MAKE_TARGETS.md
• pmoves/docs/services/README.md
• pmoves/docs/services/supabase/README.md