Skip to content

Report disposable Odoo20 preservation failures in one diagnostic #399

Closed

Description

@shiny-code-app

The Director explicitly requested one consolidated20 diagnostic on cbusillo/odoo-tenant-opw#314 instead of one fatal preservation check per run. The current pre-upgrade orchestration stops on its first rejected plan.

Add an explicit disposable-migration diagnostic path that reports independent preservation failures and continues independent checks, while retaining original data, isolation/sanitization and successful-migration distinctions. Load the pinned upstream20 framework for that diagnostic. Report blocked coverage when a real registry failure prevents later checks. Keep ordinary non-diagnostic behavior unchanged.

Admission: milestone https://github.com/cbusillo/direction/issues/4 . Next actor: agent:01a1af86-fed7-7980-8b79-f8b78d3104c1 . Execution and actual results remain on cbusillo/odoo-tenant-opw#314.

Current Status

State: Source custody handed off for account succession; exact authored claim release is confirmed. Existing source evidence and retained PR status below remain point-in-time facts, not new readiness proof.
Historical source native: 01a1af86-fed7-7980-8b79-f8b78d3104c1; exact authored claim released for account succession.
Next actor: agent:supervisor-milestone
Branch: work/opw314-diagnostic-1106
Next action: Verify the full account-succession handoff and exact claim audit at https://github.com/cbusillo/odoo-tenant-opw/issues/314#issuecomment-6817852660 before arranging non-overlapping codex-chris succession. Preserve retained source trees/PRs, original keys and qualified run030 inputs; successor source delivery uses the existing reviewed evidence and normal claim route. No source, runtime or cleanup operation is assigned by this status edit.
Last verified: 2026-11-06T20:26:02-05:00

Account succession and retained work: https://github.com/cbusillo/odoo-tenant-opw/issues/314#issuecomment-6817852660 . Source branches/worktrees and frozen inputs are intentionally retained; no ledger transfer, operator launch, runtime read, cleanup or checkout refresh occurred.

Activity

  1. shiny-code-app commented on Nov 7, 2026

    @shiny-code-app
    ContributorAuthor

    Claimed by OPW314-EXECUTE-ASTRA-1106

    Session: 01a1af86-fed7-7980-8b79-f8b78d3104c1
    Branch: work/opw314-diagnostic-1106
    Claimed at: 2026-11-06T20:26:02-05:00
    Next action: Implement Director-approved consolidated saved19-to20 diagnostic and report real failures in one job

    Admission: milestone; https://github.com/cbusillo/direction/issues/4

    Wait resolution: Read complete newly-created issue399; no person/event waits. Director explicitly ordered this diagnostic in active314 dispatch; exact adoption https://github.com/cbusillo/odoo-tenant-opw/issues/314#issuecomment-6700272065

    Work record

  2. shiny-code-app commented on Nov 12, 2026

    @shiny-code-app
    ContributorAuthor

    Released claim 6700315555

    Next actor: agent:supervisor-milestone

    Full current operational/source handoff: https://github.com/cbusillo/odoo-tenant-opw/issues/314#issuecomment-6817852660 . Source native 01a1af86-fed7-7980-8b79-f8b78d3104c1, existing OPW314-EXECUTE-ASTRA-1106/codex-info; account-capacity succession is to codex-chris only after Supervisor verifies final audit and guarded non-overlap. This exact claim releases source ownership only. Preserve branch work/opw314-diagnostic-1106, every referenced tree/commit, all originals/keys/qualified run030 pair/archive and unknown-effect/production safeguards. No source/data/credential/ledger/account mutation or new operation is authorised.

    The real testing original034214Z-d98e830f068b6221 is terminal pass at2:18:53AMET November12; canonical result https://github.com/cbusillo/odoo-tenant-opw/issues/314#issuecomment-6817585690 . No active observer/job/copy/controller is owned by this source. Existing source checks/reviews/inspection limits remain on their exact records; no new qualification is claimed. Do not resume historical PIDs/closed workers.

    Retained source stack, same source native: #403 at0fcf6f0e658f0f7aaee478d789656b2594bc3019; #405 at346328bae8d791f1de714cdd23f7bd0757894c77; #407 atbc3bb0391dcf044bf0bddb99dee55d7ad9fab538; #411 DRAFT at1dd946511dc5c0b67101ebbd69447700134b4c33. Preserve current bases and existing current-head Ready/review/CI receipts; normal delivery/proof remains with Supervisor/generation9, not an old metadata native. No rebase/retarget/source edits/Ready refresh or data rerun here.

    Other retained status follow-through: cbusillo/codex-skills#3979, https://github.com/cbusillo/odoo-tenant-opw/issues/345, https://github.com/cbusillo/shiny-infra-ops/issues/746. These preserve source adoption/current-copy outcome/history, not additional data authority. No cleanup/pruning; full claim audit after exact releases will be posted to314/277. Same source session stays at prompt until Supervisor verifies closure.

    Session: 01a1af86-fed7-7980-8b79-f8b78d3104c1

    Retained PR handoff: #403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions