[cnkang]

Summary

Adds the evidence that the first stability report left open, and corrects the
status lines that changed after the merge.

• New follow-up report: docs/validation/cross-device-opencode-pi-stability-followup-2026-10.md.
• D2: identical text under one barrier returns one record, competing updates return one update and one conflict, independent updates both commit.
• D6: released 0.5.1 keeps the FAILED gate, main returns QUARANTINED and continues serving writes.
• The first report now names both merged pull requests and the CodeRabbit approval.
• The 24-hour soak is recorded as partial with the reason. No result is claimed for a run that did not finish.
• New 24-hour cloud soak: docs/validation/cross-device-cloud-soak-2026-10.md (run cloud-2026-10-27, Runtime main f843556, two cloud ARM64 hosts, 330 controlled restarts, ledger 2115 COMMITTED / 0 FAILED, private checks leaked 0).

Verification

• Markdown link check over 65 files: no missing local links.
• Released baseline: hermes-plugin-qdrant-memory==0.5.1 from PyPI in a separate environment.
• Main branch: 1acfeb8 through the acceptance Owner.
• Cloud soak: full 24 h window on both hosts, journals intact on A; B tail reconstructed from hourly copies after a harness resume bug deleted the finished journal (documented in the report).

Notes

Documentation only. No release, tag or version change.

Summary by Sourcery

Document the outstanding stability evidence and update prior validation records with the final review and merge status.

Enhancements:

• Record follow-up cross-device stability evidence for concurrency, failure recovery, and released-baseline behavior.
• Document the completed 24-hour cloud ARM64 soak, including product findings, isolation results, restart behavior, and harness limitations.
• Correct the original stability report to reflect merged changes and completed CodeRabbit review.

Documentation:

• Add validation reports covering the cross-device stability follow-up and 24-hour cloud soak.

[sourcery-ai]

Sorry @cnkang, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 3 days and 19 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: cnkang/hermes-plugin-qdrant-memory
• Branch: codex/stability-followup
• File: .coderabbit.yaml
• Commit: c74262d
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 1fc178fd-e522-421b-97fa-ca35b605253a

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}

[sourcery-ai]

Reviewer's Guide

This documentation-only PR adds the missing post-merge stability evidence and corrects the original report’s status claims, including D2 concurrency results, the released 0.5.1 versus main D6 comparison, recovery outcomes, review approvals, and the incomplete 24-hour soak. Verification covered local Markdown links, a separately installed PyPI baseline, and main-branch acceptance testing; no release or version metadata changes are included.

Sequence diagram for D2 concurrent memory updates

sequenceDiagram
    participant HostA as OpenCode_A
    participant HostB as OpenCode_B
    participant Service as Memory_Service
    participant Ledger as Event_Ledger

    par Competing updates
        HostA->>Service: update()
        Service-->>HostA: update committed
    and
        HostB->>Service: update()
        Service-->>HostB: conflict
    end
    Service->>Ledger: record committed events
    Ledger-->>Service: operations committed

Loading

Flow diagram for partial 24-hour soak evidence

flowchart TD
    Start[24-hour soak attempt] --> Complete{Run completed?}
    Complete -->|No| Partial[PARTIAL result]
    Partial --> Evidence[Earlier 20-minute run retained]
    Evidence --> Remaining[Run full 24-hour soak on a stable host]
    Complete -->|Yes| Pass[Record completed soak result]

Loading

File-Level Changes

Change	Details	Files
Adds a post-merge follow-up report documenting concurrency, released-baseline, recovery, review, and soak evidence.	Records D2 outcomes for duplicate, competing, and independent updates. Compares Runtime 0.5.1 from PyPI with main’s quarantine behavior under D6. Documents recovery checks, partial 24-hour soak status, review state, and remaining work.	docs/validation/cross-device-opencode-pi-stability-followup-2026-10.md
Updates the original stability report to reflect merged pull requests and completed CodeRabbit review.	Adds a post-merge link to the follow-up report. Changes CodeRabbit status to approved and identifies both pull requests as merged. Clarifies that no release was published from the original work.	docs/validation/cross-device-opencode-pi-stability-2026-10.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.