RC34: verified Cloud Run image reconciliation

RC34 corrects Control reconciliation when Cloud Run resolves an immutable OCI image index to its Linux/AMD64 manifest. RC33's native repair completed its data work, but Control rejected that resolved identity before collecting results and restoring job settings.

The adapter now verifies the exact relationship through authenticated Artifact Registry metadata. The configured job image, account, command, execution identity, and repair payload checks remain enforced; unrelated images and ambiguous metadata are rejected. Control needs artifactregistry.dockerImages.get on the existing image repository when this resolution is necessary.

This is a Control-only correction. The API contract bundle and native repair protocol are unchanged. The named worker for this integration remains the verified Linux/AMD64 RC33 runtime:

ghcr.io/harrisonoconnorhover/dander@sha256:89bd242e55d6e5ca37394ce81187f7d036e26b670c22f0ed5805a3c1df9447dc

Install the attached RC34 wheel with the required postgres, bigquery, and gcp extras for Control. The GitHub wheel is not available through PyPI; the standard public beta remains RC20. Use the named runtime base for the project's configuration image instead of the default generated Dockerfile that expects a PyPI RC34 package.

Protected source: 6964d63f4e9e8eab15ce63e4a1c65efb5268c2d0. Exact-main CI: 36874195042. The wheel/source archive passed distribution checks; the fresh installed wheel verified all 45 contract files and the Salesforce0.3.2/ServiceNow0.2.3 pair. See SHA256SUMS for exact digests. Release assets and tag are immutable.

Contract bundle SHA-256: a28316b7e5158e0520fe1c24d59885083714f47b67aa396892fa9742060fb279.

The initial native-engine observation and the corrective Control qualification are distinct records. This candidate does not promote additional providers, production identity-provider support, multiple Control replicas, or the broader Phase8 release gates. Date repair uses current retained raw data and is atomic per output, not across a whole graph.

Completed paired qualification

The distinct synthetic run run-ec3ecadaeb48d3cca4ccf537 completed through RC34 Control, the RC33 Cloud Run worker, and BigQuery. Control recorded two output rows written, four affected, and zero ingestion rows. Surrounding output rows, raw data, and the watermark were unchanged; the original Job settings were restored. Repeated submission returned the same run with exactly one native execution. Druff's real production client successfully read its status and explanation. All temporary cloud resources were cleaned before their deadlines; local proof databases/processes and task credentials were also removed.

The matched Druff 0.2.0-rc.1 image is public and anonymously verified:

ghcr.io/harrisonoconnorhover/druff@sha256:6aade12c399a67c604577e4a022af6dff22db7764626dd9a7a4f5cea1a2ceac1

See the candidate setup and bounded qualification record for exact artifact identities, hosted-mode prerequisites, and proof limits. Both connector packages passed all 116 tests against the public RC34 wheel. Existing Druff active/rollback aliases and the public PyPI RC20 beta remain unchanged.

RC33: guided workflow integration candidate

Known Control issue discovered during live qualification: when Cloud Run resolves an OCI index to its platform image, RC33 Control can fail terminal reconciliation after successful repair data work. Use the published RC34 Control correction. The native runtime completed the selected-date repair correctly; do not treat the RC33 Control candidate as end-to-end qualified.

RC33 is an integration candidate for the paired Dander/Druff guided workflow. The public PyPI beta remains RC20; this release does not close broader Phase 8 support gates.

• Preview a graph change against its saved revision before running it.
• Explain recorded run outcomes while preserving unknown measurements.
• Repair selected UTC output dates from retained raw data on single-task Cloud Run with BigQuery.
• Use verified Salesforce 0.3.2 and ServiceNow 0.2.3 package pins, including consistent prerelease compatibility checks.

Install the RC34 wheel linked above when preparing Control. RC33 is not published to PyPI; use the paired candidate runtime image for hosted execution instead of a generated Dockerfile that expects RC33 on PyPI. The RC20 quickstart remains unchanged.

Protected source: e1ed8cbe087d0248ff17f3378d1097c36859c920. Exact-main CI: 36867432159. The wheel and source archive passed distribution checks; a fresh wheel install verified the connector pair and every packaged contract file.

Contract bundle SHA-256: a28316b7e5158e0520fe1c24d59885083714f47b67aa396892fa9742060fb279.
See SHA256SUMS for the exact distribution digests. Release assets and tag are immutable.

Repair remains experimental: existing partitioned outputs and scalar business keys are required; rows outside the selected interval are preserved; transactions are atomic per output, not across all outputs. Retained raw data is not a historical snapshot. Live qualification is recorded separately against exact artifact identities.

dander-platform 0.9.0rc20

Beta prerelease.

Exact tag: v0.9.0rc20
Exact commit: 75c5654e95439eaf18e90fbacc849799f4fe42b6

Added

• Add an immutable provider-neutral projection and typed startup configuration for long-running hosted Control services, including closed credential-free local and cloud GraphStore locators.
• Add a deterministic digest-only local Docker Compose profile with aligned OIDC, bootstrap, GraphStore, HTTPS edge, active/rollback, and bounded verification projections.

Known limitations

• Cloud-provider hosted Control-service and matching Terraform projections are not yet implemented. The local profile is not live-qualified until exact current Dander and Druff images pass its OIDC, restart, no-drift, rollback, and cleanup checks.
• Review the complete known limitations before use.

Dander 0.9.0rc19

Status: beta prerelease

Exact tag: v0.9.0rc19
Exact commit: cad383b8ac74e8ba0ce0b3b92c66b0a5a93a306b

Known limitations: docs/known-limitations.md

Added

• Add the provider-neutral hosted Control API for durable multi-graph management, compatibility
  and catalog discovery, validation, deployment preview, and normalized run controls.
• Add memory, local-file, GCS, S3, Azure Blob, and OCI Object Storage graph-store adapters behind
  one optimistic-concurrency contract. GCS is live-qualified; the other cloud adapters remain
  unpromoted until their separate live proofs pass.
• Add external OIDC access-token validation and centralized viewer/editor/operator/admin
  authorization for hosted mode while preserving the explicit unauthenticated loopback mode.
• Extend the deterministic Control contract bundle with bootstrap, project, graph-resource, graph
  collection, and run-collection DTOs required by the generated Druff client.

Dander 0.9.0rc18 (beta)

Status: beta prerelease

Tag: v0.9.0rc18
Commit: ae2f8f6bfda5fe54309c54eee623b83d0b2bd2a3

Added

• Package deterministic io.dander.control.contracts/v1 JSON Schemas and canonical fixtures for
  the future Dander Control API, with explicit transport DTOs, a reviewed bundle digest, and CI
  drift detection.

Known limitations: docs/known-limitations.md

Dander 0.7.1 (beta)

Dander 0.7.1 promotes the accepted 0.7.1rc1 maintenance candidate.

• Prevents BigQuery run-history startup from exhausting metadata-update quotas by batching only genuinely missing nullable columns.
• Updates GitPython to 3.1.58.
• Preserves the 0.7.0 manifest, CLI, Terraform, connector API, and GCP resource identities.
• Retained source-free acceptance passed Greenhouse, HubSpot, four-endpoint Salesforce, ServiceNow, graph execution, replay, cleanup, and final stage-zero/platform no-drift.

This is beta software; see the documented limitations and upgrade guide before using business-critical data.

Dander 0.7.0 (beta)

Dander 0.7.0 is the stable beta release for cloud-portability Phase 1.

Added

• Versioned io.dander.runtime/v1 invocation, structured events, exit codes, and graceful-signal behavior.
• Provider-free runtime inspection and credential-free conformance.
• OCI annotations, capability manifest, immutable digest recording, SBOM/provenance, and non-root/read-only artifact checks.
• Cloud-neutral execution projection consumed by the existing Cloud Run path with capability validation.

Fixed

• Exact-pinned connector installation now preserves the running Dander version instead of silently downgrading it.
• The curated catalog recommends stable Salesforce 0.3.1 and ServiceNow 0.2.2.

Acceptance

The accepted source-free artifact passed local/Cloud Run OCI parity, ServiceNow smoke, four-endpoint Salesforce ingest, five models, 35 assertions, five catalog assets, replay, overlap skip, SIGTERM/SIGKILL recovery, cleanup, and final Terraform No changes.

This release does not claim AWS, Azure, OCI, PostgreSQL, Snowflake, or Redshift support. Those remain separately gated roadmap phases.

Dander 0.7.0rc2 (beta)

Dander 0.7.0rc2 is the accepted beta candidate for cloud-portability Phase 1.

Fixed

• Preserve the running dander-platform version during exact-pinned connector installation, so an incompatible plugin fails clearly instead of silently downgrading a source-free image.
• Recommend Salesforce 0.3.1rc1 and ServiceNow 0.2.2rc1, both compatible with Dander 0.7 and plugin API v1.

Acceptance

• Public source-free installation, local/Cloud Run OCI parity, ServiceNow smoke, four-endpoint Salesforce ingestion, transforms/tests/catalog, replay, overlap skip, interruption recovery, cleanup, and final Terraform no-drift all passed.
• 0.7.0rc1 remains rejected and was never deployed.

See docs/cloud-portability-phase1-acceptance.md for the bounded record.

Dander 0.6.0 (beta)

Dander 0.6.0 is the first public beta release.

• Deep Salesforce CRM ingestion for Accounts, Contacts, Opportunities, and Users through the independently installed Salesforce 0.3.0 plugin
• Sanitized failure history and interrupted-run reconciliation
• 24-hour creation-time expiration for run-scoped BigQuery staging
• Plan-first installation, immutable image publication, permission preflight, and rollback guidance
• Accepted source-free against a disposable Salesforce org with transforms/tests, updates, soft-deletion tombstones, replay, Dataplex publication, cleanup, and Terraform no-drift

Runtime behavior is unchanged from the accepted 0.6.0rc2 candidate. Dander remains pre-1.0 software; review the known limitations before using business-critical data.

Dander 0.5.1 (alpha)

Fixed

• Update the curated Salesforce and ServiceNow connector recommendations to their published 0.2.0 releases.
• Accurately require Dander >=0.5.0,<0.6 for those connector versions.

This patch does not change pipeline runtime or Terraform resource behavior.