Skip to content

Prevent bidirectional GitHub sync from reopening remotely closed stale tickets #339

Closed

Description

@tom-sapletta-com

SESSION_EXECUTION_AUTHORIZATION: Heyasa dependency audit root PLF-19975. Current Planfile edfa131/CLI0.1.126 _execute_sync_with_progress executes outbound before inbound for direction both; all_tickets is a pre-inbound snapshot. Two verified Heyasa stale locally-open/remote-closed records251/240 would be reopened by defaultboth, masking remote closure. Actual inbound-only recovery succeeded. AC: synchronize inbound before outbound for both and reload selected local records after inbound; retain exact ticket/sprint/repository scope, legacy v1 handling, dry-run immutability, explicit one-way semantics and provider/CAS failures. Regression must prove remoteclosed remainsclosed and localterminal projects from fresh snapshot, inlet failure prevents outbound mutation, selected unrelated tickets untouched. No claim of completion for native blocked/done conflicts. Native work-start report route NEW_TICKET_CANDIDATE with0active tickets on edfa131; source scope planfile/cli/groups/sync/core.py and tests/test_sync_bidirectional_order.py. Full approved Wellman39files verified at d8c7a0ad; run capability and real bound work-start succeeded. Existing PLF-17304 remains owner of slow provider enumeration; this request only concerns both-direction state order.

Ticket impact radar (advisory)

  • Complexity: M
  • Score: 52/100
  • Estimated effort: 46 min
  • Split recommended: yes

This estimate does not grant execution, review or merge authority.


Strategy Metadata:

  • repository: semcod/planfile
  • planfile_id: semcod/planfile:d2a989f6ada2f6b2:PLF-20370

SESSION_EXECUTION_AUTHORIZATION: Heyasa dependency audit root PLF-19975. Current Planfile edfa131/CLI0.1.126 _execute_sync_with_progress executes outbound before inbound for direction both; all_tickets is a pre-inbound snapshot. Two verified Heyasa stale locally-open/remote-closed records251/240 would be reopened by defaultboth, masking remote closure. Actual inbound-only recovery succeeded. AC: synchronize inbound before outbound for both and reload selected local records after inbound; retain exact ticket/sprint/repository scope, legacy v1 handling, dry-run immutability, explicit one-way semantics and provider/CAS failures. Regression must prove remoteclosed remainsclosed and localterminal projects from fresh snapshot, inlet failure prevents outbound mutation, selected unrelated tickets untouched. No claim of completion for native blocked/done conflicts. Native work-start report route NEW_TICKET_CANDIDATE with0active tickets on edfa131; source scope planfile/cli/groups/sync/core.py and tests/test_sync_bidirectional_order.py. Full approved Wellman39files verified at d8c7a0ad; run capability and real bound work-start succeeded. Existing PLF-17304 remains owner of slow provider enumeration; this request only concerns both-direction state order.

Ticket impact radar (advisory)

  • Complexity: M
  • Score: 52/100
  • Estimated effort: 46 min
  • Split recommended: yes

This estimate does not grant execution, review or merge authority.

[native279-admission-and-proposal-20261105]
Source remains unchanged and clean at edfa131; no source branch, writer lease, commit or PR. Native allocator reserved ticket-279; its unpublished carrier is reversibly preserved in ignored repository recovery until an admitted material implementation can include it. This is a technical ownership prerequisite, not missing session consent.

Actual protected controller is healthy at HTTPS port18765, pinned runtime2a7bea4aeb2a87528470defb86a5fc136da148f3. Effective policy SHA256 b61716fab617fbd687cd92e10f5e785ad2a8118f152fa2ee8ef1d1a2274f3b41 has35admissions and zero for semcod/planfile. No policy or credentials were changed. Protected owner must resolve an authenticated admitted principal/configuration for native279, then issue initial fenced ownership and the declared canonical v5 checkout route. Do not self-enroll or take old leases. Autonom STARTER-026 records the same repository prerequisite for a different Store/API slice; it grants no ownership for this sync slice.

Concrete preparation: unapplied patch for exactly3files (sync/core.py, test_sync_bidirectional_order.py, test_sync_failure_status.py), no API or runtime dependency change. GitHub both reads inbound first, reloads the same selected snapshot, and compares outbound lifecycle with this pass's observed remote states. Conflicting native lifecycle and unobserved mappings are deferred with a diagnostic; explicit one-way sync semantics remain. Dry-run previews inbound and explicitly defers stale outbound preview. Unmapped local tickets can still publish after inbound.

Validation: independently pinned full Wellman mediates diagnostics; ordinary pytest governance PASS0errors/0warnings. Unchanged published source canary2passed. Proposal executed only in memory/private offline fixtures:114passed across YAML, sharded, legacy, scope/routing and existing outbound failure coverage. Negative control against original source fails on the stale remote closure as expected. git apply --check passes. These are proposal diagnostics, not source delivery or trusted approval.

Admission binds native279/application, accepted base above, target main, intent SHA2564d00dc2f8ea2f16a48d953614f40a7d60038c2a7b55b8a96b9364ac7f3b4c2fe and scope SHA256dbd35dbd14dfd6c7986daa97c90699e6c7774409dbaf7f4c81766896c2608261; 30minute bounded source session. After controller admission: reobserve source scopes/HEAD/lease/PR, validate canonical location, apply and run real source checks, then invoke the declared independent protected publication route. Source AC-02/03/04 remain pending.

Local recoverable artifacts: parent PLF-19975 evidence/heyasa-dependency-audit-20261105/continuation-20261105/{admission-request.json,proposal-manifest.json,native279-unapplied.patch,proposal-tests-final.log,baseline-negative-control.log}. No new implementation ticket is needed.

2026-11-05 follow-up: old native279 proposal HELD. The historical114passing proposal is NOT READY TO APPLY: a new valid local-description control proves that inbound-first overwrites unpublished accepted local planning (localPlanningPreserved:false). Root operational adapter now preserves local planning from the SDK expected_snapshot in both; explicit from imports the managed remote region. It additionally checks managed text after publication including receipt reuse, blocks nested markers, prevents replacement issue creation and lifecycle writes, while retaining numeric identity/CAS/live-execution guards.35offline regressions pass on officialSDK0.1.127. Published127 is older than currentGit sameversion and is not asserted source-identical. New managed-body regression is independently tracked; existing339/native279 remains the sync-order owner. Do not apply historical patch after admission without revised planning-ownership policy/tests and reconciled accepted scope. Carrier intent4d00dc2f and30minute budget unchanged, no source ownership issued. Healthy controller policyb61716fa still has zero semcod/planfile grants; AutonomSTARTER-026 owns shared admission prerequisite for another native slice, does not transfer ownership. Reobserve foreign ticket280 reservation before writing; preserve it. Root local safe adapter is a mitigation, not producer delivery. No local fleet timer found; reusable workflow still calls directionboth and needs producer fix through its owner. Evidence parent continuation-sync-20261105, old-proposal-planning-control.log and safe-sync-tests-final.log.

2026-11-05 revised proposal v2: supplementary120PASS. Existing3implementation paths and acceptedbaseedfa131b retained; no source code/worktree/lease change. Separate unapplied v2 patchSHA2c63df49fb263c17b8eb0f1d2cc0fff58d05c48c6b680efb4fdb5376f29083fa preserves native local planning from SDK expected_snapshot without changing CAS; legacy mapped descriptions survive copied provider view, explicitfrom remains intentional import. Proxy forwards type-level numeric repository identity and status projection. Both metadata updates omit lifecycle requests; normal readback detects concurrent closure. Deferred native conflicts retain successful other receipts but exitnonzero and skip public comments/false full success. Private immutable library model at exactbase:120passed,3legacy-CAS/execution tests skipped; originalbase9negativecontrols and oldv1additional13negativecontrols fail as expected. Lint through pinned Wellman python-mruff with producerconfigPASS; git apply--checkPASS. IMPORTANT: ordinary source pytest did not run tests: GOV-MATERIAL-001/GOV-PACKAGING-003 rejects another owner untracked project/ticket-280 tracking-only carrier. It was preserved unchanged, no gate suppressed. Root published127 cannot execute this currentGit proposal directly because it lacks _bind_sync_state; model input is read-only195module Git archiveSHAfb669147996bf2f43d02dc90d16ccc6e70907d52174e0f214027bab04f4c8aa0, not an installation or delivery checkout. Thus sourcevalidation remainsFAILED/not executed, v2 PENDING_SOURCE_GATE_AND_ADMISSION; v1 remains HELD_DO_NOT_APPLY. Prepared advisory amendment retains paths/scope/budget30minutes and originalintent4d00dc2f, requires owningcontroller reconciliation before application. No runtime/API dependency added. Source20372/#341 remains managed-reader/empty-body/reuse owner. Initialrepositoryadmission stillmissing (policyb61716fa,0semcodPlanfile), no ownership self-issued. Technicalowner shareddependency existingAutonomSTARTER026; native266 scope unchanged. Artifacts parentPLF19975 continuation-proposal-v2-20261105/{proposal-manifest.json,native279-v2-unapplied.patch,amendment-request.json,library-model-diagnostics-final.log,proposal-tests-first.log}.

Continuation20261105 V2 READINESS HOLD: new independent-owner immutable-model control proves late accepted planning is overwritten during outbound bulk persistence. V2 patch2c63df49 remains unapplied and is nowHELD_OUTBOUND_SNAPSHOT_REGRESSION; historical120PASS/3skips did not cover this race. V1 remainsHELD_DO_NOT_APPLY. Reuse Planfile20372/#341 for snapshot-safe native outbound persistence in operations.py and source tests; owning controller must reconcile that dependency/scope with original279 intent before any source application. Do not apply v2 merely after admission. Root adapter local mitigation48behavioral testsPASS; raw native plan/private outputs/live execution preserved even when another SDK store writes without a changed revision, and partial success receipts retained. Actual producer code remains unchanged edfa131, no writer lease/fencing/canonical279 checkout; foreign280 and failed required source gate preserved. Exact proofs in parent continuation-outbound-cas-20261105. No new source implementation ticket or policy bypass.

Delivery update 2026-11-06: native279 PR342

The corrected V3 implementation is committed and pushed at b0e4840 in #342. It preserves local planning, observes GitHub lifecycle inbound first, and uses guarded raw snapshots for reference-only outbound persistence. The historical V1/V2 proposals above remain unapplied; their holds do not describe V3. Native tests:93+35=128passed,0skips; Ruff and governancePASS. Seven of8requiredCIchecksPASS; only unrelated existing Goal2.2.10 freshness fails. Native281 has an approved Goal2.2.11-only lock proposal but no editing lease or applied source delta. Protected controller cannot release our expired frozen279 (lease-c1b42dc54857ad048e6def49f710c7e6, revision5/fence838); exact owner prerequisite STARTER-031 is published at https://github.com/subactor/autonom/issues/205. Private controller proposal11testsPASS is not an applied source fix or deployed runtime. All8requiredchecks remain. PR342 is open, not merged or deployed; broader API/global outbound work remains #341.

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

    managedAuto-created label for managedplanfileAuto-created label for planfilepriority-highAuto-created label for priority-high

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions