Skip to content

Track Cargo workspace and Zed Rust-adapter certification #132

Closed
Closed
Track Cargo workspace and Zed Rust-adapter certification#132

Description

@ORESoftware
ORESoftware
opened on Aug 8, 2026

Purpose

Coordinate the next black-box Cargo/Zed interoperability layer without reopening or duplicating the completed single-package certification in #113.

Certified candidate

  • PR: zed-pkg-test/rust-app#9
  • exact head: 81ae22dadbb11db441c52d4a55b6b34a65903c90
  • exact base: zed-pkg-test/rust-app@d71626a8873dc706fd827c30dd78c4bb3beb4043
  • current production CLI snapshot: zed-pkg/zed-cli@de774cc9fc5b786d85e9b5ff19251675f0e9391b
  • exact interface declared and locked by that CLI: zed-pkg/zed-interfaces@d1bf8ef7c88a75292cbe8d697bfd269f30d62e2b
  • fixture package source: zed-pkg-test/rust-lib@f3c4e33cd0e5726b2c668c0306936f01674261fa

Coverage certified

  • Cargo virtual workspace and resolver v2;
  • [workspace.dependencies] inheritance;
  • dependency rename zed-rust-lib -> rust-lib;
  • target-specific cfg(any(unix, windows)) dependency;
  • separate build and dev dependency scopes/features;
  • normal Cargo version requirement resolved to Zed-installed source through the Rust adapter's generated paths and [patch.crates-io] fragment;
  • direct and transitive crates.io dependencies;
  • tracked Cargo workspace lock and generated Zed lock immutability;
  • Linux/macOS/Windows locked and offline Cargo matrix;
  • disposable Zed file-registry publish/install, symlink-store failure, frozen copy portability, and network-disabled replay;
  • non-root container ownership and clean source restoration;
  • exact binding between the checked-out CLI, its Cargo-declared interface revision, its locked interface revision, and the independently checked-out interface source.

Exact-head evidence

Workspace suite — run 31266467217

  • workflow contract/actionlint
  • Ubuntu 24.04
  • macOS 15
  • Windows 2025
  • disposable registry/Rust adapter/symlink/copy/offline lane

Artifact digests:

  • Ubuntu: sha256:943a2d5797994695edf2065eed092527a103518a38ee5816987d5655b4ee8104
  • macOS: sha256:b3ca25633cf7938bfa9fad4e2a9a370e30d946cfac9833bc91e56a7939a9f258
  • Windows: sha256:daf37c83dcc837f05f2831c4d2afb713cf8ccb8a64b5ab7d37d7cfbee9f5a3fe
  • registry/adapter log: sha256:a7490e728bd45290afd50de08ab8a9e336ddc9816b7c7c6f8a99d4c04cb9bebb

Existing single-package suite — run 31266467237

The pre-existing Ubuntu/macOS/Windows and disposable-registry jobs also passed at the same exact candidate head. Digests are recorded in PR #9.

Non-duplication boundary

This consumes rather than reimplements:

  • merged zed-pkg-test/rust-lib#2;
  • merged zed-pkg-test/rust-app#3;
  • native dependency provenance from zed-pkg/zed-interfaces#38 and zed-pkg/zed-cli#175;
  • Rust/workspace adapter implementation from zed-pkg/zed-cli#80.

Open documentation PR zed-pkg-test/rust-app#4 remains owner of README/agent-policy paths. It has been asked to rebase so it does not replace newer Cargo/Zed documentation; #9 uses a separate document and fixture tree.

AI-agent bridge status

The expected D-Bus service com.ores.ai-agent-bridge is not registered in this execution environment. The immutable adversarial review prompt and the superseding candidate head are recorded in ORESoftware/ai-agent-bridge.rs#104; no provider-backed review is claimed complete. That ledger records the existing service/provider credit/budget blocker.

Completion

