Skip to content

Document M2 atomic reindex rollout - #84

Merged
BigSimmo merged 2 commits into
mainfrom
codex/m2-atomic-reindex-plan
Jun 27, 2026
Merged

Document M2 atomic reindex rollout#84
BigSimmo merged 2 commits into
mainfrom
codex/m2-atomic-reindex-plan

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

  • Adds the dedicated M2 atomic reindex migration note before implementation.
  • Documents API/config touchpoints, compatibility assumptions, migration shape, tests, and acceptance criteria.
  • Keeps M2 separate from the 80/20 remediation PR.

Verification

  • Docs-only change; no runtime checks were required.
  • Source branch is based on origin/main and contains no M2 code changes.

Next Step

  • Review the migration assumptions, then implement M2 in this branch with targeted reindex/retrieval tests.

@BigSimmo
BigSimmo marked this pull request as ready for review June 27, 2026 14:54
Copilot AI review requested due to automatic review settings June 27, 2026 14:54
@BigSimmo
BigSimmo merged commit eecec7c into main Jun 27, 2026
5 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a planning/implementation note documenting the intended “M2 atomic reindex” rollout so that reindexing can complete atomically (preventing search/retrieval/telemetry from observing partially swapped index generations) before any code is changed.

Changes:

  • Introduces a dedicated migration note describing current risks, touchpoints, and compatibility assumptions.
  • Outlines a proposed “staged generation → single atomic cutover → cleanup” migration shape.
  • Defines required tests and acceptance criteria to validate the rollout.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@BigSimmo
BigSimmo deleted the codex/m2-atomic-reindex-plan branch June 28, 2026 01:47
cursor Bot pushed a commit that referenced this pull request Jul 28, 2026
Main advanced with RAG/search/mockup work. Real conflict was only in
docs/outstanding-issues.md: keep #12 in Resolved (this PR) while retaining
main's newer open/resolved rows (#24 open; #19/#29/#80/#84 archive).

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
cursor Bot pushed a commit that referenced this pull request Jul 28, 2026
Resolve outstanding-issues ledger conflict by keeping main's archive
claim on #84 and capturing the upload-limit sync recommendation as #85.

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants