[harrisonoconnorhover]

Context

This draft starts from Josh's current main at e8b958d and preserves all three of its unique
commits. It then merges Harrison's exact functional beta-readiness tip at 7a1378f.

This is intended as a collaborative reconciliation, not a replacement of Josh's work. The
capability implementation, tests, tickets, and reviewed secret-scan configuration from Josh's
branch remain byte-for-byte unchanged.

Included

• sanitized failure history and interrupted-run reconciliation from Harrison PR #81
• supported 24-hour staging expiration and cleanup from Harrison PRs #82 and #85
• plan-first installation, permission preflight, upgrade, and rollback work from Harrison PR #83
• four-endpoint Salesforce CRM configuration and five governed models from Harrison PR #84
• both repositories' decision-log sections, retained together

Explicitly excluded

• Harrison PR #86 and all 0.6.0rc1 release-only metadata
• tags, package publication, deployment, Terraform apply, scheduler changes, and live mutations
• removal or redesign of Josh's get_deleted or write-back capability contracts

Package, lockfile, scaffold, and CI assertions therefore remain at 0.5.1 in this branch.

Validation

• combined full suite: 770 passed
• Ruff formatting and lint: passed
• strict mypy: passed
• platform and stage-zero Terraform validation: passed with backends disabled
• wheel/sdist inspection and external source-free install/generation/validation: passed
• local Linux container build: passed
• adversarial reconciliation review: passed with no material findings

This PR is deliberately a draft for Josh to review and adjust. Nothing should merge automatically.

[harrisonoconnorhover]

Suggested review order

The reconciliation PR is intentionally the stable base. The optional-capability work is split into small follow-ups so each concept can be reviewed independently:

1. This PR (Reconcile beta-readiness work without release metadata #3): combines both forks without release metadata and preserves Josh's three unique commits.
2. Harrison Dander #87: makes get_deleted invocable through the generic capability layer; no provider behavior.
3. Harrison Dander #88: adds explicitly confirmed generic write invocation using a stateful fake; no Salesforce code and no scheduled-runtime write path.
4. Salesforce plugin docs: record RC27 AWS correctness qualification #10–#14: implements deleted feed, create, update, delete, and opt-in External-ID upsert one operation per stacked draft PR.

The provider PRs install exact unreleased Dander commits in CI, remain drafts, and do not change package dependency metadata. Nothing should be published until the Dander contracts are reviewed, merged, and released. No live source mutation has been run.

[harrisonoconnorhover]

Since roughly 11pm, the main thread completed a substantial release and portability slice: - Published stable Dander 0.6.0, completing the Salesforce beta-readiness work. - Opened the cloud-portability architecture plan as a docs-only draft PR to Josh: WagnerJ-Dev/dander#4 <#4>. - Merged portability PRs #95–#100: - versioned OCI runtime execution contract - runtime inspection and conformance commands - normalized events, results, exit codes, and signal handling - OCI labels, capability metadata, SBOM/provenance, and immutable digest records - cloud-neutral execution templates - Cloud Run Terraform consuming those shared templates without replacing existing resources - Published Dander 0.7.0rc1, then correctly rejected it before deployment after discovering connector installation could silently downgrade Dander to 0.6.0. - Fixed that downgrade behavior and its CLI reporting through merged PRs #102 and #104. - Published compatible connector candidates: - Salesforce 0.3.1rc1 - ServiceNow 0.2.2rc1 - Updated Dander’s curated connector catalog through merged PR #103. - Prepared replacement Dander 0.7.0rc2; PR #105 <harrisonoconnorhover#105> was in protected CI when the main thread paused. - All local Dander checks passed: 815 tests, Ruff, strict typing, package builds, and release-metadata validation. Importantly, neither the retained production-like project nor the isolated GCP project was mutated. AWS and the later portability phases have not begun yet.

…

On Thu, Aug 6, 2026 at 7:25 PM WagnerJ-Dev ***@***.***> wrote: Merged #3 <#3> into main. — Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=A7FXZXOML54QU3ZNF35UQ635IUHYBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJQHEYDONBUGEYTNJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#event-29090744116>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7FXZXMGCICQCVNUKKBUQKL5IUHYBAVCNFSNUABGKJSXA33TNF2G64TZHMYTGMBYGIZTEMZUG45US43TOVSTWNJQG44TINJTGA4DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A7FXZXIF4ZEUFVXVHCPRMKT5IUHYBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJQHEYDONBUGEYTNJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/A7FXZXOWNKZNIJIBMUQ6PET5IUHYBA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTEOJQHEYDONBUGEYTNJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>