Activity

  1. ORESoftware commented on Aug 8, 2026

    @ORESoftware
    ORESoftware
    on Aug 8, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Progress update for rust-app#9:

    • initial exact head 074db91d… exposed a rustfmt-only defect before compilation;
    • head 5cc642b0… passed workflow policy and all Ubuntu/macOS/Windows Cargo workspace lanes;
    • that head also passed Zed publication, symlink installation, generated .zed/cargo-paths.toml, Cargo build/test, the missing-store negative canary, frozen copy installation, and network-disabled locked/offline replay;
    • the only remaining failure was test-harness cleanup: the root Docker user created copied package directories the host runner could not remove;
    • current candidate d9f6a25d934ea555a40a1d4d5ca51cfab0c6c825 runs every write-capable container as the host UID/GID and is queued for full exact-head recertification.

    No production implementation change has been proposed because the product behavior under test succeeded. The harness fix strengthens non-root container portability rather than weakening the cleanup assertion.

  2. ORESoftware commented on Aug 8, 2026

    @ORESoftware
    ORESoftware
    on Aug 8, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Current-main repin: rust-app#9 head c29fd6ea5c7db22b78a59142a2929924ddded105 now certifies zed-cli@de774cc9fc5b786d85e9b5ff19251675f0e9391b with the exact interface revision declared by that Cargo manifest, zed-interfaces@d1bf8ef7c88a75292cbe8d697bfd269f30d62e2b.

    The merged single-package suite retains the historical adapter baseline. This workspace suite now supplies independent evidence against current production main, including the non-root container harness fix discovered in the prior run.

  3. ORESoftware commented on Aug 8, 2026

    @ORESoftware
    ORESoftware
    on Aug 8, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Certification complete for rust-app#9

    Exact head: 81ae22dadbb11db441c52d4a55b6b34a65903c90

    Completed:

    • exact-head workflow contract and actionlint
    • Ubuntu 24.04 Cargo workspace matrix
    • macOS 15 Cargo workspace matrix
    • Windows 2025 Cargo workspace matrix
    • current zed-cli@de774cc9fc5b786d85e9b5ff19251675f0e9391b bound to its declared/locked zed-interfaces@d1bf8ef7c88a75292cbe8d697bfd269f30d62e2b
    • disposable file-registry publish and install
    • generated Rust adapter parity with consumer Cargo config
    • symlink-store negative canary
    • frozen copy-mode portability
    • network-disabled locked/offline Cargo replay
    • Cargo and Zed lock immutability
    • non-root container ownership and clean source restoration
    • current documentation PR test: finish DEN-591 OCI boundary validation after merged draft #4 notified of the path/rebase boundary
    • immutable AI-bridge review target recorded in ORESoftware/ai-agent-bridge.rs#104

    Evidence digests:

    • Ubuntu workspace provenance: sha256:943a2d5797994695edf2065eed092527a103518a38ee5816987d5655b4ee8104
    • macOS workspace provenance: sha256:b3ca25633cf7938bfa9fad4e2a9a370e30d946cfac9833bc91e56a7939a9f258
    • Windows workspace provenance: sha256:daf37c83dcc837f05f2831c4d2afb713cf8ccb8a64b5ab7d37d7cfbee9f5a3fe
    • workspace registry/adapter log: sha256:a7490e728bd45290afd50de08ab8a9e336ddc9816b7c7c6f8a99d4c04cb9bebb

    The provider-backed bridge review remains pending for the recorded external service/credit reason; it is not represented as completed. PR #9 can now move from draft to normal review.

  4. ORESoftware commented on Aug 8, 2026

    @ORESoftware
    ORESoftware
    on Aug 8, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Owner promotion completed.

    • zed-pkg-test/rust-app#9 reviewed head: 81ae22dadbb11db441c52d4a55b6b34a65903c90
    • merge commit: 49e53ebeb029bf052bb707c240be63da4b4f9691
    • workspace workflow 31266467217: all Ubuntu/macOS/Windows, workflow-contract, and disposable registry/adapter jobs passed
    • retained single-package workflow 31266467237: all jobs passed
    • review threads: none
    • semantic boundary preserved: Zed owns package materialization and adapter emission; Cargo owns workspace/alias/target/build/dev/features/lock/build/offline behavior

    The provider-backed bridge retry remains deferred and is not represented as completed. It is tracked independently on ORESoftware/ai-agent-bridge.rs#104; it is no longer a blocker to merging this credential-free test fixture after exact-head owner review.

  5. ORESoftware
    closed this as completedon Aug 8, 2026
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions